Rest API issues – plugin conflict

Have you tried putting the firewall into learning mode then duplicating the steps that lead to the error? I was able to install the theme and import the started site content with no problems. I switched starter themes a few times without a problem too.

Can you open the browser console and see if you can see any errors when Wordfence and all your other plugins are turned on like they were when you first had this issue?

Tim

Hello Tim,

Thank you for getting back to us. Did you install the orbitfox plugin as the theme suggests to be able to select a starter site also?

Because after activating the theme, when you go to neve options and try to access any of the starter sites, we get the following message:

“In order to be able to import any starter sites for Neve you would need to have OrbitFox companion active.”

We activated this plugin and we inmmediately had the conflict. WordPress presented the following leyend:

“There has been a critical error on your website. Please check your site admin email inbox for instructions.”

We couldn’t even see the whole list of plugins later on, much less finding a way to deactivate the orbitfox plugin from wordpress. We needed to deactivate it from cpanel.

We followed your suggestion and put the firewall in learning mode. We proceeded to do the same thing, but we still have the same problem.

After installing orbitfox we tried to access the starter sites and we got the same message:

“It seems that Rest API is not working properly on your website.”

We also had the same plugin conflict than before. WordPress sent the same message and we needed to deativate orbitfox from cpanel.

We enabled the firewall back. It is not in learning mode anymore.

Thank you for your help.

Yes, I installed and activated the Orbitbox plugin. I’m still not getting any errors. I’m not seeing anything about the browser console that I asked you to look at. Did you get a chance to try with that open? Also, did you look at the site error logs to see if there was something reported at the time of the problem? I’m wondering if something as simple as running out of memory could be the issue.

Tim

We did what you suggested and nothing reported other than the messages related to the problem. If this is a memory issue, how would you know? How do you fix it?

You could check the server or site error logs. You’d see something similar to this:

PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 36287088 bytes) in /path/to/public_html/wp-includes/wp-db.php on line 1989

Usually it means that there isn’t enough memory allocated to PHP for everything you have going on with the site. That memory is cumulative so all your plugins, your theme, WordPress, and any other PHP apps you have running share it. If it isn’t enough this error occurs. The error about what it failed on is usually just the proverbial ‘straw that broke the camel’s back”. In this case you can add it in php.ini or .user.ini depending on your hosting set up. 256M is usually what I see most sites set to but if you have a larger site setting it to 512M isn’t out of the question. Also making sure you have PHP 7.0 or above will help since 7 introduced some really nice memory handling improvements.

The error logs might have other messages about this if memory isn’t the culprit which would help diagnose the issue.

Let me know what you find.

Tim

We didn’t find any memory errors. We have decided to move forward with another theme because of all the issues that we had, not only with wordfence, but with other plugins also.

Our PHP is > 7.0 and the memory checks enough to what we have at the moment.

Thank you for your help and interest.