Greg

@romainprevot thanks for bringing this to my attention. I will take a look nonetheless in case there’s a better way we can implement the caching across different server set ups.

You can follow the issue here.

Awesome! Glad it worked out

Thank you for bringing this to my attention! I will try to get it working in site editing as well. You can follow here:

https://github.com/greghunt/tailpress/issues/11

I’m actually using Arc as well! Really enjoying it.

Please send screenshots of the issue if you can. Thanks!

@predawnhunter it seems to work fine on Desktop preview mode. Are you using it under Tablet or Mobile preview? If so, that’s a known issue documented in the README under DEVICE PREVIEW MODE IN BLOCK EDITOR

Oh, I see what’s happening. The class content-sidebar-wrap is in fact a reserved Tailwind CSS class name in the pattern content-{value}. This is the expected behaviour in that case.

I removed the hashing function of the classnames in 0.4.4 since it seems to be causing a lot of confusion with users. This should help in your particular case because it won’t hash the classname the first time around. Also, although TW will add a selector that matches content-sidebar-wrap, it shouldn’t have any properties so it won’t conflict with your theme’s use of it. Please try updating and letting me know if you still have this issue.

This is fixed in 0.4.4, thanks for bringing it to my attention!

@cprlrst please ensure you’re entering valid JSON. It’s not a copy paste from Tailwind docs since that’s Javascript.

If you need help validating your JSON you can try JSON Lint

That’s odd. Can you email me the website in question here: [email protected] and I’ll take a look.

“content-sidebar-wrap” shouldn’t be effected since it’s not a Tailwind class. Classes like m-0 or mx-0 can effect the margins.

Ah! Quite possible, I will check this for the 6.2 compatibility. Thanks for bringing it to my attention. I’ll notify you here when that’s fixed.

Hi @meryaguilar138 , perhaps that’s poorly worded. When I say it extracts, I don’t mean it removes anything, it simply looks at the classes on your page and compiles the CSS with that information.

It sounds like you may have a conflict with your Genesis theme. If they are using a class like “m-0” for example, Tailwind also includes this class which removes all margins.

We’re currently working on a way to scope TW styles under another name which would help with these kind of issues: https://github.com/greghunt/tailpress/issues/6

Only two hard problems in programming and one of them is caching! Glad your issue is resolved.

Feel free to reopen if there is still an issue.

Hi @mountainsmoke , I’ve released a fix for that in 0.4.3, the latest as of this comment. There was an issue with PHP 7.0 compatibility but it should work now.

Hi @toexceed , I’ve double checked the use of TW in theme files and it works fine on my end. Try clearing the cache first under Settings > Tailpress > Cache. If that doesn’t work, feel free to report back here but post some more details of your setup.