Hey @skylabb,
That usually happens when blocks don’t support the basic Gutenberg standards of using their class name in both back & front-end.
Unfortunately, if blocks don’t handle the classnames properly then our plugin really can’t do it.
If you try to use it with any Core or Third-Party blocks that use WordPress’ API properly then it should work.
You should be able to try it with our Otter Blocks: https://ww.wp.xz.cn/plugins/otter-blocks/
Let us know your thoughts. 🙂
Regardless, we will see what we can do and let you know how it goes. Thanks for reporting.
Thanks for the response, Hardeep.
It can be very tricky that this plugin relies on other third party blocks to comply with WP API standards as you can’t control what they do and be limited to the few blocks that do.
It’s a great approach though I hope you can find a way to work around this limitation. How about providing an alternative fall-back CSS injection method that can work more universally with all blocks?
Added back one review star for the quick and constructive response.
-
This reply was modified 5 years, 7 months ago by
skylabb.
It’s a great approach though I hope you can find a way to work around this limitation. How about providing an alternative fall-back CSS injection method that can work more universally with all blocks?
That’s pretty tricky as we can’t access block contents any other way. But regardless, we will take a look at this and see how we can fix it.
Added back one star for the quick and constructive response.
Don’t mind about the ratings. We don’t care about the stars as much as we care about helping people. 🙂