I'm testing a gallery at this moment on the following location:
http://www.intellitainment.nl/testsite/gallery.php
It shows up correctly in Firefox // Mozilla/5.0 (Firefox/3.6), but apparently it doesn't show the correct styling in IE7.0.6001. I get the following DEBUG message, while I disabled all three debug messages in the settings.php file.
[DEBUG] Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; Tablet PC 2.0; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 3.0.30618)
Hi, guys. I'm looking for help on something similar. I have a client who has been using Minishowcase v09b142 for about two years now but a couple of months ago reported seeing a similar debug message: [DEBUG] Mozilla/4.0 (compatible;MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; FunWebProducts; GTB6.6; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; HPDTDF; .NET4.0C
The crazy part is that I've tried on several browser and several versions (compatibility mode in IE on and off), but I am unable to see this. I've tried on different PC OS's and also my Macbook Pro. I cannot reproduce it. But she definitely sees it and has sent me a screenshot. I don't know the exact version but it appears she is getting this on two different Windows 7 machines with IE 8. I have tried this exact same setup on my work Lenovo Thinkpad, but still haven't been able to reproduce it.
If there are any tips you guys can give me, I much appreciate it. I know you mentioned apostrophes in the theme files, but I'm not quite sure what you mean. Why would apostrophes be illegal and why would it cause this issue?
I have all debug settings off. Is there some other way I can supress this error? Btw, who's printing the error, Minishowcase, the browser, Apache?
Ironically, after having posted this, I made a change in my data.php files to remove any and all apostrophes. Unfortunately, since I could never reproduce the original issue, I couldn't tell if this helped. After asking my client to check from her end, she exclaimed that the error went away. Thanks, guys! (Although, I'm still baffled as to why this would have caused the error message.)