{"id":2838,"date":"2026-10-20T08:36:34","date_gmt":"2026-10-20T07:36:34","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/geodirectory-reviews-faq\/"},"modified":"2026-10-20T09:02:33","modified_gmt":"2026-10-20T08:02:33","slug":"geodirectory-reviews-faq","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/geodirectory-reviews-faq\/","title":{"rendered":"GeoDirectory reviews and ratings FAQ"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Answers to common GeoDirectory questions about reviews and ratings. Click a question to open the answer.<\/p>\n\n\n\n<div class=\"wp-block-blockstrap-blockstrap-widget-accordion accordion mb-3\">\n<div class=\"accordion-item\" id=\"heading-disable-reviews-post-type\"><h2 class=\"accordion-header\"><button class=\"accordion-button\" type=\"button\" data-bs-toggle=\"collapse\" data-bs-target=\"#collapse-disable-reviews-post-type\" aria-expanded=\"true\" aria-controls=\"collapse-disable-reviews-post-type\">How do I turn off reviews and comments for one post type, like events?<\/button><\/h2><div class=\"accordion-collapse collapse show\" id=\"collapse-disable-reviews-post-type\" aria-labelledby=\"heading-disable-reviews-post-type\" data-bs-parent=\"\"><div class=\"wp-block-blockstrap-blockstrap-widget-accordion-item accordion-body pb-0\">\n<p class=\"wp-block-paragraph\">Each post type has its own settings for this. For events, go to Events &gt; Settings, click Show Advanced, and you will see:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Disable comments, which turns off comments and reviews for every listing of that post type, so the review form and reviews tab go away.<\/li>\n\n\n\n<li>Disable ratings, which removes the review stars but still lets people leave comments.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Save the settings. Other post types, such as Places, keep their own reviews. To turn comments off for one listing only, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/how-to-disable-comments-on-a-listing\/\">How to disable comments on a listing<\/a>.<\/p>\n<\/div><\/div><\/div>\n\n\n\n<div class=\"accordion-item\" id=\"heading-reviews-tab-members-only\"><h2 class=\"accordion-header\"><button class=\"accordion-button collapsed\" type=\"button\" data-bs-toggle=\"collapse\" data-bs-target=\"#collapse-reviews-tab-members-only\" aria-expanded=\"false\" aria-controls=\"collapse-reviews-tab-members-only\">How can I show the reviews tab only to members or logged in users?<\/button><\/h2><div class=\"accordion-collapse collapse\" id=\"collapse-reviews-tab-members-only\" aria-labelledby=\"heading-reviews-tab-members-only\" data-bs-parent=\"\"><div class=\"wp-block-blockstrap-blockstrap-widget-accordion-item accordion-body pb-0\">\n<p class=\"wp-block-paragraph\">You do not need to edit the GD > Single Tabs code. There are two ways to do it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use the tabs builder. Go to Places > Settings > Tabs, remove the Reviews tab and add a Shortcode tab in its place with the <code>&#091;&lt;span&gt;&lt;\/span&gt;gd_single_reviews&#093;<\/code> shortcode, which shows the full reviews area with ratings and the review form. Wrap it in your membership plugin&#8217;s restrict shortcode, if that plugin runs shortcodes inside its content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Or remove the tab with a snippet when the visitor should not see it. This example hides it from logged out visitors. Replace the check with your membership plugin&#8217;s own function if you need something more specific.<\/p>\n\n\n\n<pre class=\"wp-block-prismatic-blocks\"><code class=\"language-php\">add_filter( &#039;geodir_single_post_tabs_array&#039;, function( $tabs ) {\n\tif ( is_user_logged_in() ) {\n\t\treturn $tabs;\n\t}\n\n\tforeach ( $tabs as $key =&gt; $tab ) {\n\t\tif ( isset( $tab&#091;&lt;span&gt;&lt;\/span&gt;&#039;tab_key&#039;&#093; ) &amp;&amp; $tab&#091;&lt;span&gt;&lt;\/span&gt;&#039;tab_key&#039;&#093; === &#039;reviews&#039; ) {\n\t\t\tunset( $tabs&#091;&lt;span&gt;&lt;\/span&gt; $key &#093; );\n\t\t}\n\t}\n\n\treturn array_values( $tabs );\n} );<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Only one reviews area can show on a page, so do not add GD > Single Reviews elsewhere on the details page as well.<\/p>\n<\/div><\/div><\/div>\n\n\n\n<div class=\"accordion-item\" id=\"heading-rich-text-review-editor\"><h2 class=\"accordion-header\"><button class=\"accordion-button collapsed\" type=\"button\" data-bs-toggle=\"collapse\" data-bs-target=\"#collapse-rich-text-review-editor\" aria-expanded=\"false\" aria-controls=\"collapse-rich-text-review-editor\">Why does my review say it is empty when I use a rich text editor for comments?<\/button><\/h2><div class=\"accordion-collapse collapse\" id=\"collapse-rich-text-review-editor\" aria-labelledby=\"heading-rich-text-review-editor\" data-bs-parent=\"\"><div class=\"wp-block-blockstrap-blockstrap-widget-accordion-item accordion-body pb-0\">\n<p class=\"wp-block-paragraph\">GeoDirectory reviews use the normal WordPress comment form, with a plain text box named <code>comment<\/code>. GeoDirectory does not add a rich text editor to that form and we do not support one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Plugins that turn the comment box into a visual editor hide the original text box and show the editor in its place. If the editor does not copy its content back into the hidden box before the form is sent, WordPress receives an empty comment and refuses the review, even though the visitor typed one. Replies to reviews go through the same form, so they fail in the same way.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Turn the editor plugin off and post a test review. If it now works, the editor is the cause.<\/li>\n\n\n\n<li>Ask the editor plugin&#8217;s author to save the editor content to the comment field when the form is submitted. For TinyMCE that is <code>tinyMCE.triggerSave()<\/code>.<\/li>\n\n\n\n<li>Clear your browser cache and any page cache after changing plugins, so the old scripts are not still loaded.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you only want reviews that are a star rating with no text, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/code-snippets\/allow-reviews-with-no-comment\/\">Allow reviews with no comment<\/a>.<\/p>\n<\/div><\/div><\/div>\n\n\n\n<div class=\"accordion-item\" id=\"heading-review-error-405\"><h2 class=\"accordion-header\"><button class=\"accordion-button collapsed\" type=\"button\" data-bs-toggle=\"collapse\" data-bs-target=\"#collapse-review-error-405\" aria-expanded=\"false\" aria-controls=\"collapse-review-error-405\">Why do I get a 405 error from wp-comments-post.php when posting a review?<\/button><\/h2><div class=\"accordion-collapse collapse\" id=\"collapse-review-error-405\" aria-labelledby=\"heading-review-error-405\" data-bs-parent=\"\"><div class=\"wp-block-blockstrap-blockstrap-widget-accordion-item accordion-body pb-0\">\n<p class=\"wp-block-paragraph\">A 405 (Method Not Allowed) error means the web server refused the request before WordPress could handle it. GeoDirectory reviews are WordPress comments, so they are sent to <code>wp-comments-post.php<\/code> like any other comment, and something on the server is blocking that file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common causes are a firewall or security rule at your host, a security plugin that blocks comment posting, or a CDN or caching layer that does not pass form submissions through. To narrow it down:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Post a normal comment on a blog post. If that also fails, the problem is not specific to GeoDirectory.<\/li>\n\n\n\n<li>Temporarily turn off security and caching plugins and try again.<\/li>\n\n\n\n<li>Ask your host to check their firewall (often ModSecurity) and server logs for blocked requests to <code>wp-comments-post.php<\/code>.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">These errors often come and go with changes at the host, so contacting them first usually gets the quickest answer.<\/p>\n<\/div><\/div><\/div>\n<\/div>\n<script type=\"application\/ld+json\">{\n    \"@context\": \"https:\/\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How do I turn off reviews and comments for one post type, like events?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"Each post type has its own settings for this. For events, go to Events \\u003E Settings, click Show Advanced, and you will see:\\n\\n\\n\\n\\nDisable comments, which turns off comments and reviews for every listing of that post type, so the review form and reviews tab go away.\\n\\n\\n\\nDisable ratings, which removes the review stars but still lets people leave comments.\\n\\n\\n\\n\\nSave the settings. Other post types, such as Places, keep their own reviews. To turn comments off for one listing only, see How to disable comments on a listing.\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How can I show the reviews tab only to members or logged in users?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"You do not need to edit the GD \\u003E Single Tabs code. There are two ways to do it.\\n\\n\\n\\nUse the tabs builder. Go to Places \\u003E Settings \\u003E Tabs, remove the Reviews tab and add a Shortcode tab in its place with the [\\u003Cspan\\u003E\\u003C\/span\\u003Egd_single_reviews] shortcode, which shows the full reviews area with ratings and the review form. Wrap it in your membership plugin\\u0027s restrict shortcode, if that plugin runs shortcodes inside its content.\\n\\n\\n\\nOr remove the tab with a snippet when the visitor should not see it. This example hides it from logged out visitors. Replace the check with your membership plugin\\u0027s own function if you need something more specific.\\n\\n\\n\\nadd_filter( \\u0027geodir_single_post_tabs_array\\u0027, function( $tabs ) {\\n\\tif ( is_user_logged_in() ) {\\n\\t\\treturn $tabs;\\n\\t}\\n\\n\\tforeach ( $tabs as $key =\\u003E $tab ) {\\n\\t\\tif ( isset( $tab[\\u003Cspan\\u003E\\u003C\/span\\u003E\\u0027tab_key\\u0027] ) \\u0026\\u0026 $tab[\\u003Cspan\\u003E\\u003C\/span\\u003E\\u0027tab_key\\u0027] === \\u0027reviews\\u0027 ) {\\n\\t\\t\\tunset( $tabs[\\u003Cspan\\u003E\\u003C\/span\\u003E $key ] );\\n\\t\\t}\\n\\t}\\n\\n\\treturn array_values( $tabs );\\n} );\\n\\n\\n\\nOnly one reviews area can show on a page, so do not add GD \\u003E Single Reviews elsewhere on the details page as well.\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Why does my review say it is empty when I use a rich text editor for comments?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"GeoDirectory reviews use the normal WordPress comment form, with a plain text box named comment. GeoDirectory does not add a rich text editor to that form and we do not support one.\\n\\n\\n\\nPlugins that turn the comment box into a visual editor hide the original text box and show the editor in its place. If the editor does not copy its content back into the hidden box before the form is sent, WordPress receives an empty comment and refuses the review, even though the visitor typed one. Replies to reviews go through the same form, so they fail in the same way.\\n\\n\\n\\n\\nTurn the editor plugin off and post a test review. If it now works, the editor is the cause.\\n\\n\\n\\nAsk the editor plugin\\u0027s author to save the editor content to the comment field when the form is submitted. For TinyMCE that is tinyMCE.triggerSave().\\n\\n\\n\\nClear your browser cache and any page cache after changing plugins, so the old scripts are not still loaded.\\n\\n\\n\\n\\nIf you only want reviews that are a star rating with no text, see Allow reviews with no comment.\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Why do I get a 405 error from wp-comments-post.php when posting a review?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"A 405 (Method Not Allowed) error means the web server refused the request before WordPress could handle it. GeoDirectory reviews are WordPress comments, so they are sent to wp-comments-post.php like any other comment, and something on the server is blocking that file.\\n\\n\\n\\nCommon causes are a firewall or security rule at your host, a security plugin that blocks comment posting, or a CDN or caching layer that does not pass form submissions through. To narrow it down:\\n\\n\\n\\n\\nPost a normal comment on a blog post. If that also fails, the problem is not specific to GeoDirectory.\\n\\n\\n\\nTemporarily turn off security and caching plugins and try again.\\n\\n\\n\\nAsk your host to check their firewall (often ModSecurity) and server logs for blocked requests to wp-comments-post.php.\\n\\n\\n\\n\\nThese errors often come and go with changes at the host, so contacting them first usually gets the quickest answer.\"\n            }\n        }\n    ]\n}<\/script>","protected":false},"excerpt":{"rendered":"<p>Answers to common GeoDirectory questions about reviews and ratings. Click a question to open the answer.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,432],"class_list":["post-2838","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-how-tos"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2838","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=2838"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2838\/revisions"}],"predecessor-version":[{"id":2962,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2838\/revisions\/2962"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2838"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2838"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2838"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}