New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User gets logged out when trying to edit specific pages or globals #1560

Closed
peda opened this Issue Aug 18, 2017 · 11 comments

Comments

Projects
None yet
5 participants
@peda

peda commented Aug 18, 2017

Expected behaviour

When a user (with admin permissions) does access a page or globals and want's to edit them, he should stay logged in and be able to edit them.

Actual behaviour

In ~60-70% of the cases the user gets redirected to the login screen with the the error message "session expired"

There is nothing in the PHP error logs and nothing in the Statamic logs

Steps to reproduce

  1. This issue does occur on one specific live customer website (I can provide a bundle of the entire website - just let me know whom I should email it to)

Server Details

Operating System: CentOS release 6.9 (Final)

Web Server: Apache/2.2.15

PHP Version: PHP 5.6.31

Statamic Version: 2.6.4

Updated from an older Statamic or fresh install: Updated from older version

List of installed addons:

Logs

nothing gets logged ...

@peda

This comment has been minimized.

peda commented Aug 18, 2017

It might be related to the Stache - as enabling "update Stache on every request" seems to fix this issue, but that's obviously no solution for a production website

@jasonvarga

This comment has been minimized.

Member

jasonvarga commented Aug 18, 2017

Would you consider this a large site? About how many pages, entries, etc?

Please email a zip of the site to support@statamic.com

@peda

This comment has been minimized.

peda commented Aug 18, 2017

I would consider it a small to medium sized site with 37 pages and 32 entries

I'm right now uploading the zipped website to wetransfer and will send it to you in a few minutes - please be aware that "update stache on every request" is disabled at the moment. Once I re-enable this problem keeps happening again.

Clearing all caches didn't help either.

@anthubbard

This comment has been minimized.

anthubbard commented Aug 20, 2017

This has happened to me also, a lot, and almost always on large pages with heaps of replicator and asset sets (20 +). I was wondering if it were a cache / memory issue... It could also be related to #1558

@peda

This comment has been minimized.

peda commented Aug 22, 2017

@jasonvarga just wanted to let you know that the wetransfer link I sent you is about to expire on 25th August

@benjamin

This comment has been minimized.

benjamin commented Feb 11, 2018

@jasonvarga Did this get fixed/released - because I'm seeing the exact same thing on a site running v2.8.3. Let me know what info you need to help debug it...

@markdavies

This comment has been minimized.

markdavies commented Feb 12, 2018

@jasonvarga I'm also seeing this a lot, any update on when we'll see a fix?

@benjamin

This comment has been minimized.

benjamin commented Feb 15, 2018

Yeh, happens so frequently that it pretty much makes the control panel unusable for editing content.

@markdavies

This comment has been minimized.

markdavies commented Feb 15, 2018

For us we've discovered that it's whenever we hit our front end, we get logged out of the back end.

We think it's because we're running Statamic in a sub directory of a Laravel site, maybe the sessions are conflicting?

@benjamin

This comment has been minimized.

benjamin commented Feb 18, 2018

Thanks @markdavies but that's definitely not the issue we're having - Statamic is running all by itself on my server and the frontend is "essentially" just static html/js.

@peda

This comment has been minimized.

peda commented Feb 19, 2018

@benjamin in some cases when I had this issue it was a corrupt page *.md file - so when this issue does occur and can not be (temporarily) resolved by clearing the cache - have a look at the latest modifications to your pages (and collections and taxonomies). If clearing the cache does help, then it's most likely related to a caching issue (like the one I reported a while ago)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment