Trouble with Amember integration and 3.8.4

[Hilary]

I wonder if anyone else had this problem and has found a solution?

The original setup -

I have Amember and Vbulletin fully integrated, so Amember handles all signups and logins for Vbulletin. New members sign up in Amember and are added to the relevant Vbulletin usergroup; when they sign in to Amember they're signed in to Vbulletin. Fine.

Normally, I run Vbulletin's upgrade and Amember isn't affected at all. This time, upgrading from 3.8.3 to 3.8.4 patch 2, the login is broken.

Things that still work:

• database integration - that is, new members (Amember) still become new Vbulletin users
• Vbulletin's own login - that is, I can still sign in as administrator through Vbulletin admincp, independently of Amember
• Amember login - that is, people can log into Amember itself and everything it protects except for Vbulletin.

Thing that doesn't work:

• single login. People logged into Amember are not logged into Vbulletin.

This is all very weird indeed. Minor upgrade of Vbulletin, no changes made to Amember.

Anyone already encountered and fixed this? Or have any inspired suggestions? I'd be pathetically grateful...

[Marco van Herwaarden]

You should ask this at the aMember support site.

[Hilary]

I did, thank you, and they just got it fixed yesterday. I thought it worth asking round in case anyone already knew how to solve the problem.

For the record - first they installed the latest version of the Vbulletin-Amember integration, then when that didn't work at all they somehow managed to get 'Rebuild Database' to run from inside Amember. (I have no idea how; it hasn't worked for me for about a year - always times out.)

Anyway - problem solved, thanks.