thomas82

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:

• WHY are some translations after the update properly, and some others not?
• WHY is the custom CSS no longer applied after the update?
• WHY the update overwrites changes in the display and order of items on some pages?

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.