The first thing to check is whether any other plugins on your site may be responsible for the trouble. To test, you can deactivate all plugins on your site, and see if that resolves the issue. If it does, then activate them one at a time to determine which is causing the conflict.
If that doesn’t help, please rule out a theme conflict by temporarily changing your site’s theme to a default theme (such as Twenty Sixteen) and trying again.
If the issue persists after that, could you post your site URL here, so I can have a look?
If you want it to remain private, you can contact us using the form here:
http://jetpack.com/contact-support/
Please make sure to include a link to this thread in your message. Thanks!
Hi Ryan,
I’ve tried disabling and enabling all plugins, including Jetpack (funny!). But the problem appears and persists after upgrading Jetpack a couple of days ago.
I’m already using Twenty Seventeen, so it is a default.
That’s why I’m so puzzled.
The site is catuslee.com.
Please help.
Thanks
Thanks for the link! I had a look at your site, and noticed that your server is running an older version of PHP.
Can you contact your host, and ask if they can update your server to PHP 5.4 or more recent? Ideally they would update to PHP 7 as it’s the version of PHP recommended by WordPress:
http://wordpress.org/about/requirements
Hi Ryan,
I have tried that before. Now I have just set the PHP version to 7.1 and the site just display Error 500.
And, I’ve tried as instructed by the error page to rename .htaccess file and enable display error. Both didn’t work.
What I don’t understand is that this site is a sub-directory of another site (zensiblo.com), which works fine without any problem. What is the deal here?
What can I do? Reinstall the whole site?
It happened that my hosting structure caused a problem. My site is a subdirectory of my other site and setting the php version in my cpanel cannot change the setting in the problem site.
My hosting provider had helped rectified the problem now.
Ryan, thanks for the suggestion.
Thanks for the update; I’m glad to hear things are working as expected!