Conflict with Widgets that use multi-select

  • Resolved thisismyalterego

    (@thisismyalterego)


    7 years, 12 months ago

    Hey there,
    your plugin does what it should till the moment it’s used on a widget that has multiselect options. When your plugin is used on these widgets all of the selected options are gone after pressing the “save” button.

    Here is an example:
    Before submitting:

    After submitting:

    Everything in the “category” selection field is unselected after submitting.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter thisismyalterego

    (@thisismyalterego)

    Update:
    I’ve found out that the categories-array was converted into a comma-separated string in this widget. So what I did to your code was to implode the category-instance via comma. Now it works.

    So I guess converting arrays to strings is nothing that all the widget-devs do and this specific “error” was based on some special code by the other widgets author.

    This can be marked as fixed though…

    Plugin Author Daniel Iser

    (@danieliser)

    @thisismyalterego – Glad you found a fix, just to confirm your saying they are doing something out of the ordinary, not us?

    In which case were you able to determine why our plugin being enabled caused theres to stop functioning when it worked previously? Are we converting their array to a string somehow? I generally write code to only touch our own data and never any other so that would be strange.

    Let me know if this is something we can address from our end.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with Widgets that use multi-select’ is closed to new replies.