Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Wordpress Integration - Sign out Problems
leafboxtea
New
I've been fussing with this - the sign out process when Vanilla is integrated into WP fails most times.
After clicking the the signout link it with either refresh the page with a "blank user" logged in. Even after I delete that user, it still comes back as a result of the signout process. If it doesn't refresh with the Vanilla page, it goes to a WP logout confirmation page. The next time I visit, it still shows as having the blank user logged in.
I tried this fix http://vanillaforums.org/discussion/comment/130686/#Comment_130686, but haven't had any success yet. I was using a caching plugin (W3 total cache) but disabled it thinking it was causing the problem. Even with caching turned off, the problem exists.
Can someone try it out and see what they can find.
username: testybob
password: test123
email (invalid): testing@leafboxtea.com
embedded forum: http://leafboxtea.com/discuss
alternate url: http://leafboxtea.com/social/vanilla
alternate login url: http://leafboxtea.com/social/vanilla/entry/password
I know it has something to do with the cookie getting deleted on logout, but I don't know enough about these things to wrinkle it out.
After clicking the the signout link it with either refresh the page with a "blank user" logged in. Even after I delete that user, it still comes back as a result of the signout process. If it doesn't refresh with the Vanilla page, it goes to a WP logout confirmation page. The next time I visit, it still shows as having the blank user logged in.
I tried this fix http://vanillaforums.org/discussion/comment/130686/#Comment_130686, but haven't had any success yet. I was using a caching plugin (W3 total cache) but disabled it thinking it was causing the problem. Even with caching turned off, the problem exists.
Can someone try it out and see what they can find.
username: testybob
password: test123
email (invalid): testing@leafboxtea.com
embedded forum: http://leafboxtea.com/discuss
alternate url: http://leafboxtea.com/social/vanilla
alternate login url: http://leafboxtea.com/social/vanilla/entry/password
I know it has something to do with the cookie getting deleted on logout, but I don't know enough about these things to wrinkle it out.
0
Comments
Since I switched to password auth, I wonder if this is a problem in the core?
Seems to be working so far, but I'm still testing it through.
Herein lies the problem: Tabbed browsing. Typically when I'm browsing my WP press I keep a tab of the backend dashboard open next to the one I'm working in. If a user is WP logged into a separate tab (frontend or backend, doesn't matter), then when that user logs out of Vanilla the forum reloads with the ghost account. Clicking sign out a second time while in the ghost account takes you to the WP logout confirmation (this happens regardless of ProxyConnect. I was getting this behavior using standard password authentication).
As long as I was only browsing with a single tab open, the sign out function in Vanilla worked smoothly. As soon as I complicated things by having a second browser tab open, Vanilla got all kinds of confused.
The error appears when ProxyConnect is enabled and when password is enabled - which then, of course, points to the problem being in the WordPress integratation. Though I have read on these forums that the ghost user problem was happening on embeds on other sites as well.
UPDATE: after disabling the ProxyConnect plugin I was unable to recreate the issue and signin/out worked fine. I renabled Proxy and then tried manual integration and then WP integration. I did all the setting changes in my Chrome browser. I then switched to FireFox and deleted all cookies and cleared the cache. On the refresh, the bug came up immediately. I tried to login to my admin account and Vanilla put me into the ghost account instead.
For the time being, so my users can access, I'm going to switch it all off. When @Tim has responded, I'll turn it back on and work with him.
1 go to Dashboard -> Settings -> Routes
2 Click edit on Default404
3 Target = your home page (ex: Categories/all) & Type = Internal
worked for me