Session changes in 5.1.1? Problems integrating 3rd party sessions
-
Hello,
I’m in the process of trying to update a woefully out-of-date WP installation (4.5.2). The site is currently running a custom mu-plugin to integrate user accounts/sessions from Magento.
This plugin is currently working on WP versions up to 4.5.2, but is causing issues on 5.1.1. The code in question can be found all around but looks something like this:
require_once('app/Mage.php'); umask(0); Mage::app("default"); Mage::getSingleton('core/session', array('name' => 'frontend')); $wp_mage_session = Mage::getSingleton('customer/session', array('name' => 'frontend')); $wp_mage_session -> start();
It appears the umask call and the sessions start calls are impacting WPs autoloader for classes. When these calls are included I get class not found errors.
Are there changes around session management in 5.1.1 that I should be aware of and haven’t found?
Viewing 5 replies - 1 through 5 (of 5 total)
Viewing 5 replies - 1 through 5 (of 5 total)
- The topic ‘Session changes in 5.1.1? Problems integrating 3rd party sessions’ is closed to new replies.