Home Forums WoodMart support forum Troubles when updating to new version

Troubles when updating to new version

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #291557

    webreturn
    Participant

    Hi, last update has many troubles with updating.

    On a few websites we see after updating the theme to latest version and then appereance > update plugins that the wp bakery and/or the woodmart core plugin are deactivated?

    And we have to go to theme settings and resave the theme settings to make the options visible? This wasn’t before updating the woodmart theme. We see this in many installations.

    And new template version had a bug, see attachment. Things are going wrong and are not the same. We have placed an older version of the theme back. Please how can we fix this?

    Best regards, Tim

    Attachments:
    You must be logged in to view attached files.
    #291568

    Artem Temos
    Keymaster

    Hello,

    Could you please disable all plugins that are not related to our theme and provide us your admin access so we can check it?

    Note that if you have some changes made in the child theme you need to read our 6.0 update details and revise all the customization made in the code https://xtemos.com/docs/woodmart/faq-guides/woodmart-update-6-0-explained/

    Thank you in advance

    #294408

    webreturn
    Participant

    Hi,

    Theme option ‘Deprecated CSS classes from v5.x’ does not work properly, because classes that existed in the main navigation are no longer present.
    This is the case for more parts of the website. Since there are so many class changes in update 6.0, are we supposed to go through thousands of lines of custom CSS?

    This is not fair, in our opinion. We are very happy with your theme and we really appreciate the effort put into optimizing the theme for performance!
    However, we have like 25 projects that use Woodmart, and some contain over a 1000 lines or 30KB of custom CSS.

    Could you provide a tool that uses the list of class changes to automatically make all the classes match up with the refactored CSS and remove classes from queries in case they are not added in version 6?
    Maybe put the a page at woodmart.xtemos.com, just so people can paste their custom CSS and that it will return the refactored custom CSS?

    I think a lot of people would find this handy, because it would save them a lot of time.
    Some people may simply choose not to update their Woodmart theme, because it breaks their website, which is not good if you want to keep your customers.

    Kind regards,
    Webreturn

    #294609

    Hello,

    Unfortunately, it is no possible to make it automatically.

    We can give you the table with the old and new classes. Please check the classes with you custom CSS code and replace: https://docs.google.com/spreadsheets/d/1b_PBt1itPNby4mkpeV_VcRrQHPHjtuF9DIs8jJE0maQ/edit#gid=0

    Best Regards

    #295177

    webreturn
    Participant

    Hi,
    We are really not happy with this. This costs us days of work with 25 installations. We have update subscriptions with customers and we can not make any money for this only costs. Please why you don’t have a good think about this? Websites have child themes and custom css styles?? Please don’t do this any more, I am really disappointed in this.
    Regards, Tim

    #295219

    Bogdan Donovan
    Keymaster

    Hi,

    Since release of the Woodmart theme, and we constantly try to optimize theme performance from update to update. But after Google announce that in mid of 2021 site page speed performance will start to be a one of the main valuable factor in Google search ranking, we were forced to make big changes in our theme to stay competitive on theme market and provide best scores for users who care about page performance and search engine optimization.

    Before 6.0 update, we prepared a detail migration guide to new version, special update transition option with main deprecated classes and correspondence table with full list of the 500+ classes that was changed. Unfortunately, this does not guarantee a smooth transition for sites with a lot of customizations and a change in custom code may be needed. We apologize for the current situation, but these changes were necessary in order to provide the best results for our clients.

    Our next update will not contain such critical changes in HTML structure and class names. If you have any questions please feel free to contact us.

    We hope for your understanding. Best Regards

    #295235

    webreturn
    Participant

    Hi,

    Oke, but you don’t have any converter from old css to new css? We have big css style sheets.

    Please can you help us soon with below?

    After the latest update we are running into some font issues, see screenshot http://prntscr.com/13e1775. I’ve read the part about the fonts in https://xtemos.com/docs/woodmart/faq-guides/woodmart-update-6-0-explained/), we made them matched but the font remains different. Can you help us out?

    Google fonts
    Prior to our 6.0 update, when you select any Google Font in our Typography settings, all its variations and font-weight are loaded on your website. We made it work this way to ensure absolute compatibility with all CSS rules on your website. But it is a bad approach in terms of performance. So now we load only 2 font weights by default: 400 and 700 or 300 and 600 (it depends on font). By doing this, we have reduced the number of font files loaded by 50-70% in different situations.
    INFO. Note that you still can load any font-weight you need on your website. If you see that some font-weight is missed, just go to Theme Settings -> Typography and select the desired font-weight for some of the font groups.

    #295285

    Bogdan Donovan
    Keymaster

    1. Unfortunately, there is no possible way to make such converter. But since the main change in theme styles in 6.0 update is replacing theme prefix from woodmart- to wd-, simple find and replace method will fix 80% of the custom code. For example, if you make changes for logo with CSS selector .woodmart-logo, renaming it to .wd-logo will fix this issue. Full list of renamed classes can be found here (https://docs.google.com/spreadsheets/d/1b_PBt1itPNby4mkpeV_VcRrQHPHjtuF9DIs8jJE0maQ/edit#gid=0)

    2. Earlier all font-weights were loaded on site pages even when they were not used increasing font size in several times. Now only font-weight that is configured in the Theme Settings => Typography section are loaded on site pages.

    In order to apply the font-weight that is not configured in the Theme Settings, you need to set this font-weight in the Theme Settings => Typography => Advanced Typography, by using this custom selector: .wd-load-font-weight-400. Same selector can be created for any font-weight from 100 to 900. (screenshot https://prnt.sc/13e6l7y)

    Here is the documentation providing more detailed instructions about advanced typography: https://xtemos.com/docs/woodmart/advanced-typography-settings/

    Best Regards

Viewing 8 posts - 1 through 8 (of 8 total)