Update to 2.0.13 breaks custom styles through different HTML structure of blocks

  • Resolved fabro1909

    (@fabro1909)


    2 years, 4 months ago

    We have big problems with the plugin since the update to the new major version (2.1.3; Spectra).
    Currently, the only option for us is to roll back to the old version of the plugin (Version 1.25.4)
    The problem is that after the update the HTML structure of blocks has completely changed, so that our custom CSS does no longer work.
    Is there any way to update the plugin without changing the HTML structure of the blocks? Or any other solution?
    As it is currently, the plugin is unfortunately no longer usable for us, since we would have to rebuild everything at great expense.
    Many thanks in advance.
    fabro

    • This topic was modified 2 years, 4 months ago by fabro1909.

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

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hello @fabro1909,

    Thanks for writing to us.

    We’re sad that this update has caused you issues. Our team worked hard and tried its best to make it a smooth transition from prior versions to 2.0 and ran an extensive public beta testing program for several weeks. However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

    There is a new release of Spectra 2.0.13 that has fixed the issues that came up with the latest updates.

    After updating, please be sure to regenerate the assets. We do this automatically after the plugin is updated, but just to be sure, go to “Spectra > Settings > Asset Generation > Regenerate Assets” and press the button as shown here:https://share.bsf.io/9ZugNRdO?method=GET.

    Also, empty cache and hard reload while on the editor screen. Here’s how: https://share.bsf.io/2NumNvZ2.

    Please let me know how this goes.

    Regards.
    Judith.

    Thread Starter fabro1909

    (@fabro1909)

    Hi Judith,

    many thanks for the reply.
    We already have Version 2.0.13 installed and of course tried to regenerate the assets manually and deleted cache and hard reload.
    This has not resolved the issue.

    As already described above our problem is that it seems as if the whole HTML structure of your blocks have changed after the update.
    This causes our custom styles to break.

    Our question is if there is any way to keep the old HTML structure of the blocks?

    BR

    Hello @fabro1909,

    Thanks for writing back.

    This would depend on the legacy blocks you are using.

    Please create a support ticket with us from here so that we can help you out in a better way.

    Looking forward to hearing from you.

    Regards,
    Judith`

    I have the same issue. The blocks no longer accept css input and are no longer formatted correctly. The basic alignment options in the plugin blocks no longer work.

    Hello @cmba,

    Thanks for writing to us.

    Please create a support ticket with us from so that we can help you out in a better way.

    Looking forward to hearing from you.

    Regards,
    Judith`

    Hello @cmba,

    It’s been a while since we heard from you.

    So we are going to mark this as resolved. Please feel free to open a new thread in case of any other queries.

    Regards.
    Judith.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Update to 2.0.13 breaks custom styles through different HTML structure of blocks’ is closed to new replies.