Alex Rollin
Forum Replies Created
-
Posts
-
I get this error, meaning the host is not resolving.
Status: Resolving address of reddtrekker.com
Status: Connection attempt failed with “EAI_NONAME – Neither nodename nor servname provided, or not known”.
Error: Could not connect to serverI will flag this for the team to see if they get the same issue.
If that is important to you, you should use the GD Post Claim feature that will redirect users to the login page.
Hello!
About the two issues you mentioned:
1) My front page is not my front page anymore. Now there is a new front page named “location” – featuring a completely different image and look, the map is not loading a single listing.
Getting started with GDV2 -> See this doc !
-> https://wpgeodirectory.com/docs-v2/geodirectory/getting-started/There is a section about the front page, too
2) The main and sub menu is gone. I used to be able to adjust this via GD -> Settings -> Design -> Navigation. Where do I find the settings for the menu now?
Read about navigation options here: https://wpgeodirectory.com/docs-v2/geodirectory/navigation/
There is also a doc about Supreme V2 here: https://wpgeodirectory.com/docs-v2/themes/supreme/
V2 is a major update, which is why we highly recommend it be done on a staging server first. After the initial upgrade it will be back to normal with easy updates.
If you have more questions about GDV2, please post a new topic to the appropriate V2 subforum. This topic was about the converter and that has been resolved.
Thanks!
Hello,
sitemaps are created by Yoast based on the settings in Yoast, and it can create sitemaps for country/region/city.
Review the Yoast settings or see our SEO page for more info:
https://wpgeodirectory.com/docs-v2/faq/seo/This topic was about an error and that seems to be resolved.
If you have an additional issue please create a new topic.
Thanks! 🙂
That isn’t a known issue at this time.
If you can recreate it let us know and we will be glad to check into it! 🙂
Why the 500, not sure, would need to enable debugging to see the error: https://wpgeodirectory.com/docs-v2/faq/troubleshooting/#500
Try moving the addons first before core.
You can also disable the addons first, then GD, then move them to the backup folder.You’re Welcome! 🙂
Have a great day!OK!
Next time please post in a GDV2 subforum, please, thanks!Search results cannot be sorted with the sorting options on the CPT Sorting tab. Those options only apply to Archive pages.
Is there a problem with CPT sorting? If so, what is the problem, and for which CPT?
The developers will post an update here as soon as they have checked into the issue.
We have different teams working on different plugins. Thanks for your patience as we are currently outside of support hours. They will check during normal hours.
Hello,
we do not have an integration with that plugin.
We documented how to integrate Formidable with GDV1, that may help if you are using GDV1.
https://wpgeodirectory.com/formidable-forms-in-geodirectory-tabs/For GDV2 you can examine the Ninja Forms integration in the GDV2 core plugin.
Support for integration with 3rd party plugins is outside of support.
Many updates have been released, so, update your GD addons.
I updated you to 20048.
Since you are on a staging site and your URL has changed you may need to deactivate and reactivate license keys.To fix the issue, simply deactivate and then reactivate your license keys with these steps:
- Visit the plugins page on your site.
- Click on the license link.
- Copy the key to your clipboard.
- Click deactivate, and then click on the deactivation confirmation.
- Click on license again and paste the key.
- Click activate, and then click on the activation confirmation.
- Repeat for each plugin, and when finished refresh the page.
- Click on the automatic update links for each plugin to update them.
https://wpgeodirectory.com/docs-v2/addons/installing-addons/#url-change
Check out our SEO page for other ideas, too:
https://wpgeodirectory.com/docs-v2/faq/seo/Hello,
which folder is the site in?
I updated GD to 20048. Try updating your other addons to see if you get the same error. We added some fixes in 20048.
