500 Server error when using plugin

> When wordpress debug mode is activated, there are error appearing on admin screens for the plugin, but they are related to deprecated arguments in wordpress core files (wp-includes/wp-db.php and wp-includes/functions.php).

What kind of error messages you get? All errors must be fixed, otherwise the ajax requests for wp staging will not work as expected.

> If I try activating Query Monitor, it breaks my site

In 5 years of using wordpress i never experienced that query monitor breaks a site, so i suppose you have serious php code errors on your site.

With debug mode enabled, try deactivating your plugins one by one until all errors are away than you can give WP Staging another try.

Here are the error messages:

Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/…./wp/wp-includes/wp-db.php on line 1515

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/…./wp/wp-includes/functions.php on line 3846

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/…../wp/wp-includes/functions.php on line 3846

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/…./wp/wp-includes/functions.php on line 3846

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/…./wp/wp-includes/functions.php on line 3846

Notice: get_currentuserinfo is deprecated since version 4.5! Use wp_get_current_user() instead. in /home/…/wp/wp-includes/functions.php on line 3662

I’ve used Query Monitor before without a problem –and I also used WP-Staging without any issues, but that was before upgrading to WordPress 4.5.

Hi,

these errors are caused by other plugins. WP Staging is not using deprecated functions and is working well with WP 4.5. So keep trying and disable all your plugins, than enable one by one to find out which plugin is causing that.

Regards
René

I just tried to install WP Staging on another site — same server, but I chose a site that is using a simple theme and has few plugins. On installation I got this error:

WP Staging File Permission error: /home/...../wordpress/wp-content/uploads/wp-staging/clone_details.json is not write and/or readable.
Check if the file /home/..../wordpress/wp-content/uploads/wp-staging/clone_details.json exists! File permissions should be chmod 644.

WP Staging File Permission error: /home/...../wordpress/wp-content/uploads/wp-staging/remaining_files.json is not write and/or readable .
Check if the file /home/...../wordpress/wp-content/uploads/wp-staging/remaining_files.json exists! File permissions should be chmod 644.

I checked and those two json files were NOT in the appropriate subdirectory.

I then went back to the site where I encountered the 500 server error and checked, and those two files DO exist, but their date does not correspond to installation date. Before I reported the problem here, I had uninstalled and reinstalled the WP-Staging plugin- because sometimes it helps to work with a fresh installation – so all plugin files are dated 4/18. However the json files in the uploads/wp-staging directory have file dates of 4/3/16 (probably from when I first installed WP-Staging). That’s fine if there has been no change in those files, but if there has been a change then it’s possible that there could be an issue with the WordPress distribution.

> I checked and those two json files were NOT in the appropriate subdirectory.

Create the files manually and give them via FTP 644 permission.

Make also sure that the file owner is the same as the owner php/apache is running under (Usually www-data)

Thanks…it doesn’t matter because I was only installing the plugin to test on a site without many plugins. I don’t have time to debug right now- I’ve already completed the task that I was going to create the staging site for.

The value of your plugin is in the time saved to quickly set up a staging site, but if I have to disable a bunch of plugins on a live site in order to debug, that kind of defeats the purpose. So I’m going to give this a pass for now. I’m guessing that the WP 4.5 upgrade created problems with another plugin on my site that didn’t exist before — probably a plugin that hasn’t been upgraded in a while…. but I’ll have to wait until some other time to deal with this.