• Resolved OsakaWebbie

    (@osakawebbie)


    After a routine update of my VPS’s major software (including nginx and PHP engines), PHP sessions were no longer being saved, causing both my own web apps and WordPress’s admin area to insist on a login for every page request. I solved the problem for my web apps when I discovered that for the directory where regular PHP sessions are stored, the user group had been inexplicably changed to apache (weird, since Apache is not even installed!). But apparently WP handles its sessions differently, so it is still claiming immediately after any login that my session has expired, and there is also no styling – I assume /wp-admin/load-styles.php is checking for a session also, although it was not obvious by a casual reading of the code. I’ve looked through log files for some error about directory permissions, but haven’t found any. Where should I look for the problem?

Viewing 1 replies (of 1 total)
  • Thread Starter OsakaWebbie

    (@osakawebbie)

    To follow up on this, I learned that authentication was happening fine, but the “session expired” message was visible simply because there was no CSS to hide it. Studying this off and on for several days, I finally noticed that if I View Source in the browser and paste the load-styles.php URL in a new tab, I can see what’s happening. The first 46,140 bytes of the CSS data that load-styles.php was combining would appear, and no more. I have no idea why that suddenly started acting that way – I still think it has something to do with the server update, but it’s a weird symptom. Anyway, I decided to simply stop concatenating the CSS files by adding define('CONCATENATE_SCRIPTS', false); to wp-config.php. It’s not ideal, but it only affects the admin area. Perhaps someday I’ll figure out what is causing the problem, but meanwhile, at least it works now.

Viewing 1 replies (of 1 total)
  • The topic ‘Where are WordPress sessions saved?’ is closed to new replies.