Guust
Forum Replies Created
-
Posts
-
Use the Payment Manager.
Set up 2CO at GD > Prices and Payments > Payments tab > 2CO (2Checkout)
Then when adding a package at GD > Prices and Payments > Prices tab > select “Recurring payment? (Only supported by PayPal and 2checkout)”.
ThanksThanks for sharing.
Does the system suggest the addresses if you start typing your addresses in the address field?
Thanks
All hard to say without checking your settings, and an exact step by step way of re-creating the problem.
Make sure to update all plugins and when adding or editing listings, let the system complete all steps before clicking away from a page.
https://wpgeodirectory.com/docs/faqs/what-is-the-best-way-to-update-the-gd-plugins/This reply has been marked as private.Your site is not limited to a particular country, but allows listings everywhere: GD > multilocations
You have not restricted the search like this either: https://wpgeodirectory.com/docs/core-general/#specific
I have changed your multilocations to your default country only, and it then works as expected.
Did you follow the link to https://wpgeodirectory.com/docs/core-general/#specific in the documentation I linked?
Are the listings within the radius of the centre of the postcode, ie the radius you set as explained at https://wpgeodirectory.com/docs/gd-search/#near?If we need to check your settings, post your URL and WP admin details in a private reply and we will check it out.
Thanks
A fieldset creates a heading.
If you set it as “own tab”, it will create a tab.
If you drag the HTML field below the fieldset, then the HTML field will appear in the new tab.
Labels can be hidden with CSS.
ThanksThat’s because you set the custom field to show in its own tab, so it shows as the heading and then as the label for the custom field.
Prevent that with adding a fieldset above it, see https://wpgeodirectory.com/docs/core-place-settings/#customThanks
This reply has been marked as private.You’re welcome 🙂
You’re welcome 🙂
Please update GD framework, it is still at 1.2.5 and should be 1.2.8.
You may want to delete the renamed older versions so your child theme is not confused.
Let us know if that fixes it.We prefer you post a new topic for a different issue, and use a relevant heading
That way the resolution of your issue may help others too.
ThanksDid you turn off the coming soon setting before deleting the plugin?
I suggest to reinstall the plugin, turn the setting off, and test before deactivating first and then delete.
GD would not be the cause of this.
Thanks
