Jump to content

Replying to Login/logout Page Bug/conflict With Custom Menus

Post Options

  or Cancel

Topic Summary


Posted 28 January 2014 - 06:43 PM

Well then, that would explain it! I thought we had made an update that same or next day. (I might just have too many plugins to keep an accurate account of ;) ) Thanks for the update to the thread!

Elise Alley

Posted 28 January 2014 - 06:30 PM

Hey Kerry,

The update with this fix actually hasn't been released yet!  :)  The last update released was on the 14th (1.7.14).  The next release should be out soon.




Posted 28 January 2014 - 03:35 PM

I have not yet had a chance to test completely but it looks like the fix is not working.


Posted 20 January 2014 - 01:57 PM

View PostGlenn Ansley, on 20 January 2014 - 01:47 PM, said:

Hi Kerry,
Thanks for your detailed explanations. I was able to reproduce your problem and find a solution. It will be fixed in the next release of Exchange.
WooWhoo! Thanks for the prompt reply.

Glenn Ansley

Posted 20 January 2014 - 01:47 PM

Hi Kerry,
Thanks for your detailed explanations. I was able to reproduce your problem and find a solution. It will be fixed in the next release of Exchange.


Posted 20 January 2014 - 01:07 PM

I preface this entire post with the fact that my use of Exchange has been limited. I found the following which I have tested and confirmed and am looking for a permanent fix. You can try this on any Exchange install using the login/logout page in exchange placed in a navigation module of Builder.

Scenario: Basic paid membership site, Builder Theme, Exchange Membership product, using WP custom menu and the Exchange LogIn/LogOut menu item.

OK, this is not easy to explain so please bear with me.
1. Ideally when a member is not logged in, the the label of the menu should read Log In. And obviously when Logged In, should read Log Out.

I noticed on a site that I was working on that this was not always the case. At first it would work but then later it would not. And although the menu item, when selected, would function correctly, the label was not always correct. For example...

A user was logged in but the menu item label in the navigation module was reflecting LogIn. If that lagged in user selected the menu item it would log them out (so again, the function was there but the label was wrong).

The common thread I found was tied to the custom menu.

So, going back to when the menu-item was added to the the menu...
  • an admin was logged in
  • the exchange login page was added to the custom menu
  • no special label was added
  • no conditional logic was applied to that menu-item
  • the menu was saved
Everything works great so far for any users from the front end and the menu item reflects what is expected.... now, lets move forward and add a scenario where the admin must add something to that menu.

So, the admin logs into the admin area and proceeds to add another menu item to the custom menu that already contains the exchange login/logout page. And proceeds by saving the menu.

From this point on, the front end users will never again see the LogOut option on the exchange LogIn/LogOut menu item.

Theory: My theory is that because the custom menu has the option of customizing the labels of the menu-items and the fact that they ARE lagged in, when they save that custom menu WP thinks that they have also made the label for that menu-item "Log In".

Furthermore, if the admin removes the label on that exchange page before saving, when the menu is saved, that page ends up removed from the custom menu altogether.

The only way that I have been able to resolve this is to make any needed custom menu changes, remove the exchange page from the custom menu, then re-add LogIn/LogOut exchange custom menu item and save the menu.

As long as the last action before saving the custom menu is adding the LogIn/LogOut page to the custom menu, the front end menu item functions AND reflects the correct label.

Hope this is helpful to someone who can find a better resolution.

Review the complete topic (launches new window)