Alex Rollin
Forum Replies Created
-
Posts
-
paraphrasing Guust, 119 must also be in post_category
Please post again, so we can make sure, thanks
GDB is for v1 only so you can remove that plugin folder.
WC failed updates are famous causes of 500.
In most cases loading a fresh copy of the plugin by FTP will fix.
If you add a listing from frontend/backend with a known category working category does it work properly?
Please share WP Admin if we need to check the settings.
Make sure you have set the option to allow the CPT to be added from the frontend.
For V2 this is a checkbox in the advanced settings
GD – Places – Settings – General – Advanced – Allow add from frontendYou mean the title for the listing?
Listing titles are changed manually. We don’t provide any settings for auto-naming them.
There are some 3rd party plugins that do auto-naming, but, they may not work with the frontend editor form. This would be a customization.I have not yet tested that myself, but, since the plugins should not be network activated in the first place, there should be no issue. Each site must be converted in turn.
Have you enabled debugging on the site?
If not, then do enable debugging to see where the error is coming from.
Make sure you have swapped out all V1 plugins for the V2 versions, and updated themes.
You can write back with FTP and WP Admin info and we can take a look, but pleas enable debugging first.
You did this on a staging site, right?
This will be available in the next release, the register link at least. Coming this week some time.
This reply has been marked as private.It is a single setting for all individual files for all file upload fields.
When the user is not already logged in the “Is Claimed” field is not visible. It is that field that connects the User to the Listing.
I can’t recreate the issue with the deleted listings.
I will flag this for the developers to let us know if they have plans about this, but, for now the “Allow not logged in users to post from the frontend” creates users silently.
Works for me, your cache?
This reply has been marked as private.Please send over site access info so we can take a look.
Be sure to include links to those pages
Thanks
This is the error from the page:
Geocoding Service: This API project is not authorized to use this API. For more information on authentication and Google Maps JavaScript API services please see: https://developers.google.com/maps/documentation/javascript/get-api-keyYou can open up the Google API console and make sure the Geocoding API is added to the project. If it isn’t just add it.
This is a change from Google’s side. New keys created inside GD Settings include this API, but, if you already have a key setup, no need to make a new one if you can edit the old one.
