• Resolved JensBNS

    (@jensbns)


    When updating from 2.3.0 to 2.4.2 I noticed that the visualization of the form at the product page was gone and horrible.

    So I went to the back-end and noticed that not only all the color settings has been reset, noticed that the default (suggested) values are not shown when the form is rendered.

    Before update:

    After update:

    And the worst part is that this is not the first time I got issues with the form after I update the plugin.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support mouindi

    (@mouindi)

    Hi @jensbns, sorry to hear that you have faced this issue.

    We have added some modification in our last update, however we are running migration to sync old settings with new.

    It might happen for your site the migration didn’t run. Not to worry, deactivate the plugin and activate this again. After that check the form field.

    Keep us posted.

    Thread Starter JensBNS

    (@jensbns)

    So every time I update this plugin, I need to deactivate and reactivate this plugin?

    Plugin Support mouindi

    (@mouindi)

    You don’t need to do this everytime @jensbns.

    This is only to run the migration, as previously it didn’t run.

    Thread Starter JensBNS

    (@jensbns)

    When you are referring to “the migration” do you mean the migration from version 1 to version 2?
    Because I already did the deactivation and reactivating of the plugin for another issue with the subscriber’s amount.

    And when I downgrade from 2.4.2 back to 2.3.0 everything works like before.
    So if there was another breaking migration between these versions and there were no mentions in the changelog that I should deactivate and reactivate the plugin. How should I know that I need to do this?

    Another option for me would be to code the styling in my style sheet.
    But I discovered that the classes for the input and button were changed between version 2.3.0 and 2.4.2. So there is no guarantee that even this solution is future-proof.

    Plugin Support mouindi

    (@mouindi)

    If you review our changelog for 2.4.0, you’ll notice that we’ve updated the coding structure, which is why we’ve included migration here as well. Normally, when you update the plugin, migration should run automatically.

    However, in your site’s case, the migration didn’t initiate. That’s why we’ve requested you to deactivate and then activate it again.

    Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Default Form Customization values not visable’ is closed to new replies.