The most recent update to the Filter Bar add-on changed a lot of the markup, added javascript functionality and messed up the existing select fields we had carefully positioned, styled, and customized functionality for. <\/p>\n
The filter drop-downs were looking and functioning just fine before this update, now see how they look (first screenshot). The next two screenshots show the markup around these select fields before & after the recent update. The change in the markup is massive!! There’s no longer any <select> field which we were targeting with js and css — you replaced it with a div with a new class and added a bunch more divs surrounding it.<\/p>\n
These changes you do may be nice for new users, but not for existing users. If you’re going to tell your users that we can customize the plugin files (and encourage it), then I think you should be much more careful about how your updates affect customers who have customized things. Changing the markup that extensively is often not backward compatible with sites that already customized it, and in my opinion is pretty reckless.<\/p>\n
This is the at least the 5th time we’ve had similar problems with your plugin updates breaking our customizations (not just Filter Bar, but the main Pro plugin, and Community Events)… within the past year since the site launched.<\/p>\n
We have completely blocked updates to any Tribe Events plugins from happening on the live site because there seems to be a really good chance that any update might break something in the layout. Every Tribe update now requires extensive local testing (and usually changes) to fix problems your updates have created. This extra time required to maintain sites with your plugins has a seriously questioning if we’ll ever use it on future sites (honestly, probably not).<\/p>\n
Please, consider your users who are customizing your plugin before releasing updates that may break layouts or functionality. If you insist on changing core layout markup (either in templates or via js), at least add a checkbox\/option to disable the new feature. Or if you need to add a new class to a dom element, fine, but don’t remove classes we may have been using.<\/p>\n
Signing off to dig around all the recent Filter Bar changes to see what broke this site…<\/p>\n","protected":false},"template":"","class_list":["post-1329759","topic","type-topic","status-closed","hentry"],"yoast_head":"\n