Plugin breaks advanced iframe plugin

  • mdempfle

    (@mdempfle)


    10 months, 1 week ago

    Hi,

    I’m the author of advanced iframe. A user of mine just reported that using your plugin cause issues with advanced iframe.
    The problem is that you add shortcode attributes to my plugin! My plugin does check that all used short code attributes are known so users find e.g. typos in their setup quickly.
    Now my check reports

    The following attributes are unknown or cannot be read properly. Please fix or remove this attributes:

    • extended_widget_opts_block=””
    • extended_widget_opts=””

    I think you should NOT modify shortcodes from other plugins. Please fix this on your side asap.

    Thanks, Michael

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter mdempfle

    (@mdempfle)

    10 months, 1 week ago

    Hi, I also tried to reproduce this on my systems. With the default settings I could not reproduce it. Maybe the user has made some selections which cause that the 2 settings above are added. Maybe he also uses the pro version. I could only test with the free version.

    Hope this helps to find the issue.

    Best regards, Michael

    Thread Starter mdempfle

    (@mdempfle)

    10 months, 1 week ago

    I got this from my user:

    I’m only using the free version of Widget Options – specifically version 4.0.6.1 (latest). The following features are enabled:

    Classic Widgets Screen, Gutenberg Page & Post Block Options* , Pages Visibility* , Devices Restriction, Custom Alignment, Hide Title, Classes & ID* , User Login State, Display Logic*. Within those only the asterisked options have configurable features – these are all unticked except the following:

    Page Visibility – all features ticked

    Classes & ID – only Enable ID Field ticked

    Hope this helps, Michael

    Plugin Author Mej de Castro

    (@mej)

    10 months, 1 week ago

    Hi @mdempfle,

    Thanks for reaching out. We have now relayed this to our development team for further troubleshooting. We will let you know once the issue is fixed.

    Regards,
    Mej, from Widget Options team

    Plugin Author Mej de Castro

    (@mej)

    8 months, 2 weeks ago

    Hi @mdempfle,

    I hope you’re doing well. We want to let you know that we have an update for you.

    We wanted to provide you with an update on the issue you’re experiencing with the iFrame plugin. Our team has attempted to replicate the problem, and we found that the error reproduced was not a fatal error. Our developer noted that while the Widget Options plugin does not register this as an error, the Advanced iFrame plugin does.

    Could we possibly request some filters or hooks from the Advanced iFrame plugin to address this issue within our plugin? We have included screenshots below for your reference.

    Reproduced/replicated issue: https://snipboard.io/G9l4UE.jpg
    Code References: https://snipboard.io/o2Xq6E.jpg
    https://snipboard.io/oErltM.jpg

    Best Regards,
    Mej, from the Widget Options Team

    Thread Starter mdempfle

    (@mdempfle)

    8 months, 1 week ago

    Hi,

    Please see my first post again. There I exactly write what you also found out.

    The problem is that your plugin modifies the shortcode attributes of MY plugin. So it seems you globally register your settings to any other plugin.

    My plugin has a check that only known attributes are allowed. The reason is that many users make typos in the shortcode attributes and then tell me my plugin does not work properly.

    So my main question is – Why do you add your settings to my plugin? I think you use a hook to enhance shortcodes. And unfortunately not only enhance yours but also mine. Not sure how I should provide a hook/filter as you add additional properties.

    Best regards, Michael

    Thread Starter mdempfle

    (@mdempfle)

    8 months, 1 week ago

    The code you send in the screenshot is checking for valid attributes of my plugin. It should actually report invalid attributes like it does.

    Best regards, Michael

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Plugin breaks advanced iframe plugin’ is closed to new replies.