Guust
Forum Replies Created
-
Posts
-
I deactivated WP Super Cache for you and Root Relative URLs.
You should only use GD Booster as caching and the other plugin would only work for simple sites, not a GD site.
It should all work now.It used to be pre-populated if I remember correctly.
I’ll get Paolo to look at this to see what the story is.And what happened when you clicked “Fix”?
If that did not fix it, post your URL and admin details please.That hover is normal for Avada, it is the same in other Avada sites.
This reply has been marked as private.You need to look in /wp-content/themes/GeoDirectory_framework/languages/en_US.po
and move that to /wp-content/themes/GDF_child/languages/es_ES.mo
You had the GeoDirectory – Multinews Theme Compatibility plugin activated.
That plugin is now obsolete since the new Theme Compatibility settings.
You can just delete that plugin.They are in the wp-content/uploads folder organised by months, when the listing was submitted.
Easiest is to save the current images to your computer and then add them to the new listing.You’re welcome 😉
That is already possible using pricing packages.
Create different pricing packages per category.
Then allow a custom field only for the relevant price package.Where are you saving your MO files?
If saved within /themes or /plugins they will be wiped every update.
The need to be in a special /languages folder, and most translation plugins do not do that automatically.You have to enable your sections at GD > design > …
[I enabled the detail top section for you]For listings already in your database you have to disable comments for each listing, or with a bulk quick edit.
So after you have disabled all comments in WP settings, you need to go to the listings in the backend and un-tick “allow comments”.
Just changing the main setting is only for new listings, not for those already in the database.Also GD > design > detail > Exclude selected tabs from detail page > Reviews
Add the GD Listings map widget to the top section of the GD Listings template at Appearance > widgets.
Without testing, what you have implemented should hide the tab of every user, for any other visitor except level 2 and above.
So anybody with level 2 and above should be able to see the tab of levels 0 to 4.Is that what you are trying to do?
I did not know current_user_cannot existed.
Can you use current_user_can instead?
https://codex.wordpress.org/Function_Reference/current_user_can
