Mailchimp plugin conflicts with Catalyst/Dynamik

Hey there,

Thanks for writing in. Could you describe a bit further what specific conflicts you’re seeing when both are activated? If possible, do you have a link to a live site with the conflict displaying, or a screenshot showing the issues you’re seeing?

Look forward to hearing back!

-tk

I don’t see any what to upload a screenshot.

Details:
Caltalyst has a frontend css editor option. When in use, you can edit css in a pop-up window right on the page you’re working on.

With Mailchimp activated the pop-up window becomes so transparent as to be useless, so when MC is activated I can’t use the css editor.

Does that make sense?

I have a screenshot but don’t see any way to attach it to this message.

Here’s a link to the screenshot elsewhere
https://www.beyondbones.com/wp-content/uploads/2013/02/Screen-Shot-2013-02-24-at-7.42.22-AM.png

Hey there,

I wasn’t able to obtain Catalyst in order to test the issue in my local environment, but it does sound like there’s a CSS conflict with our plugin and the popup CSS editor in Catalyst.

One option, as you alluded to, is to deactivate the MailChimp plugin whenever utilizing the popup CSS editor. While this isn’t ideal, this is one option that you would have in moving forward.

The next option would be to identify the particular bit of CSS that’s causing that to happen. In order to do that, you’ll want to see what CSS is active when using the popup editor. One way to do that would be to use the built-in developers tools on your browser, like ‘inspect element’ in Google Chrome. To use this tool, open up the Catalyst editor as it’s displaying transparent, then right click on it and select ‘inspect element’. You can then see all CSS that’s active on that window.

Try disabling each of the checkboxes besides the various CSS to see which particular CSS declaration is causing the conflict to occur. Once you’ve disabled the ‘conflicting’ CSS, you should see the editor return back to a normal opacity.

Once you’ve identified the conflicting CSS, you can then make changes to the plugin’s code if you wish (this can be doen from the WP-Admin). Also, if you’d like, feel free to pass back on to us what particular CSS declaration is causing the conflict and I’d be happy to pass that along to our developers to make them aware of that potential interaction. This will then be considered as an improvement to make in the next iteration of the plugin.

If you have any further questions, feel free to write us back and we’d be happy to help!

-tk