This topic contains 7 replies, has 2 voices, and was last updated by 
Stiofan O’Connor 8 years, 9 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketHello,
We have the following 3 problems, which have occurred after update from version 1.4.3 to version 1.5.0:
1. Faulty translations
2. Incorrect CSS formatting
3. Incorrect display and order of items on some pages
In previous updates of GeoDirectory we found that there are problems with the translations after each update. Although these are stored in the folder /wp-content/languages, as described in the documentation, you have to manually change some translations after each update, because they are overwritten when updating.
When updating from 1.4.3 to version 1.5.0 two more problems occured. First, the CSS formatting, which is totally messed up, although it is inserted as custom CSS in Avada and secondly, the appearance and order of items on some pages are no longer correct. For all mentioned problems, see examples in the attached screenshots.
Fortunately, the affected website is still under construction, but if that would happen on the fly, that would be an absolute disaster. We have recommended GeoDirectory to the customer because it has offered the most opportunities compared to other directory plugins, but if you have to bring the site back into shape after each update…
Can it be that we missed something or did something wrong?
We ask for immediate help and will provide you with an administrator access to both GeoDirectory versions 1.4.3 and 1.5.0 for comparison.
Furthermore, the customer missed in the GeoDirectory search box the real time search, or the automatic adjustment of the search criteria to the search parameters, such as in the WordPress theme Listify. Is it possible to realize a similar search function with GeoDirectory or is it possibly provided in future updates?
Many Thanks.
Please provide wp-admin and ftp details in a private reply (only staff can see private replies)
Thanks,
Stiofan
A lot has changed since then, most things though look like custom CSS that is included in the page, have u seen this update?: https://wpgeodirectory.com/docs/avada-compatibility-header-php/
Stiofan
Hello,
we know that a lot has changed since then, but that can not be a justification that after each update the website has to be re-translated correctly and rigged.
We have renamed the file header.php in the Avada-Child folder, but obviously that is not the solution for the three problems mentioned.
Hi Thomas,
I have been through all problem and most of the problems are caused by custom CSS you have added, this is something we can not account for all the time.
All the changes we have made have been to make the theme work better with Avada and to work better in general. there has been 4 months between your versions and the only problems are a few little CSS problems, since then even Avada has changed alot, we even managed to get them to add a hook specifically for our needs to make GD 100% compatible.
I can understand your frustration but the after looking at the problems it’s really not that bad, i doubt it’s more than 3-4 lines of code need tweaked.
Let me know if you want me to make the changes for you to make it look like your 1.4.3 version, i can’t be fairer than that 🙂
Thanks,
Stiofan
Most of the problems are caused by custom CSS we have added?! How can faulty translations or the wrong display and order of items be caused by custom CSS?! If you think the only problem is to make it look like our 1.4.3 version, that’s wrong and no help at all.
To put the things right, only the CSS formatting may be associated with custom CSS. The altered display after the update are not caused by OUR custom CSS, which was working perfectly, but in that the existend custom CSS no longer works, because of changes made by YOU.
You say, that all the changes you have made have been to make the theme work better with Avada, but in fact it’s obviously working worse.
You doubt it’s more than 3-4 lines of code need tweaked? Well it’s much more than 3-4 lines, but that’s actually not the problem. The point is, if we can’t be sure how will the website look like after an update and how much time and effort we have to invest each time in order to bring things back to normal, then that’s not a viable solution in the long run.
The right questions are:
You only have to find out the correct answers to this questions and we would like to help you in our own interests. Here you have a chance to compare two parallel versions of GD on a web page to determine where the problems come from in order to fix them in the future for all of YOUR customers.
I am here to help, not have an argument, we did not set out to break your theme 🙂
WHY are some translations after the update properly, and some others not?
There could be many reasons, all of which would have been implemented to help other users in the long run.
WHY is the custom CSS no longer applied after the update?
For example search we added a class “search” which is used by Avada and styles thing more naturally, this is causing problems with your custom CSS, our changes proabley helped 100’s and broke your custom CSS.
WHY the update overwrites changes in the display and order of items on some pages?
This i am not sure, i assume you would not have edited core but made changes in your child theme via hooks, i would need to know how you applied this.
Thanks,
Stiofan
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketGet the latest news, tips, and exclusive content directly in your inbox.
Confirm your email address, and instantly receive the discount code :)
