{"id":2272,"date":"2026-10-20T08:29:35","date_gmt":"2026-10-20T07:29:35","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/membership-plugin-with-geodirectory\/"},"modified":"2026-10-20T08:40:41","modified_gmt":"2026-10-20T07:40:41","slug":"membership-plugin-with-geodirectory","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/integrations\/membership-plugin-with-geodirectory\/","title":{"rendered":"Can I use a membership plugin with GeoDirectory?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Yes. GeoDirectory doesn&#8217;t restrict content by membership level itself, but its listings are ordinary WordPress custom post types (<code>gd_place<\/code> for Places, for example) and its users are ordinary WordPress users. A membership plugin that can restrict custom post types, pages or user roles can be used alongside it. Check that the plugin supports custom post types, and try it on a staging site before you go live.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Charging for listings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If what you want is for people to pay to be listed, you don&#8217;t need a membership plugin. GeoDirectory&#8217;s Pricing Manager add-on sells listing packages through GetPaid. Each package can have a one-off or recurring price, a free trial, its own image, category and tag limits, and upgrade paths to other packages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">See the <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/pricing-manager-extension\/pricing-manager-setup-guide\/\">Pricing Manager setup guide<\/a>, <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/pricing-manager-extension\/how-do-recurring-packages-work\/\">How do recurring packages work<\/a> and <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/pricing-manager-extension\/how-to-sell-package-bundles-with-geodirectorys-pricing-manager-and-getpaid\/\">How to sell package bundles<\/a> if you want to sell several listings at once.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Showing packages to some users only<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pricing Manager has no setting to show packages by user role or membership level. You can mark a package as private with Is Private?, which hides it from frontend users adding a listing, and assign it yourself from the backend.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To vary what a listing shows by package, use Exclude Fields and Exclude Categories in the package, or the Show only on these price packages option on each custom field.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Registration and user types<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For registration forms, user profiles and different kinds of account, use UsersWP, our user plugin that works with GeoDirectory. Each UsersWP user type has its own registration form and assigns its own WordPress role, which a membership plugin can then use.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yes. GeoDirectory doesn&#8217;t restrict content by membership level itself, but its listings are ordinary WordPress custom post types (gd_place for Places, for example) and its users are ordinary WordPress users. A membership plugin that can restrict custom post types, pages or user roles can be used alongside it. Check that the plugin supports custom post [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[213,403],"class_list":["post-2272","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-extensions-features","gd_placecategory-integrations"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2272","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=2272"}],"version-history":[{"count":2,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2272\/revisions"}],"predecessor-version":[{"id":2666,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2272\/revisions\/2666"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2272"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2272"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}