|
adasch
|
February 23, 2016 at 4:16 am
Hi there,
I tried to set up a backupbuddy process but it always failed with this error message
Error #937734: Unable to process BackupBuddy Stash Live stats. Invalid JSON. See browser console for details or here: `<br />
<b>Notice</b>: session_start(): ps_files_cleanup_dir: opendir(/tmp) failed: Permission denied (13) in <b>/wordpress/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php</b> on line <b>398</b><br />
I contacted BackupBuddy support and they said me it’s a Event Espresso bug:
Your Event Espresso plugin has a bug and is dumping out their error message on our page load, corrupting the Stash Live data unfortunately. The next Quick Release version of BackupBuddy, version 7.0.3.10, which will release later today, will strip out this error message. However, that plugin should NOT be injecting its errors on our pages.
What do you say? 🙂
|
|
adasch
|
February 23, 2016 at 4:21 am
Oh, it was not a “normal” backup but one to Stash Live.
|
|
Josh
|
February 23, 2016 at 9:08 am
Hi there,
It’d be interesting to see if you’d still get the Permission denied (13) error with Event Espresso deactivated. The Permission denied error usually means there’s a file/folder path/permissions issue.
Along with that, if you’re seeing notices getting spit out in places where they shouldn’t be, your server might have error_display turned on or you have WP_DEBUG turned on. In either case, those should be be turned off on a production server.
If the folks from Backupbuddy feel that this is an error that Event Espresso actually caused, they’re more than welcome to open up a pull request on our github project.
https://github.com/eventespresso/event-espresso-core/
|
|
adasch
|
February 24, 2016 at 6:55 am
Hi & thank you for your answer.
It’s kind of difficult to test things because the Stash Live backup takes sooooo lang – I have no idea why.
I did have WP_DEBUG set to true – this would be the reason for the error log (it is a non productive test site anyway).
But the problem remains, why EE throws a “permission denied” error.
So I deactiveted EE as you told me.
After deactivating EE, the other plugin EE Calendar was automatically deactivated as well.
Just after deactivating the plugin I gut this error message from wordpress:
http://snag.gy/ak2sO.jpg
when I activated the Core plugin again evything went fine. I activated EE Calendar and got the same error again.
So I guess the problem I have is not related to backupbuddy, as this error message directs to the same file and to the same line!?
I’m using EE Version 4.8.33.p and Event Espresso – Calendar (EE 4.3+) Version 3.2.6.p
Any suggestions?
|
|
Josh
|
February 24, 2016 at 7:55 am
Event Espresso is asking the server to open a session to set a cookie. The problem is that PHP sessions are currently not working on your server and the cookie cannot be set. The PHP server is not allowing the session to start and the error is how you find out.
The Permission denied (13) part of the error is telling you that it cannot open the required session temporary folder because the folder does not exist or that the permissions or ownership is incorrect. This is purely a server misconfiguration, not a program error with the plugin. You can ask your web host to fix the broken PHP session feature of the web server.
|
|
adasch
|
February 24, 2016 at 8:22 am
ok, thanks Josh!
|
