Alex Rollin
Forum Replies Created
-
Posts
-
Have you already exported the current categories?
Does your CSV match the same format?zip it first and then attach in a private reply
Please also include your site URL and WP Admin credentials so we can look at the site settings
The options for V1 packages are documented here: https://wpgeodirectory.com/docs/prices-and-payments-add-on-overview/#config
I mentioned making the package inactive becauseit sounds like … maybe users won’t sign up in time? Maybe that will lead to things expiring too fast? Maybe you want to do some bulk updates? Having a package that you ‘know’ you can change around, that the users can’t select, might be helpful.
“Force upgrade” is an option in the Claim listings settings.
V2 is out of beta and will be on wp.org very soon, at which point V1 will only receive security updates. If you are pre-launch…
The “Upgrade” and “renew” options appears on the listing on the date of the first reminder.
You are using V1?
Each package with Upgrades should have “Has upgrades” checked in the package
https://wpgeodirectory.com/docs/prices-and-payments-add-on-overview/#config
The site has gone 500.
Please see https://wpgeodirectory.com/docs-v2/faq/troubleshooting/#500
I do not see the CSV file, can you reupload please?
thanks
On the new site you need to assign a non-recurring price package to the new listings, so that the expiry email will be sent when the package is expiring. Once applied, using GDV1, you should set the package to ‘inactive’ so they cannot claim the same package.
On that package, you will have more options with GDV2 to set which packages they can access when they claim and when/if they upgrade.
If I understand you correctly, the users will claim the listing, so, with GDV2 they would/could be forced to choose a new package (not the current package).
Nothing to crack, exactly. All the routes are declared. This is every day stuff for developers, now.
OK, I have logged in, thanks.
Now, please tell me what we can help with.
Did you run the setup wizard?
Is there something specific, like, can you send a URL and describe the issue?Right now your custom css is in a snippet, but, it is probably better if you keep it in appearance -> customizer
I disabled your custom CSS and it seems to be single on Mobile. You should debug that CSS to find the issue.
Selecting an autocomplete result in the ‘search for’ field is like clicking on a link, disregarding other search selections, and forward the user directly to the appropriate page. We have had several requests about the functionality and are considering which configuration options to offer for later versions.
No, nothing in the update about SiteOrigin, and certainly not applicable to a WP page.
Check with SiteOrigin supportIt is ‘just an API’, and works ‘the WP way’, so, any example you find for WP, you just need to apply that to the GD routes.
ex. https://www.pjvillanueva.com/wordpress-rest-api-using-postman/
Use places, why not?
Rename places, yes.
