-
AuthorPosts
-
December 11, 2019 at 4:56 am #1164701
Hi,
After the upgrade the tabs of the product pages have been changed. There is a child theme on the site. What would be the reason?
I have shared 2 images and the actual page in private section.
Thanks
December 11, 2019 at 5:27 pm #1164888Hey ilkbaharkunduzu,
Please have a look at the following thread:
If you need further assistance please let us know.
Best regards,
VictoriaDecember 11, 2019 at 5:38 pm #1164895Hi,
I added the code below and emptied caches. The tabs have not changed. What should I do?
#top div div.product .woocommerce-tabs ul.tabs li a { white-space: nowrap !important; }
Thanks
December 11, 2019 at 6:45 pm #1164941Hi ilkbaharkunduzu,
Could you please give us a link to your website, we need more context to be able to help you.
Best regards,
VictoriaDecember 11, 2019 at 7:07 pm #1164954Hi,
I have shared before ( before the update) and after ( after the update) images of the specific problem and the related link of that page to my website in private content. I shared again. Could you please check that? The problem is the same for all the product pages.
Thanks
December 11, 2019 at 8:43 pm #1164983Hi ilkbaharkunduzu,
https://share.getcloudapp.com/8LuwZY75 The code works, you might have some errors in your quick css or you need to clear the browser cache.
Best regards,
VictoriaDecember 11, 2019 at 9:06 pm #1164995Hi,
The problem is still there even if I cleared the cache. However, I have to purge the zone in keycdn. I guess that may cause the problem. I will wait and inform you.
By the way, before you looked at the links I posted that in another thread. Sorry for the duplication.
Thanks
December 12, 2019 at 3:51 am #1165038Hi,
Thank you Victoria. There is not any problem for now. However, after the upgrade 6.4, should I delete the code from quickcss section?
Thanks
December 12, 2019 at 7:43 am #1165103Hi,
You can comment it out instead of flat out removing it.
Best regards,
Jordan ShannonDecember 12, 2019 at 4:00 pm #1165228Hi,
I can do that yes but in time the number of the lines will go to the stratosphere and finding a line of codes would be hard. Thank you for the suggestion but the question is should I. I guess I can but I have to be sure if 6.4 solves that or not.
A suggestion for you.
There are some problems because of the updates and before enfold team fixes those, you kind of solve those issues before the upgrade. After the release those may be in changelog if the problem is really a general issue, we can read and find those and delete or comment out for historical purposes. However, if one relese solves a problem that has been solved by the codes we paste into quick css, you can kind of tag that specific thread and linked to the specific changelog and inform the participants via mail then they delete or comment that out. This could be more clean and systematic. We can name those threads “TagCL”. Like for many threads, inside we can find that the problem no longer occurs after the specific release.
Thanks
- This reply was modified 4 years, 11 months ago by ilkbaharkunduzu.
December 15, 2019 at 12:53 pm #1166032Hi ilkbaharkunduzu,
Glad we could help :)
Well, after the update you can comment the code out and see if it works without it and then delete it if it is unnecessary anymore.
If you need further assistance please let us know.
Best regards,
Victoria -
AuthorPosts
- You must be logged in to reply to this topic.