Conversation
|
Thanks. I don't see 'caldera' in any of Postmatic's CSS, and only Still, if you're not in a hurry I'd feel better if I could check out this branch and do a few tests with it. |
|
@cyberhobo That line is 100% going to break Postmatic. There is no longer a function called I had to change the CSS and JS prefixes beacuse Ingot's use of Caldera Modals and Caldera Forms' almost identical modal system were clashing, which was embarassing... |
|
@Shelob9 how about you tag the current master with a version we can depend on in Postmatic for now? Then you could submit a Postmatic PR that works with the new version 😁 |
|
@cyberhobo Use tag 1.0.1 https://github.com/CalderaWP/caldera-modals/releases/tag/1.0.1 Once @Desertsnowman merges this I'll tag it as 1.1.0 and then PR postmatic. |
|
Will do, thanks @Shelob9. On Thu, Jun 2, 2016 at 3:52 PM, Josh Pollock notifications@github.com
|
|
For reference Postmatic 2.0.4 will include caldera-modals 1.0.1: postmatic/postmatic-basic@005e134 |
To fix issue #5 in Ingot I switched to a fork that changes "caldera" to "calmodal" in JS/CSS. Sensible fix, but I worry beacuse we used these modals in Postmatic and called them programmatically that if we merge this, it will break the optins in Postmatic, so let's discuss this with @cyberhobo before merge