Did you encounter an unexpected behavior while trying to use Thrive Comments on Custom Posts created using the Pods plugin? Enabling the Rest API for the plugin will help solve this.
In this article, we’ll see a common behavior people have been seeing while trying to use Thrive Comments with the Pod plugin and how enabling the Rest API for Pod will help solve it.
Understanding What Happens
By enabling Thrive Comments on blog posts, pages, and custom posts, you allow website visitors to drop their comments. This works fine when you use Thrive Comments on Custom Posts created using the Pods plugin.
But, the problem may occur when you try to reply to these comments through the Moderation Dashboard in Thrive Comments. The message says, “Sorry, you are not allowed to read the post for this comment.”
Enabling the Rest API for the Pod plugin
The message mentioned above appears when the plugin you use for custom posts does not use Rest API, while WordPress and Thrive Comments already do.
To enable Rest API in the Pods plugin on your website, open your WordPress admin area, navigate to Pods Admin -> Edit Pods, hover over the Pod you want to accept comments in, and click Edit.
When you open the Pod to edit, click to open the Rest API tab.
In the Rest API tab, check the checkbox beside Enable to enable the Rest API for this Pod.
After you enable the Rest API and manage any desired settings, click the Save Pod button on the right.
If you use any other plugin to create custom posts where you see a similar message while using Thrive Comments, enabling the Rest API will solve it.
We’ve just seen the message some users see while using custom post plugins with a disabled Rest API and how to enable Rest API in the Pods plugin.
Next, if you want to style the comments on custom post types, here’s a document that will help you use the styling options in Thrive Comments.