Alex Rollin
Forum Replies Created
-
Posts
-
We would be happy to take a look at your settings to see if we can find the problem.
Please be sure to have completed all the steps for configuration, and do check to see that your plugins are all up to date.
https://wpgeodirectory.com/docs/installing-addons/#updates
To allow us to examine the site, please create a private reply and include all the information listed below so we can make a complete diagnosis.
Add listing URL where we can see the issue:
WordPress Credentials
WP Admin Login URL:
WP Admin Username:
WP Admin Password:FTP Credentials
SFTP/FTP:
FTP Host:
FTP Port:
FTP User:
FTP Password:Hello!
I checked the site and found a few issues:
1. Set new page /location-2/ for Location page in GD Permalinks – this was previously set to the same page as the homepage
2. Fixed zoom shortcode in the homepage header section. This was set to zoom=1
3. Icon for camping category – icons should be 35*45px or near to that so they display correctly on the map.
4. Google API key – The map key for this site has reached the quota. Billing must be setup for the map key.
5. Open streetmap – You can switch it to OpenStreeMap to continue troubleshooting the site. Let us know if you do that and want us to take another look.
Hello,
we do not provide customizations here in the forum, paid or otherwise, but we do have a site where you can contact GD Experts for a quote: http://geodirectoryexperts.com
It sounds like you do not have users editing the listings. If that is the case, and you do not have some kind of complex versioning happening, you could build an app that talks to the GD Rest API.
If you look through the forums you can see various questions that others have asked about the Rest API. In some cases users are running apps that do CRUD ops on GD listings, for example.
Here are some docs to show you what is possible with the API: https://wpgeo.directory/rest-api/geodirectory-rest-api-endpoints/
That doc is for V1. V2’s API has had many changes and docs will be available soon.
It would not be recommended the recommended approach to try to automate CSV upload. CSV import is a resource intensive process and your app would need to respond to log errors. It might end up being more work in the end.
Hello,
as of right now we are using the flat maps and there isn’t a way to show that view.
It is already available: https://wpgeodirectory.com/try-geodirectory-v2/
Hi Kathy,
If you haven’t already, please see this thread that explains the issue:
In short, FB requires that apps using some API data be submitted for review, but so far they have not approved any apps using social importer.
We are making an update to Social Importer for V1 that will be available shortly.
Please subscribe to the thread above to receive a forum notification when the update it available.
Thanks
Hello!
For the Issue: X does not close
We have already created a ticket with Ninja to inform them of the issue.
If you have a chance to make a ticket with them you can share this link:
https://wpgeodirectory.com/the-font-awesome-v5-wordpress-problem/
@geek support, please make a new topic and we will try to help you with #2. Docs are here: https://wpgeodirectory.com/docs-v2/integrations/ninja-forms/
Please share a link to the page where we can see the issue. If you provide WP Admin we can take a look at the settings and see if there is some possibility to adjust this with the settings.
At this time moving the map buttons would be a customization, but there may be other options, we just need to take a look.
This reply has been marked as private.This reply has been marked as private.You can select a few at a time and run through them, if you are getting a resource error when running the query.
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.Hello,
I’m sorry but that is not possible without a customization.
A developer might use some javascript on a places date custom field to work with the calendar on a custom date field handling.
However the event manager addon would need further work as it is assumed users will input future dates.
