Robert reported today that he got an error saying that the REST API has no route. Here is how he had fixed it:

What the “route” is:

SNIP uses WordPress’ internal REST-API. It allows to exchange data back and forth between WordPress an SNIP. This is also used for activating and deactivating the plugin. If a route is not available there it means that there is something wrong with your WordPress configuration.

Solution 1:

Robert solved the issue by configuring the .htaccess file. A solution was posted on StackOverflow. Look it up there.

Solution 2:

Some users reported that they’re using an SSL Plugin to get WordPress ready to use SSL. It seems that those plugins cause side effects with the REST API. You can try the following:

1. Deactivate the SSL plugin for a while.
2. Try to activate SNIP.
3. If it works, try to re-activate your SSL plugin again.

If you still are not able to use SNIP, try the following:

1. Deactivate the SSL plugin.
2. Make a backup of your database.
3. Switch to SSL by doing a search-replace in your database like described here: How to Mass Replace URLs to HTTPS in the WordPress Database
4. With that you don’t need a SSL plugin any longer.

Solution 3:

Some users reported that they have issues activate the plugin while a security plugin is active (iThemes Security, etc). Try to deactivate them during SNIPs activation process.