New Community Forums are coming. Watch this space for news.
Subscribe: RSS
  • I've been trying to figure this out for a few hours now, and I've narrowed it down to this: If I log into MODx (Evo 1.0.10), make a change to a resource on mywebsite.com, then switch to another tab within the same browser and load any page on mywebsite.com, then MODx will log me out immediately. This obviously makes it a pain to update mywebsite.com.

    So, why is this happening? I used MODx for years without this problem, and since I recently migrated mywebsite.com from a shared environment to a VPS (on the same host), I am guessing there is a new server configuration that Evo is not happy with.

    The only thing I've tried is deleting Firefox cookies for mywebsite.com, but that didn't change anything.

    (I am the only user logging in during this time.)

    More info:
    Browser: Firefox 24.0
    Web host: Liquid Web VPS
    CentOS release 6.4 (Final)
    PHP 5.3.26 (cli) (built: Aug 16 2013 19:16:36)
    mysql Ver 14.14 Distrib 5.1.68, for unknown-linux-gnu (x86_64) using readline 5.1
    Server version: Apache/2.2.25 (Unix)
    Server built: Aug 16 2013 19:11:58
    Cpanel::Easy::Apache v3.22.4 rev9999
    cPanel 11.36.2 (build 4)

    And yet more info (if needed):

    Compiled in modules:

    core.c

    mod_authn_file.c

    mod_authn_default.c

    mod_authz_host.c

    mod_authz_groupfile.c

    mod_authz_user.c

    mod_authz_default.c

    mod_auth_basic.c

    mod_include.c

    mod_filter.c

    mod_deflate.c

    mod_log_config.c

    mod_logio.c

    mod_env.c

    mod_expires.c

    mod_headers.c

    mod_unique_id.c

    mod_setenvif.c

    mod_version.c

    mod_proxy.c

    mod_proxy_connect.c

    mod_proxy_ftp.c

    mod_proxy_http.c

    mod_proxy_scgi.c

    mod_proxy_ajp.c

    mod_proxy_balancer.c

    mod_ssl.c

    prefork.c

    http_core.c

    mod_mime.c

    mod_status.c

    mod_autoindex.c

    mod_asis.c

    mod_info.c

    mod_suexec.c

    mod_cgi.c

    mod_negotiation.c

    mod_dir.c

    mod_actions.c

    mod_userdir.c

    mod_alias.c

    mod_rewrite.c

    mod_so.c




    PHP 5.3.26 (cli) (built: Aug 16 2013 19:16:36)

    Copyright (c) 1997-2013 The PHP Group

    Zend Engine v2.3.0, Copyright (c) 1998-2013 Zend Technologies

    with the ionCube PHP Loader v4.4.1, Copyright (c) 2002-2013, by ionCube Ltd., and

    with Zend Guard Loader v3.3, Copyright (c) 1998-2010, by Zend Technologies

    with Suhosin v0.9.33, Copyright (c) 2007-2012, by SektionEins GmbH





    [PHP Modules]

    bcmath

    calendar

    Core

    ctype

    curl

    date

    dom

    ereg

    exif

    filter

    ftp

    gd

    gettext

    hash

    imagick

    imap

    ionCube Loader

    json

    libxml

    magickwand

    mbstring

    mcrypt

    mysql

    mysqli

    openssl

    pcre

    PDO

    pdo_mysql

    pdo_sqlite

    Phar

    posix

    Reflection

    session

    SimpleXML

    sockets

    SPL

    SQLite

    sqlite3

    standard

    suhosin

    tokenizer

    xml

    xmlreader

    xmlwriter

    Zend Guard Loader

    zip

    zlib



    Thanks!
    • It may have something to do with PHP or server caching proxy settings, or perhaps IonCube? I seem to remember reading about some problems with that a while ago.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
      • I finally resolved this with help from my host. I don't fully understand php.ini files, but I will paste the host's response below in case this helps someone in the future:

        If you look at the php.ini files, you can see one is much newer than the other. PHP settings change and an old php.ini cannot properly configure a new PHP on a continually updated system.

        Also, php.ini is not an additive file. That it, PHP does not load the global php.ini file when a local one exists. This is why ionCube was not loading.