Changes not taking effect and logging me out

[jeboyd]

I just today upgraded from 1.4.07 "Dreadwind" to Pivotx 2.3.2.
I managed to get all my prior weblog entries imported to the new version.
When I go to MYInfo to change my email address, it does not complete and responds with
"Some fields were not correct. Please try again."
even though I filled in every field except the image field (which is not required.
I have tried it in every browser (Firefox11, IE8, Chrome and even Safari, all on my Windows XP system).
Also, when I try to update some things in the configs, like switching templates for my Weblog, the system does not register the update and, instead, logs me out.
I realize that this is similar to issue viewtopic.php?f=13&t=1341&hilit=password, but that issue does not appear to have been resolved in a way that works for me.
Please help.
Thanks,
Jim

[Harm10]

You did chmod all the right folders like described in installation (http://book.pivotx.net/page/1-2)?
You could try cleaning the cache (Administration / Maintenance) or removing your cookie.
Do you have PivotX tools installed? Then you can check integrity. http://extensions.pivotx.net/entry/28/pivotx-tools
And perhaps good to know for further investigation: is this flat file or MySQL?

[hansfn]

I assume you have followed the advice given in the forum thread you pointed to? In particular, explicitly logging out. If so, this might be a firewall issue - that the firewall is messing with the PivotX cookies (which is used to protect against CSRF).

Put a file called "pivotxdebugmode.txt" in the pivotx folder. Try to edit MyInfo or anything else that logs you out, log in again and the visit example.org/pivotx/modules/module_debug.php. Does it say "CSRF check failed ..."?

[jeboyd]

Harm10,
I double checked to make sure /images, /pivotx/templates and /pivotx/db and all files and folders in them are set to 777.
Mine is a flat file installation.
I cleared the cache in both the pivot admin and in my browser.
I deleted the cookie.
I logged out and requested a reset password.
Still, when I try to change my name on the MyInfo admin page, it responds with "some info is not correct. Please try again"
When I try to change my weblog to a different template, it says "The configuration was successfully updated". Then when I click the "Back to Weblogs" button at the bottom of that page it logs me out and when I look at my blog, the configuration has NOT in fact changed.
I guess I still need help.
I have Pivotx Tools installed, but it does not show in the Tool bar, even though I am logged in as a SuperAdmin???
It would seem that this is somehow related to the issue above as well.

Hansfn,
I have specifically logged out, reset my password deleted cache, deleted cookies, all resulting in same issue.
I put the "pivotxdebugmode.txt" file in the pivotx directory and then went back to try to change my weblog template and it logged me out as before. I then went to module_debug.php and it displayed a blank screen except for a "reload" link and a "clear" link ... no error info displayed.
I hope I am being clear enough with everything.

Thank you both very much,
Jim

[hansfn]

You have done everything you can do. Thanks for following my advice carefully.

I don't have any other ideas, but I'm probably able to fix it if I get PivotX and FTP access. If you trust me, send the login details to hansfn@pivotx.net

[jeboyd]

Ok, sending now.
Thanks,
Jim

[ben74]

Damn, I have exactly the same issues...

I tried to follow the steps but it doesn't change anything.

I'm working on a "one install only" handling subdomains (multisite). It's too bad I took quite a few hours to find out how the subdomains should be set in multisite mode and now I'm completely stuck.

Has a workaround been found for this issue ?

Cheers,

EDIT : I'm tried the same on ANOTHER browser (Opera) and it's working now. There must be some serious cookies coliding with Firefox I guess (as I had emptied FF cookies...)

[hansfn]

If you use multisite and you have domains example.org/www.example.org, sub1.example.org, sub2.example.org and so on, the cookie from example.org/www.example.org will cause problems for the other sub domains.