Hello, FDigital01, & welcome. This does seem to be primarily a problem w/your page builder &other plugins on your site, so our ability to help is likely limited, since the problem basically involves 3rd-party software. Having said thus, I’ll make a few suggestions & perhaps something I say here may (or may not) help.
The first thing I do in situations like this is to open wp-config.php & change WP_DEBUG to ‘true’. Please note that this is a security risk, so please change it back to false when you’re done. Then try to edit, etc, & see if any errors show.
Another thing you might try is to look in your web root & any subfolders for files called either error.log or error_log. These may contain error messages that might prove helpful. Lastly, sometimes your hosting provider has an aplet in their control panel called Errors or Error Logs which may also contain helpful error messages. If you’d like to post any of these here in your next reply, please enclose them in
line 1
line 2
line 3
Please let us know what you find out, if anything, ok? I wish I could be of more assistance, but when the problem is outside of core, it can be difficult to troubleshoot.
thankyou. is there anyway to determine what the correct order to re-activate plug-ins is? with the conflicts i get the error 500 white screen and the only way to get back into admin (I believe) is to disable the plug-in folder, then once in admin – renable the plug-ins. The problem is that the site keeps crashing when I re-enable the plug-ins one by one. It crashes at different points with varying plug-ins. All are up to date.
Would it be the order in which I am enabling the plug-ins be the issue?
FDigital01, the core plugins such as Akismet, Jetpack, etc, should be enabled first, as these are basically part of WordPress. From then on, it likely doesn’t matter, but if a plugin crashes, there’s obviously some conflict there. You should also ask your host if perchance your site is throwing any mod_security errors.
1 thing I can offer you is to set up a staging site on my server. If the site works well, then we know this has something to do w/your hosting provider. If not, then we know it’s a plugin conflict.
Unfortunately, the link you provided just leads me to the short url site where you can input a link to be shortened, not your site itself. That’s too bad, as often by looking at a site one can get clues as to things that might be going on.
It turned out to be a memory issue. I had not updated the php.ini on the staging site.
