Just to confirm that this is still in an issue in the latest dev and not to lose this issue from the other thread....

Login works fine the second time...

Comments

iva2k’s picture

Status: Active » Postponed (maintainer needs more info)

Thanks for posting. Can you list all the details: steps to reproduce, expected vs. actual effect? Is it with multilingual setup or not?

Chad_Dupuis’s picture

Thank you for the response (and for the great module!)... no multi-lingual. Botcha was on the site working fine with pressflow until last two botcha updates as far as I can tell and still now with dev. Basically at first login you get the session reuse error, then the second login is fine. This will be for all users including admin. Disabling botcha on the user login form stops the issue.

iva2k’s picture

Can you specify which version (or -dev snapshot date) that it was working with Pressflow? Also it would be very helpful if you could downgrade to that version and try again to confirm. That will greatly help to narrow down what causes the problem and fix it quickly. Thanks!

Chad_Dupuis’s picture

I'll try to downgrade and work on a few versions, probably won't be able to do this until tuesday... hopefully some of the other pressflow users in the previous thread can try this out before then. I will report back as soon as I can...

kndr’s picture

I am using Pressflow-6.22.104, Botcha-6.x-1.x (2011-10-01), i18n-6.x-1.9 and everything looks fine. I can't reproduce this error.

bfikree’s picture

Status: Postponed (maintainer needs more info) » Active

We are using Pressflow-6.22 and the latest Botcha dev and we get the error on login, have to clear cache and try again. Disabled module for login pages.

iva2k’s picture

Status: Active » Postponed (maintainer needs more info)

Is that still an issue?

iva2k’s picture

Status: Postponed (maintainer needs more info) » Fixed

Assuming that the fixes did their job and this is no longer an issue. Please reopen with new information if it is still an issue with latest release 6.x-1.8.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.