hi,
i’m using version 4.3.5. Plugin WPBakery Visual Composer, with thema NewsMag version 1.7,
as latest version 4.4.3 or previous versions of Visual Composer plugin WPBakery, always give 500 error, blocking the site.
What do you pua to understand why it happens ??
I await your response about
Hi,
Since version 4.4.2 the Visual Composer plugin has doubled in size and also has several new features therefore uses more resources.
The 500 error is an internal server error, I suggest you contact your host provider and let theme know about this: http://www.checkupdown.com/status/E500.html
If you have access to your error.log file, you can take a look at it and see if there’s any data that can lead to a conclusion. Also try to reduce the number of plugins and see if it happens again.
Thanks
Orlando i had the same error today
What u did to fix it ?
FYI …
you can try to do a full delete of the old folder via your hosting file manager;
then upload clean version via FTP — not the WP panel installer (!). Make sure your FTP software can “smart” upload txt vs binary files (some make you turn that feature “on”).
Make sure you have at least 128MB allocated to WordPress — which *must* be done from your wp-config.php file, in addition to the php.ini/panel settings in your hosting account.
Newsmag 1.71 *does* work fine with 4.4.2 if you are using that version vs the “latest” VC.
i did all of this and error 500 still here ^^
I use woocomerce plugin to check server status and i have 2 problems but i don’t know if it can explain the 500 error for Visual composer
Here are the 2 errors :
– Your server does not have the SOAP Client class enabled – some gateway plugins which use SOAP may not work as expected.
– wp_remote_get() failed. The WooCommerce plugin updater won’t work with your server. Contact your hosting provider. Status code: 403
Can u tell me ?
Well, those are issues with WooCommerce, not the thene. So, you likely want to contact Woo for support, use their support forum, or perhaps join one of the great Facebook ‘groups’ for help with WooCommerce.
Obviously — those two errors are self explanatory. You need to contact your hosting provider.
For Visual Composer, perhaps try the full reset procedure from my sticky topic on moving to new template. Note my section on how to address the “500 error of doom” if the above suggestion didn’t work.
See bottom this post for how to recover from 500 error:
https://forum.tagdiv.com/topic/how-to-guide-to-moving-from-newspaper-to-newsmag/
