Conflict with Toolset plugins

Hi @dave_garlock

I hope you are doing well.

The fix should be included in the free version too.

Could you let us know which version of the toolset plugin you are using and the correct steps to replicate so we can try to replicate the problem?

Best Regards
Patrick Freitas

Thanks. We were using:
Smush 3.8.4, and the most recent version of all the Toolset plugins.

To reproduce the error, go to the backend editor screen on a custom post type. In the browser console, it will report an error like the one below, and break some backend editor functionality. Like I said, adding the patch you put out fixes the issue.

Uncaught TypeError: this._setOptionDisabled is not a function
    at d.<computed>.<computed>._setOption (jquery.fancytree.ui-deps.js:449)
    at d.<computed>.<computed>.s [as _super] (widget.min.js?ver=1.11.4:11)
    at d.<computed>.<computed>._setOption (button.min.js?ver=1.11.4:11)
    at d.<computed>.<computed>.d.isFunction.a.<computed> [as _setOption] (widget.min.js?ver=1.11.4:11)
    at d.<computed>.<computed>._create (button.min.js?ver=1.11.4:11)
    at d.<computed>.<computed>.d.isFunction.a.<computed> [as _create] (widget.min.js?ver=1.11.4:11)
    at d.<computed>.<computed>._createWidget (widget.min.js?ver=1.11.4:11)
    at new d.<computed>.<computed> (widget.min.js?ver=1.11.4:11)
    at HTMLButtonElement.<anonymous> (widget.min.js?ver=1.11.4:11)
    at Function.each (load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate&ver=fd2fd4ade45fc8e3399a2f995106fcc7:2)

Hi @dave_garlock,

Smush 3.6.1 included a fix for this but I’m afraid that I don’t have a latest version of Toolset Types in order to check why the issue might be back.

Could you get in touch with us via our contact form so we can see how we could debug this further:
https://wpmudev.com/contact/#i-have-a-different-question

Send in:

Subject: “Attn: Predrag Dubajic”
– Link to your WordPress site
– Link back to this thread for reference
– Any other relevant urls/info`

Cheers,
Predrag

Actually, I updated my wordpress version, and the problem went away (even without the patch). So, I guess the fix you added didn’t work with an older version of WordPress, but does with more recent ones, so I would consider this issue solved. Thanks for your help!

Hi @dave_garlock,

Glad to hear it’s working fine now. I’m marking this thread as resolved. Please feel free to re-open the thread if you need further assistance.

Best Regards
Nithin