Chosen styling and functionality not working after WooCommerce Update

[raj]

The styling and functionality for the Chosen dropdown styling and such appears to be broken when adding or editing events. See screen shot:
screen shot 1
These are the classes being added: ‘chzn-container chzn-container-single’

It appears to work fine on the Events Calendar settings page. See screen shot:
screen shot 2
These are the classes being added: ‘chosen-container chosen-container-single chosen-with-drop chosen-container-active’

I disabled all plugins and it appeared to break when only activating WooCommerce

[Brian]

Hi,

Sorry for the issues you are having. I can help out.

I was not able to reproduce the error on my site with the same plugins active.

Are you able to check in the Console Inspector of your browser when on that page to see if there are errors in it that might be causing this?

Let me know and we can go from here.

Thanks

[raj]

There are no issues/errors in the console.

Is there a reason why the classes ‘chosen-container chosen-container-single’ would be used on one page and ‘chzn-container chzn-container-single’ on the other? ‘chosen-container chosen-container-single’ doesn’t seem to have any problems.

When the page loads (new event/ edit event), Chosen initializes those fields briefly and then it’s removed.

[Brian]

For the single events dropdown this is the class I see:

chosen-container chosen-container-single

And this for the Events Settings:

select2-container select2-container-active select2-dropdown-open

We have both the Chosen and Select2 libraries. Not sure why we do not use just one.

However, since your classes are different it could be the result of a conflict.

You mentioned disabling plugins, but can you run through our entire testing for conflicts guide and see if that finds an issue:

Testing Conflicts With Themes and Other Plugins

Let me know what you find out.

Thanks

[raj]

It’s definitely an issue with WooCommerce. When I deactivate Woo everything works fine. It looks like Woo goes in after the page has loaded and changes the classes on that page. That’s all I can find.

[Brian]

How strange.

I have WooCommerce as well and not seeing the issue.

When I look at the scripts loaded on that page through Query Monitor I do not see any WooCommerce Scripts running.

So not sure what setting or coding you have that is causing the script to load.

You can use the Query Monitor Plugin to see all the scripts loading on that page to confirm that WooCommerc is running their chosen script:

Query Monitor – The developer tools panel for WordPress

Then we can go from there.

Thanks

[raj]

Query Monitor was clutch! The plugin that was buggering everything up was InfusedWooCRM. I deleted chosen.min.js from wp-content/plugins/infusedwooCRM/assets and that did the trick.

Thanks for your help.

[Brian]

Query Monitor is a nice debugging plugin!

I am glad to see you were able to fix this issue.

Since the issue is resolved I am going to go ahead and close this ticket. If you have a similar issue or another in the future, please do not hesitate to create a new ticket.

Thanks!

[Author]

Posts