Stiofan O'Connor
Forum Replies Created
-
AuthorPosts
-
Hi Andersen,
We have reached out to the creator of the plugin who simply does not have the time to develop it and offered to maintain it, we won’t be developing it any further only maintaining its current functionality with security and maintenance releases.
I have already been over the plugins code fully and there are only some small changes needed for PHP7 to stop some notices (it does not affect functionality) We will be updating the plugin very soon which will remove this notice.
Thanks,
Stiofan
Hi Patrick,
That is already wrapped inside a doc ready function, the 100ms is to allow the JS version to initialise, i tested in many situations and 100 was always worked, i will however change it to 250 for edge cases i was not able to re-create. Again this is just the time allowing the JS FA to initialise, not the load time of any file.
Thanks,
Stiofan
Hi Kathy,
I have set a task for this to be looked at, if possible we will add a direct renew link in the email.
Thanks,
Stiofan
WP login seems wrong, if u can provide as much info as possible we can help more.
Stiofan
Thanks for the info, this is fixed and will be in the next release of the theme.
Thanks,
Stiofan
No sidebar will work in next release.
Stiofan
Hi Richard,
It looks like u have something adding defer to all the JS files, this means they are not loaded immediately, but there is a JS function being called immediately which fails and breaks the rest of the JS including the maps…
Thanks,
Stiofan
Hi again,
GDv1 and GDv2 work very differently, your customisation might have worked in v1 as we only checked the place name query var and ignored all others, but in GDv2 we have moved to be more WP compliant, this is a great thing if you do things the WP way, it will make it much easier to make it do what you want, but bad news for your customisation.
We are here to support the advertised functionality of our products we simply can’t help with customisations, we don’t even do that for paid customers, our resources can be better spent serving the whole community rather than one user.
Thanks,
Stiofan
Hello,
The warning message in ur logs happens when a user tried to geolocate themselfs but it fails and goes to a manual location, it tries to ping that site to get generallocation for the IP but your hosting has the function used disabled, i have added a check for it so it won’t produce a warning in future if disabled by the host.
The logins no longer seem to work so i can’t check anything else, but i was reading up on things a but and think it might be related to the DB version, if you can provide working logins i can do some tests or you can ask your host to update to latest SQL version.
Thanks,
Stiofan
Hi,
There are a few reasons its not working, setting up a query var like that is more complex,you need to add query vars properly for them to work or they will just fail, one thing to note is that we no longer alter the global $post but instead use our own global $gd_post;, this will have the $gd_post->default_category but $post wont.
Why you are trying to do is considered a customisation and we don’t support customisations as it would take up far too much of our time, you are on the right track but a bit more code is needed.
Thanks,
Stiofan
The backend filters are being worked on, i don’t think they will make them in the next release but likely the one after that.
Thanks,
Stiofan
April 26, 2019 at 9:48 am in reply to: Not compatible with Elementor Single Templates (not applied to GD urls.) #483024Hello,
1. It depends on how you setup the Archive, if you are using the Elementor post archives then that replaces the gd_loop so you would not need the GD Archive item. If you are using the gd_loop then you can just edit the GD Archive Item page, either as normal or with Elementor but it is not confined to the Archive layout when editing so you don’t get a full visual representation when editing, just placeholders.
2. We need Elementor to add a hook so we can differentiate between post_types, i’m working on this but its a slow process.
Thanks,
Stiofan
April 25, 2019 at 6:50 pm in reply to: Not compatible with Elementor Single Templates (not applied to GD urls.) #482897Hello,
I tested this with the latest Elementor (pro) and it seems to work fine, the only way i could make it not work was by setting a custom page template for the GD Details page (normal WP settings).So please check these settings first:
1. GD Details template > Page attributes = “Default Template”
2. GD>Settings>Design>Details>Page template file override = Auto.If that does not help i would need to take a look myself.
Thanks,
Stiofan
Hi Gavin,
Those are standard WP revisions, you should find maybe plugin that will remove them https://wordpress.org/plugins/search/delete+revisions/
Thanks,
Stiofan
Hi Jeff,
This was a tricky one to track down, the issue is that i guess at some point you deleted the original email field for that CPT and when adding it back the field key was set to “contact_email” instead of “email”.
If you have cpanel i can change it for you, if not you need to change the field key in the custom fields table named “htmlvar_name” and then change the column of the CPT table to email also.
Stiofan
-
AuthorPosts