• Resolved RGB Lab

    (@rgblab)


    hi folks,

    in version 5.4.0 you have replaced source code for select2 w/ your wooselect script. so, now you’re shipping the plugin w/ duplicated wooselect script. sure it was not a mistake?

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

    (@conschneider)

    Engineer

    Hi there,

    now you’re shipping the plugin w/ duplicated wooselect script. sure it was not a mistake?

    I am not involved in the asset management of WooCommerce core, but maybe asset optimisation will come at a later point in time.

    Kind regards,

    Thread Starter RGB Lab

    (@rgblab)

    hi,

    can you pass this question to someone who is involved, because after woo update, code for select2 init in my themes stopped working…

    Thread Starter RGB Lab

    (@rgblab)

    hi,

    you can close this thread, we have contacted dev team on github, issue w/ wooselect is fixed in 5.4.1

    Fix – Update jQuery compatibility changes to trim functions to work with types other than string. #30074

    Plugin Support con

    (@conschneider)

    Engineer

    Hi again,

    you can close this thread, we have contacted dev team on github, issue w/ wooselect is fixed in 5.4.1
    Fix – Update jQuery compatibility changes to trim functions to work with types other than string. #30074

    Yes, the Javascript caused some undesired behaviour indeed. Good call, thank you.

    For next time you can also open a GitHub issue for such topics as it allows everyone to check the referred code instantly as well.

    Kind regards,

    Plugin Support Gabriel – a11n

    (@gabrielfuentes)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Select2 source files’ is closed to new replies.