Hi @palpatine1976,
Do you mean on the front end or the widget editor screens?
I haven’t found problems with either so can you please also provide a list of other plugins?
Regards, Jory
Hi Jory –
I mean on the front-end code generated from the widgets. Custom CSS classes added in the Widgets screen are no longer included in v1.5.0, but were working fine in v.1.4.0. For now I just rolled back to 1.4 and it’s working. This same behavior is noticed on 3 sites I run, all of which have slightly different themes and plugins. I guess it could be a conflict, but it was introduced in 1.5.
When I get time I can spin up a clean site and test, but wanted you to know. I see there are other similar posts in this support thread where people have noted this issue
Thanks!
That’s a weird one and since I’m not having this issue on both test and production sites I’m really curious to what it could be.
I’ll try to reproduct when I get back home. If you can provide me with any info of your installation let me know!
Thanks, Jory
It is weird! Maybe something from the 1.4 -> 1.5 upgrade (vs. a clean 1.5 install?) with the settings perhaps? Looks like there were a few extra features introduced in 1.5 – maybe one of them is conflicting with another plugin like Widget Logic or similar?
I just spun up a clean site, and 1.4 works, and then upgrading to 1.5 still works. So maybe there is a conflict (but a common one, since several other people reported same issue). I’ll poke around a bit more and see.
Thanks for testing this! Did you find anything?
Not yet.
Could you tell me any wp_options that your plugin creates? I was thinking I’d try to delete an existing install and try 1.5 fresh and see if that helps.
Just did a test with Widget Logic and it works fine.
This plugin has some integration logic in it and it still works apparently. See: https://github.com/cleverness/widget-css-classes/blob/master/includes/widget-css-classes.class.php#L648-L655
The metakeys this plugin creates is:
– WCSSC_options = Stores all options etc.
– WCSSC_db_version = Stores the current db version for the plugin
If you uninstall the plugin it should trigger removal of these options.
Hi @palpatine1976,
Did you find the conflict?
I’ve tried several things but can’t replicate your bug.
Please let me know!
Regards, Jory
Sorry – still not had time. Funny I just updated another old site of mine with no problem, so it is likely something on my end. I’ll keep digging and update this ticket if/when I find something!
No problem, thanks for the update.
If you can send me a list of plugins you use in the website with the bug I can test it as well. Let me know!
Hi @keraweb
Sorry for the delay. I’ve found the issue – it is a conflict with Widget Logic. Specifically, the widget_content filter.
Clean install (running 2017 theme) only plugins are WL and Widget CSS classes, latest versions.
If you go to the Widgets screen, and check the “enable widget_content” filter checkbox that WL creates, you will see all the CSS classes disappear.
Are you hooking that filter in the v.1.5.0 version?
Hey Jory – just checking you saw my note on this? I’m guessing one of the new filters you added in 1.5.0 isn’t playing nicely with the WL filter I mentioned. Please review and let me know – thanks!
Hi @palpatine1976,
Sorry, forgot to reply. Currently I’m on holiday so I will look into this when I get back (next week).
Regards, Jory
No worries @keraweb – enjoy the time off!!
