7
Based on @Max Lazar's comment I was looking over our "logout" code vs.
the code given in EE's documentation and I noticed this difference, we
use this code: Log
Out, but the docs say to use {path='logout'}. Does it matter?
I solved the mystery. The question I made above ^^^ was key and I probably should have just tried it from the get go. Turns out it ...
3
This may be related to bug #19338 which was fixed in EE 2.6.1. There was also a manual fix that could be applied. See 19338 on the changelog.
2
I've created a really basic extension to bypass the default message. It redirects to an account page on login and the home page on logout but this could be modified to point to any URL (i.e. a custom message landing page)
I've included a link to the download but should that expire you'll need to copy/save these two files into system/user/addons/loginbypass/
...
2
I have no idea what your actual setup is, but I general find that a best practice is to utilize embeds for control features as well as consistency. Here is an example: Two template groups, one call embeds, one called pages.
Embeds
index.html (unused)
_header.html
_footer.html
Pages
index.html
random_template.html
Your pages template will all look like ...
2
Check and update all your add-ons first. One of the difference between 2.5.2 & 2.7.3 is that now XID hash code is mandatory for all forms. Many add-ons don't used it before, as result - You are not authorized to perform this action after EE update.
For member_logout function XID is also mandatory.
$xid = ee()->input->get('XID') ? ee()->input-...
1
Try:
{redirect="{site_url}?ACT=16&return=/sign-out/"}
The & will probably be treated as part of the string instead of the divider between query strings.
Also try (just to keep it simple):
{redirect="{site_url}?ACT=16"}
Assuming the logout is working and it's the conditional that's at fault, try this conditional instead:
{if logged_out}
...
{/...
1
I wrote an answer to a related question a couple of days back on here: CP Session Timeout - no Solution?
That probably provides the info you need, but in short I referenced, as you have, that the previously usable session time variable $config['cp_session_ttl'] looks to have been deprecated, which allowed for custom login session lengths.
Solution ...
1
Have you tried outputting the session > userdata > fingerprint on the template. I've used this in addons to recreate the session ID in the control panel.
ee()->session->userdata['fingerprint']
I haven't accessed or tried this on a template though, but it might point you a the right direction.
1
I am getting the same thing. {path='logout'} does not work
This finally ended up working. I use Solspace User, not sure if that is related..
<a href="{path='?ACT=16'}&XID={XID_HASH}">Log out</a>
1
Try changing the user session type under Admin->Security and Privacy->Security and Sessions. I'm not sure which would be the best option so give all three a try!
1
Looks like you're using the Core Version of EECMS. The core version doesn't have the member module.
1
Before doing anything, make sure you are running the most recent version of EE. It's possible they have updated EE code in a newer version to deal with changes in how PDFs are created.
The issue sounds specific to the PDF so you'll have to have it in hand for testing. When you get it, disable XSS Filtering as a test.
Admin > Security and Privacy > ...
Only top voted, non community-wiki answers of a minimum length are eligible
