{"id":2388,"date":"2026-10-20T08:32:20","date_gmt":"2026-10-20T07:32:20","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/edit-add-listing-form-and-title\/"},"modified":"2026-10-20T08:41:00","modified_gmt":"2026-10-20T07:41:00","slug":"edit-add-listing-form-and-title","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/edit-add-listing-form-and-title\/","title":{"rendered":"How to edit the Add Listing form and the &#8220;Add Place&#8221; title"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The Add Listing page shows the <code>&#091;gd_add_listing&#093;<\/code> shortcode. The fields in the form come from your post type&#8217;s custom fields, and the &#8220;Add Place&#8221; heading comes from a GeoDirectory setting, so you change both in the admin and not on the page itself.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Change, reorder or add form fields<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to Places &gt; Settings &gt; Custom Fields. If you have more than one post type, use the Settings menu of the one you want to change.<\/li>\n\n\n\n<li>Drag fields up or down to change their order in the form.<\/li>\n\n\n\n<li>Open a field to change its label (frontend title), its description and whether it is required.<\/li>\n\n\n\n<li>Add new fields from the list of field types, then save.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Fields set as admin only are not shown in the frontend form. There is a step by step guide in <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/how-to-add-a-custom-field-to-custom-post-type\/\">How to add a custom field to a custom post type<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Change the &#8220;Add Place&#8221; title<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to GeoDirectory &gt; Settings &gt; General &gt; Titles &amp; Meta.<\/li>\n\n\n\n<li>Find the Add listing page section.<\/li>\n\n\n\n<li>Change Add Title. The default is <code>Add %%pt_single%%<\/code>, and <code>%%pt_single%%<\/code> is replaced with the singular name of the post type, which is where &#8220;Add Place&#8221; comes from. Edit Title is the heading shown when a user edits a listing.<\/li>\n\n\n\n<li>Save the settings.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If you want &#8220;Place&#8221; to read differently everywhere, change the post type&#8217;s Name and Singular name at Places &gt; Settings &gt; General instead.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Add text or change the look<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Add Listing page is a normal WordPress page, so you can add text, images or other blocks above or below the GD &gt; Add Listing block. To restyle the form, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/code-snippets\/how-to-alter-the-add-listing-form-with-css\/\">How to alter the add listing form with CSS<\/a>. To give each post type its own add listing page, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/first-steps\/create-an-add-listing-page\/\">Create an &#8220;Add Listing&#8221; page<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Add Listing page shows the &#091;gd_add_listing&#093; shortcode. The fields in the form come from your post type&#8217;s custom fields, and the &#8220;Add Place&#8221; heading comes from a GeoDirectory setting, so you change both in the admin and not on the page itself. Change, reorder or add form fields Fields set as admin only are [&hellip;]<\/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-2388","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\/2388","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=2388"}],"version-history":[{"count":2,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2388\/revisions"}],"predecessor-version":[{"id":2695,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2388\/revisions\/2695"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2388"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2388"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}