updated to 3.7.3 and.... :O~!!!!!

[pspmaster93]

now everytime someone posts on my site in all forums, all usergroups, both quick reply, and full reply, both super long posts and short posts it shows at the very end of the post underneath the last line the character ">" lol and the posts before i updated it added it to them all the ones already posted...

why does it keep showing > everypost

[Lynne]

Hard to tell. Did you upgrade your templates when you updated your vB? Perhaps when editing them, you goofed?

[pspmaster93]

i suppose its possible seeing i did them manually cause they are all customized but what could possibly cause that lol

[Lynne]

If you had an extra ">" in a template, it could add that at the bottom of all posts.

[pspmaster93]

yes... i supose it could lol the problem though, where and what template could the extrra > be in cuz its driving me nuts lol actually that gives me an idea, i could put an adsense code there once i find the extra > to increase revenue

--------------- Added [DATE]1224450971[/DATE] at [TIME]1224450971[/TIME] ---------------

DAM i cant find the problem

what template would do that and where in the template roughly could the problem be !

--------------- Added [DATE]1224453432[/DATE] at [TIME]1224453432[/TIME] ---------------

screenie

http://img513.imageshack.us/my.php?i...tffffffry9.png

[Marco van Herwaarden]

To troubleshoot this, please create a new Style with no Parent set. Now browse the forum using this new style, do you still have the same problems? If you are troubleshooting login or guest issues, you will need to set this style as board default in the vBulletin Options.

If this solves your problem then you know for sure it is style related. Next step would be to export your regular style and re-import it creating a new style, now test with this style, reverting each template and test every time if reverting this 1 template solves anything. Once you know which template is causing the problems you can focus on fixing it in your main style.

[Lynne]

We actually fixed this. He had an extra ">" in his postbit_legacy template. He removed it and it's fine now.