Footer causing style problem

[imported_Ian]

http://www.total-emu.org/gallery/

No unregistered access, but you can see what the problem is.

I have tried using if condition="THIS_SCRIPT == 'scriptnamehere' to stop it doing it, but there are a few scripts that call the STANDARD_ERROR template and I'm not sure how to include all the gallery scripts into the condition.

I've tried a couple of ways that didn't work.

Any help would be appreciate.

You're not allowed to remove the copyright notice unless you have purchased a branding free license, so your best bet would be to fix the problems with the style.

[imported_Ian]

I don't want to remove it, I want to make it so the image at the edge line up.

I have added the code to the vb gallery footer, I need a way (if there is one) to make the STANDARD_ERROR template to ignore the same code that's on the end of that if it's a gallery page.

I do not want to remove the copyright. If I wanted to do that I would've already done it as it's the easiest thing in the world to remove

There is no problem with the style, apart from in the gallery, I fully understand why it's doing it, I just don't know who to stop it doing it.

This is what it says now, unrequired code in bold.

Content visible to verified customers only.

What I want to know really is, is there a way to stop the standard_error page adding that code when it's called from the gallery, I can do it for one script, but I can't get it to ignore that bit of code from all the gallery scripts.

If I put this at the end of the error template I can do it per script, I just don't have the knowledge to make it do this with every gallery script.

Content visible to verified customers only.

Ahh, gotcha now.
One thing you may want to try first... I checked your pages for XHTML compliance before my first post to make sure that it was a problem with the style and there were a few problems on your forum pages as well as your error page. I'd say it's very likely that if you fix those problems then it will take care of the problem there as well. Just incase you're not familiar with the site, here's where you can see the problems:
http://validator.w3.org/check?uri=ht...ss=1&verbose=1

Doesn't look like the problems would be too hard to fix as they're mostly some tables being ended that aren't finished and such. If you get those worked out then I'm about 90% sure that will solve the problem. If that doesn't help or you're not worried about the XHTML problems, then you should be able to use something like this in your error template:

<if condition="defined('VBA_SCRIPT')">

[imported_Ian]

Trying to fix the xhtml errors is on my to-do list, just above writing a script to see if the server is in a good mood

That works a treat though until I get round to it, thanks