Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
1. At the Page in the wordpress when I click edit button it will go to error page (HTTP ERROR 500)
2. At the Post under Categories latest news & events, when I click the edit button it also go to this error page (HTTP ERROR 500)
3. When I went to Appearance-> Customize there’s no features to click.
4. At the Page –> Draft, when we click the item to the trash, it will said the page already moved to trash but actually the page is still there.
5. For Event, i cannot add or edit the description.
Hi Violet,
It sounds like you’re either experiencing a very major plugin conflict, or your hosting provider is accidentally (but very actively) blocking your requests.
Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Hi Alex,
I already told the WordPress about what you told me. This is their replies.
“As per checked, the issues caused you unable to be access those page is due to the Word Fence. Hence, may request you to uninstall the Word Fence and try to access once again with those site and check if the issues still persists or not.”
I didn’t understand what he said about the Word Fence. Could you help me about this? I’m sorry to take your time. since, this is my first time to handle about this and i’m still a student. Thank you for your replies.
Hi Violet,
The highlighted errors aren’t typical of Wordfence but if you do have that plugin installed, it’s quite possible. Please navigate to WP AdminPluginsInstalled Plugins. Is Wordfence listed? If it is, please deactivate Wordfence and then delete Wordfence. Does that help?
If that doesn’t help or Wordfence isn’t listed, please run a plugin conflict test.
This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Hi Alex,
Is it the Wordfence Security? I should deactivate this one right?
Hi Violet,
Yes, that’s the plugin. Yes, please temporarily disable it to see if that helps. If it does, please re-enable Wordfence and then enable Learning Mode.
Hi Alex,
I already did what you said but it still the same. Is there any other way?
Hi Violet,
If that doesn’t help, that rules out Wordfence as the cause of this issue. Please run a general plugin conflict test.
Please disable all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.