• Resolved mykillink

    (@mykillink)


    I am running Botiga on multiple sites, and had encountered an issue several months ago with the release of Botiga 1.1.3; which had re-written the website header, and also how Google fonts are imported.

    We worked through the bugs of 1.1.3 and now we have a new set of headaches with 1.1.9 – this update really did a number on our sites, specifically font colors and also (to a lesser extent) background colors.

    The thing I have noticed in inspecting the code is that the class which had been controlling these text colors is no longer being called:

    class=”has-palette-1-color-6-color has-text-color”

    So what happened to this class? They are still being declared on the front-end, but no longer have any corresponding CSS to make them display as intended.

    Question #1 for the developer:
    Is this a case of Customization options being reset every time we update the theme? Or is the customization options code being re-written with every release (such as we saw with the fonts in 1.1.3), leaving the existing setting obsolete?

    Question #2:
    I would genuinely like some guidance on how / where the class “has-palette-1-color-6-color” is defined.

    Here is an example, scroll down to Testimonials, where the H2 tag should be #ffffff:
    https://rizzolidentureclinic.ca/

    Here is a staging site with Botiga rolled back, scroll to the same Testimonials area, and notice the white headline:
    https://staging18.bluecitrus1.site-staging.xyz/

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi @mykillink ,

    Firstly, thanks for using our theme!

    Please note that the gutenberg/block editor color and background class name pattern were changed only in the version 1.1.8. Since then we didn’t touched in those class names anymore. So it is still a reflection from the 1.1.8 update and it is not related with the latest theme update (1.1.9 and 1.2.0) we released yesterday.

    So what happened to this class? They are still being declared on the front-end, but no longer have any corresponding CSS to make them display as intended.

    We sorry for this inconvenience. As I said above, it is a reflection from the 1.1.8 update. You need to edit the page in question, edit the ‘Testimonials’ heading (set color) and save/publish again to get the correct class name pattern rendered on the front-end.

    Question #1 for the developer:
    Is this a case of Customization options being reset every time we update the theme? Or is the customization options code being re-written with every release (such as we saw with the fonts in 1.1.3), leaving the existing setting obsolete?

    No, the customization options are not being reseted on every update. The root of the issue is that your pages are not rendering the correct class name. So you need to edit the page in question, edit the ‘Testimonials’ heading (set color) and save/publish again to get the correct class name pattern rendered on the front-end.

    If you don’t want to edit every page, you can try adding the custom CSS code below at Appearance > Customize > Additional CSS:

    .has-palette-1-color-6-color.has-text-color {
        color: #FFF !important;
    }
    

    Question #2:
    I would genuinely like some guidance on how / where the class “has-palette-1-color-6-color” is defined.

    Those color classes are handled inside ‘functions.php’ around line 169:
    https://snipboard.io/6Pembs.jpg

    Hope this helps!

    Let me know if you have more questions.

    Kind Regards,

    Rodrigo.

    Thread Starter mykillink

    (@mykillink)

    Hi @maaprote, and thank you for the quick reply.

    Understood that the change in question came about in version 1.1.8 and not 1.1.9

    As mentioned in my initial post, I have several sites running Botiga. As you may imagine, it is a real headache having them all go sideways at once due to a theme update (twice this has happened now); and also frustrating not knowing which new update will break these sites again.

    For me to go in and edit every page affected by these updates is also very counter-productive, as the text and background formatting have broken on several pages across multiple sites (and I haven’t touched on how this has effected the sites running a child theme).

    For future Botiga updates, how can we preserve the layout and formatting of our existing sites while keeping the theme updated? Any insight here would be helpful; Auditing and manually fixing multiple sites with each update is not sustainable.

    Hi @mykillink ,

    We totally understand and really sorry for not providing a backward compatibility to this specific color palette class name pattern. Looking to help you and fix the things, we are going to provide backward compatibility for this in the next version from Botiga. So my suggestion for now to you is sticky that old websites to a Botiga version prior to 1.1.8 and once we have released the next version, then you can update the themes to the latest version.

    Hope this helps!

    Kind Regards,

    Rodrigo.

    Thread Starter mykillink

    (@mykillink)

    Hi @maaprote,

    Thank you once again for the quick reply, I truly appreciate it and hope that with backwards compatibility added to future releases that I can continue to use Botiga without further incident.

    Final question – would you have any idea when the next release will arrive? Are these new releases announced via newsletter?

    Hi @mykillink,

    would you have any idea when the next release will arrive?

    Currently we don’t have a fixed date for this. But we’ll let you know when we have.

    Are these new releases announced via newsletter?

    No. When the update is availabel, you’ll a prompt to update in a form of link in themes administration screen (Dashboard > Themes).

    If you want to enable email notification for theme update, looks likely you’ll need additional plugin. You could find it in the plugins directory.

    Thread Starter mykillink

    (@mykillink)

    @kharisblank Thank you for the information, I look forward to the new update.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Formatting broken after update’ is closed to new replies.