• Overall, I’m happy with this plugin, but in the ~3 months that I’ve been using it I’ve encountered two super annoying problems. First, it does not support the latest CSS syntax. Media queries such as @media (max-width: 1024px) { } will produce error messages even though that syntax is perfectly valid. I also get false errors when I use syntax such as .some-class-name:has(.another-class-name) { } even though that too is perfectly valid. For a paid plugin, I expect full support for the latest syntax. Instead, I got a support person who initially told me I was doing it wrong and only later admitted that this tool simply doesn’t support the newest syntactical goodies. The other annoyance is that the company is extremely slow to fix known bugs. Shortly after I started using this tool, I lost the ability to add or edit tags. The company admits this is a bug and even sent me the GitHub issue where they were tracking the fix. However, it’s been 6 weeks since the bug was identified and over a month since the Github issue was closed and the fix still hasn’t been released to production. Even accounting for the holidays, this seems too long. So this plugin is fine, but don’t expect full support for the latest code syntax or fast turn around times if you encounter any defects.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi @twb001 ,

    Thank you for taking the time to share your detailed feedback. We greatly value input like yours, as it helps us improve and prioritize what matters most to our users.

    We want to acknowledge the frustration caused by the issues you mentioned, particularly regarding the lack of support for the latest CSS syntax and the delays in releasing fixes. We sincerely apologize for any inconvenience this has caused.

    We’re excited to share that we’ve already taken your suggestion into account and updated our roadmap to include CSS/JS processors, such as Sass and Less. These updates will unlock advanced coding capabilities and ensure better compatibility with modern syntax, such as the :has() pseudo-class and updated media query formats. While the current syntax support works in many cases, we recognize the need to expand and modernize to meet your expectations.

    We’re also committed to improving our responsiveness to bug fixes and feature updates. Faster development cycles and more frequent releases are top priorities for us this year.

    Thank you again for your thoughtful review and for being a part of our journey.

    Warm regards,
    Pau.

    Plugin Contributor Verdi Heinz

    (@ver3)

    Hi @twb001

    Thank you for sharing your thoughts with us. Your feedback highlighted areas we could improve, and we’ve since made updates, including the ones mentioned by Pau in the comment above and the ticket we answered in November. These changes were made with users like you in mind, and we hope they’ve enhanced your experience.

    If you feel our efforts have improved things, we’d greatly appreciate it if you could revisit your original rating. Your support makes a big difference to us and our community.

    Please don’t hesitate to reach out if there’s anything more we can do for you.

    Best regards,

    Verdi Heinz
    Co-Founder

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this review.