• When I attempt to “save and publish” changes to my theme (any theme) via the “customize” tab, I get the message “Your session has expired. Please log-in again.” The changes save, however.

    -I performed a clean install of 3.5.1 just today.
    -I’m using the default theme, Twenty Twelve.
    -I have deleted all plugins.
    -I have cleared my browser history (Chrome 27).
    -This happens in Firefox as well (haven’t tested IE).

    Perhaps it has something to do with the fact that my single hosting account is host to multiple domains. This particular domain is located in a subdirectory folder within the root file.

    Thanks in advance for any help you’re able to offer. ??

    -Kristy

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter klbarkan

    (@klbarkan)

    Still trying to wrap my head around this one. I discovered that there’s a master .htaccess file for my hosting account which automatically copies over to all subdirectories. So, I created a new .htaccess file for the subdirectory with basically nothing in it, thinking maybe something in the master .htaccess was causing trouble? Unfortunately I still got the session expiry notice.

    I also tried uninstalling WP, deleting the entire subdirectory, creating a new subdirectory with the same name, then reinstalling. Still no luck.

    I’ve been browsing other threads with people describing the same issue, but none of them seemed able to pinpoint the problem or discover a resolution.

    Somewhere along the line, cookies are not being saved correctly.

    More info:

    -In my WP settings, both my WP Address and Site Address are listed as “https://www.mysite.com” – On my host account, the MySite.com domain is pointing to a subdirectory within the root folder of the main (different) domain for my hosting account.

    -Every time I try anything, I clear all cookies and log back in to my admin account.

    -I have no plugins and am using Twenty Twelve. Error persists on other browsers.

    Any help or suggestions would be much appreciated. ??

    While this may seem fundamental, simply clearing all site data from your local browsers and flushing DNS may resolve this issue…you may also want to ask that each hosted domain points to a different domain nameserver if you’re on a shared host and each site uses the same ip address

    domain 1 points to dns1.domainservice.com and dns2.domainservice.com

    domain 2 points to dns3.domainservice.com and dns4.domainservice.com

    domain 3 points to dns5.domainservice.com and dns6.domainservice.com

    Thread Starter klbarkan

    (@klbarkan)

    Thanks so much for the response. I contacted my hosting provider and they told me that my domain nameserver has to stay at dns1.provider.com and dns2.provider.com. All of my domains point to the same.

    To be honest, I’m only vaguely aware of what this means. ??

    Also — What do you mean by “flushing” DNS?

    When I contacted my hosting company, I explained my WP problem in detail and the rep told me (via instant chat) “I have set the proper session.save_path for the account and resolved the issue. You will not experience such issue in future.”

    He asked me to clear my cache and cookies and try to log in again. I said thank you and lost the chat (of course), and then still (of course) experienced the problem. I’m not even sure what they were talking about with the session save path, though it sounded hopeful.

    Oh dear. I guess I’m going to have to dig deeper here…

    Thread Starter klbarkan

    (@klbarkan)

    Something important to mention (which I left out) — I have a second WP install in a different subdirectory, for a different domain, under the same hosting account.

    It gets the “Your session has expired. Please log-in again.” error too, when I hit “Save and Publish” after customizing the theme.

    The changes always save on both sites, however. I just have to hit the back button to get out of the session timeout screen.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Your session has expired. Please log-in again.’ is closed to new replies.