Hi,
After Winden 2.8 introduced regressions on a production site earlier this month, I reproduced the behavior on a clean local install to isolate the cause. Those problems must not have existed for you when you tested the plugin; I’m not sure if my stack or settings differ from yours.
Environment
-
WordPress: (current stable)
-
PHP: (8.2)
-
Theme/Builder: Bricks 2.0.2
-
Plugins: Winden 2.8, Advanced Themer, Font Hero, Swiss Knife (for Bricks)
-
No custom code relevant to styling
Issues
-
Bricks styles overridden by Winden
As shown in the screenshot, Winden interferes with Bricks’ styling. It’s not just the white background behind fields—multiple UI elements render incorrectly whenever Winden is enabled in Bricks. -
WordPress “Edit Page” screen breaks
With Winden enabled, the WP editor layout becomes garbled (see screenshot). -
Utilities missing from cache / not generated
Tailwind classes such asrounded-md
are missing in both the Bricks builder and the frontend. On the live site, additional classes failed after updating to 2.8. I rolled back there, so I can’t provide the full list from production.
Questions
-
Is Winden fully compatible with dequeuing Bricks v2 styles, including Bricks’ cascade layer system?
-
Can we use
@plugin
in the CSS tab now (especially Tailwind Typography and Forms)? -
Has Winden been tested with Bricks 2.1 Beta? Any known issues?
I can provide a staging copy of the affected production site for your inspection if my client approves it. But you should be able to reproduce it yourself.
Kind regards,
Malte
Uploaded files:
Kindly update Winden to latest first (2.8.2), and try again, We have not tested the latest Bricks beta as well, We will do the needful only after the final release of Bricks. You can report if there is compatibility issue here.
Regards,
Arshad
DPlugins Support
Those issues are with 2.8.2. Sorry that I only said 2.8, but I use the latest Winden Version.
Same Winden issues regardless if I use Brick Beta or 2.0.2.
Hello? Did you see my comment? I used the newest version.
I just got the confirmation from my client that I can create a copy/staging site and give you access. I will try to set it up tomorrow and give you access. Maybe that helps and shows my update issues.
I added the login details to this ticket. Except for the lack of a Redis cache, the copy is identical to the current version of the website with Bricks 1. You can test, update plugins, and do whatever you need to debug the described issues.
I would also appreciate it if you could answer my questions related to dequeuing Bricks v2 styles and using @plugin.