Page 1 of 1

vBulletin + aMember --> Strange Stylesheet Issue

Posted: Thu Jan 07, 2010 6:25 pm
by volomike
I have this problem where vBulletin has been upgraded from 3.8 to 4.0, but now the aMember authentication plugin won't work and it's causing vBulletin 4.0 to completely lose its style sheet settings. It's like not loading any style sheet at all, although we see the stylesheet clear as day and we can hit the URL manually.

Note that it's not the whole plugin -- just the part of the plugin that reads "During startup - set session user_id from aMember if possible and reload" which affects the "style_fetch" hook location. If we deactivate that in vBulletin 4.0, the problem of the stylesheet issue goes away, but then users have to login twice -- once to aMember and once to vBulletin.

I tried looking at the HTML of the page when the plugin isn't loaded in vBulletin 4.0, and then compared to when the plugin is loaded in vBulletin 4.0. I then ran it through a DIFF tool and didn't see any major differences except that the SECURITYTOKEN Javascript global variable is different.

Unfortunately I can't go back to 3.8 because this project I inherited never had a backup before the upgrade. And because this is a production website, I can't give you URLs here to see the problem in action. We disabled the plugin for now, meaning our paying members are having to login twice and are confused to say the least.

Have you seen this problem with aMember and vBulletin 4.0? Can you suggest a programming fix?

Re: vBulletin + aMember --> Strange Stylesheet Issue

Posted: Fri Jan 08, 2010 1:11 pm
by volomike
Well, my client ended up getting a patch from aMember. So, if this happens to you too, go ahead and contact aMember for the patch.

Re: vBulletin + aMember --> Strange Stylesheet Issue

Posted: Tue Jan 12, 2010 4:17 pm
by daedalus__
i haven't used either software but im interested in seeing the code. its a strange day indeed when stylesheets are obstructed.