Greg

Hi @jembatan , I’m not sure what modal or slider you’re referring to since neither of those components are included in this plugin.

Regarding the error, the source map error is harmless and nothing to worry about. It looks like you have a JQuery initialization error.

@romainprevot this editor won’t save invalid JSON, so if you enter invalid JSON it never actually gets saved and reverts to the previous working version. I suggest you type in your configuration one line at a time or paste in your config as a whole into a JSON linter and edit in there to get it working. Once it’s valid if you paste it into the plugin and save there should be no problem.

Please note that the default Tailwind config is written in javascript and not JSON, so it’s not a copy paste situation from their docs.

There are plans for a better config editing experience here.

• This reply was modified 1 year, 12 months ago by Greg.

Hi @yarogo, thanks for bringing this to my attention. Unfortunately, this is a bit of a pickle since the plugin supports arbitrary variants just fine. The issue is with WordPress and the use of the Advanced Classes field. This field will escape user input and so the characters used in arbitrary variants get escaped. Simply deactivating this functionality would be a major security issue. I’ll have to think of some sort of work around.

I’m open to any ideas here

Hi @tctrautmanslp , good question! Please look at the documentation on our companion API page, it explains how to configure the supported plugins.

I noticed a JS error on the frontend that could lead to us. Please upgrade to the latest 0.4.2 – I think that should fix it.

@dreu91 your issue is a separate one, I replied to your email. In summary, you’ll need to make your styles more specific. Usually, with Tailwind the way to do this is the “prefix” option in the config. Unfortunately, the library we’re using to compile TW doesn’t support this option at the moment. We’ll be sure to implement it as soon as it does.

Hi @cvladan , could you post some more details here? A screenshot of the styles not being applied and the version of TailPress & WordPress, please?

Hi @catskill , this is expected on the first page load, as its part of the caching process. Whenever you change the classes on a page, the first request to it triggers the generation of the CSS in the background. In order for the page to display properly while this is happening, the plugin adds the styles via javascript and uses a hashing function for the classnames which is what you see.

Long story short, these classes should only appear once on first load. Any requests after that should work as expected. I’ve checked your page and it seems to be working correctly with the proper class names and applied styles.

I will work on a potential solution on this Github issue if you’d like to follow.

@badouxinternetprojects, unfortunately this isn’t how the plugin works. It watches your classes used in your HTML, not your CSS.

I will keep it mind if I come across a way of doing this. Here’s a Github issue to watch.

I suggest you integrate Tailwind in your theme with an actual build step for this. If you need to watch for classnames from WordPress in your build, I will be adding an option to generate a text file with all of your WordPress classes. Then you can reference it in your build step. This feature can be followed here.

@cprlrst this is probably because their color picker is using a tailwind class and it’s interfering with their expected styles. Could you please email me a copy of the plugin you’re using here, please: [email protected]

I did a quick search and it’s a premium plugin I don’t have access to. I’ll test it out once I get it and see if there’s something to be done.

@ranx2k it sounds like it’s working correctly up until you say the page isn’t styled. Can you please go to a page with your TW classes applied in incognito mode, then refresh the page after a few seconds. If you look at the source code after refreshing you should have a <style id="tailpress"></style> with your TW CSS in it.

If not, I’ll need some more details about your specific installation. Please email me at [email protected] with further details, like your theme and source code of the page in question.

Marking resolved

I’ve added a notice in the readme!

Thank you for this! It’s resolved in the latest version 0.3.2

Hi @won5572 thanks for that suggestion! In the latest version 0.3 I moved to a server side generation of CSS instead of the client side since it was causing several issues that were hard to control including a potential security vulnerability (CSS injection).

In the case of Windi CSS and your suggestion, unfortunately that would require a NodeJS runtime which we don’t have in WordPress. Instead I made my own server side Tailwind API here. Feel free to use for your cases directly too, it’s completely free.