@Chris D - when I put some ad or classic banner on page, gallery page layout is ruined. Any ad location (header, above breadcrumb...) ruined gallery page layout. For example, photo is streched through all page, sidebars are destroyed, rate is not working... please see picture below
If I disable banner, gallery page is like it should be.
Try now @Mike - http://www.pijanitvor.com/media/image.554/
Photo is not streched because is not wide enough to destroy page layout, but all other errors are there, but only in firefox.
Image is not centered, lightbox is not working, sidebar is destroyed...
So, after experimenting with different browsers and accounts, this bug start only if user is in Superadmin group whatever browser is in use.
If any kind of banner is activated on page, and user is member of SuperAdmin group, layout of gallery page is broken.
I've looked at the problem and it's weird. Basically the css.php only shows this line:
If you remove 2 CSS templates from the CSS list of the css.php GET request, the CSS is displayed. My Add-on uses 2 CSS templates here so that's why when you disable the Ad on this page, the CSS is displayed again as the 2 CSS aren't used.
You might think that my Add-on causes the problem but I also tried removing manually other 2 CSS templates with the Ad enabled and the CSS is displayed.
On this page there are 29 CSS templates. So what could be the problem?
It is getting stranger. Somehow is connected with @Luke Foreman addon Minorin because if I disable that addon, gallery page layout is getting back to normal. Luke, could you find somehow soulution here?
Yep, if I disable random two addons (or in some case just one) which are connected with css on gallery page, then gallery page layout is normal, not broken.
So, like Siropu said, problem has something to do with the amount of css templates and the data loaded from them.
So, is there some solution other then unistall addons related with css on gallery page?
If you submit a ticket with FTP details and an example css.php URL that triggers the issue (though I suppose you have above), I will attempt to debug it. I suspect it is related to something on your server (a configuration value) more than XF itself, though I'm not sure what that would be off hand. (Potentially a regular expression limit.)