Posted: October 30, 2015 at 9:03 am
|
Hi all, we need to do some major development so I want to move it on to a sub domain so we aren’t working on their live site. We did this about 3 months ago with no issues, but this time it throws up heaps of EE4 errors. The development URL is on the same server with the exact same set up so I’m not sure whats going on. I’ve checked the /tmp file and its there, opening up the permissions on it has no effect. These are the two main errors we get: Warning: session_start(): open(/tmp/sess_0cbd3f105cb1fe0de5dd3211f7b8cd19, O_RDWR) failed: Permission denied (13) in /home/…./public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 399 Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/…./public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php:399) in /home/…./public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 399 Any ideas what we can do? |
|
Ok, I’ve just realised the path to the /tmp folder is wrong! The error has the path of the live hosting not the dev one (they are very similar). Where is this being set!? We can’t find any reference to the live hosting folder name… |
Hi, could you try the last suggestion on this page? http://stackoverflow.com/questions/27039635/warning-session-start-failed-permission-denied-13 — |
|
Hi Zoe, You set the save session path within either your php.ini file within the sites root directory, or within the .htaccess file within that directory. Within php.ini you’ll use something like this:
Within the .htacces file you’ll need something like:
Which method you use depends on your host really, if they support php.ini files within each sites root directory use that, if not use the .htaccess method. |
|
|
Argh I just found the problem!!! The live site has an SSL and it was the ithemes security settings causing the issue. Here’s what I did incase it helps anyone else. When on to my hosting and launched PHPMyAdmin. Then delete itsec_ssl row (the lazy but quicker option) and ensured all other SSL settings are set to 0. There is also a URL that in the rows that are returned that will need changing. |
Thanks for sharing Zoe, One word of caution is to be careful when editing URL’s directly within the datebase, especially if they are being stored within a serialized array as changing the length of values will break the array when PHP tries to unserialize the data from the database. I don’t know what/where you changed urls above, so this may not even apply. But if altering URL’s within the database, use a search and replace script that will adjust the serialized array values too, like – InterconnectIT Search and Replace Script Or when moving the site use a plugin that will do it for you, like WP Migrate DB |
|
The support post ‘Copying live site to dev URL produces errors’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.