Guust
Forum Replies Created
-
AuthorPosts
-
Please review https://wpgeodirectory.com/docs/core-export/ and https://wpgeodirectory.com/docs/core-export/#important
1. You should not use post ID unless you want to overwrite existing listings with the same ID.
2. You have non-html characters like Le�n, you need to create the file in OpenOffice CSV, not copy and paste from other programs.
Same issue for city and region entries, and neighboorhoud.
That will be the same reason the location data does not match your default location and therefore it cannot import.3. As a free user, you cannot use data in the featured column. That column can only be used if you have the Payment Manager.
4. You cannot use neighboorhoods unless you are using the Location Manager.
Best practice is to add a few listings in the backend and then export the file so you can see the format.
ThanksWP admin details please, and more details please of what changes you need to make again and why.
Thankshttps://wpgeodirectory.com/support/topic/whoop-options-menu-hover-colour-not-working/
Please refer to the answer to your duplicate question at https://wpgeodirectory.com/support/topic/disable-city-and-region-requirements
Thanks
That is not possible.
All locations need to be in the city > region > country format.
There is no need to add any locations to the database.Please refer to
https://wpgeodirectory.com/docs/definitions/#location
https://wpgeodirectory.com/docs/manage-location/#editThanks
The incorrect message in your footer is what broke the pages.
Thanks for letting us know, I’ll set this to resolved.The warnmings come from your caching plugin.
I suppressed them as explained here: https://wpgeodirectory.com/docs/faqs/help-i-get-a-php-warning-on-my-pages/See also https://wpgeodirectory.com/docs/known-issues/#w3cache
Thanks
I think that is only possible by manipulating the database, but I’ll get a developer to have a look for you too after the weekend.
ThanksYou’re welcome 🙂
This reply has been marked as private.June 11, 2017 at 4:34 am in reply to: Geocode was not successful for the following reason: REQUEST_DENIED #382701This reply has been marked as private.June 11, 2017 at 4:34 am in reply to: Geocode was not successful for the following reason: REQUEST_DENIED #382700The API key is not authorized for the (sub)domain you are using.
ThanksHave a look at this:
https://wpgeodirectory.com/docs/useful-plugins/#logicThat will allow you to use different widgets on the Listings/category pages depending on the CPT.
Thanks
#1 See https://wpgeodirectory.com/docs/searching-and-browsing/
#2 The Google API may think it is in a different “city”, see more at https://wpgeodirectory.com/docs/definitions/#location
You may need the Location Manager: https://wpgeodirectory.com/downloads/location-manager/Thanks
Hi Andrew, if you use plugins to input custom CSS and functions, then that data will be retained when the theme gets updated.
You should delete the SG cache plugin, see https://wpgeodirectory.com/docs/known-issues/#w3cache
You should also add your licences at WP Plugins.
I’ll get one of the developers to have a look at your other question after the weekend.
Thanks
Hard to say I think without testing it. As long it follows all WP theme development standards it should be able to be integrated I think.
There is only one way to find out, and that is try it, so if you run in troubles when trying, let us know and we’ll have a look for you.
Thanks -
AuthorPosts