Your datepicker CSS breaks features of another plugin (AdRotate)
-
You have a nice plugin. However, it interferes with another plugin we use, namely, AdRotate (and probably other plugins as well). We’ve found that if your plugin is active, it isn’t possible to set dates in AdRotate, so we need to deactivate your plugin whenever we need to set dates in AdRotate.
The problem seems to be in your file foundation-datepicker.min.css where you set properties for the generic datepicker CSS class (including display:none). The key point is that your CSS gets loaded on all admin pages, so it affects admin pages of other plugins. And because you specify display:none the datepicker fields in other plugins that use a datepicker routine can become invisible.
If you can simply rename your custom datepicker styles using a name that’s unique to your plugin, maybe something like wpdv-datepicker, the problem ought to be solved.
- The topic ‘Your datepicker CSS breaks features of another plugin (AdRotate)’ is closed to new replies.