I suspect it just didn't occur to them or they didn't know exactly how to go about it, but it sounds like that might be the solution to the dialog conflict issue. Until they get around to resolving the issue at their end, could you share the details about specifically how you went about "overriding" the UI theme? I'm reasonably proficient with jQuery but not an expert on scoping and namespaces.

See also this discussion...

http://www.concrete5.org/community/forums/customizing_c5/using-regu...

-Steve

We end up using a custom jquery script. It was too much work trying to override css and debug conflicts since we had to create 5 different theme for tabs and accordion menu.

I hope that c5 core will use a unique scope someday or having a way to define one in the config/

on our list of things to address is compatibility with the jQuery UI Dialog class. Of course, many add-ons require .dialog() continuing to work the way it has been assumed to work, which is part of the challenge.

I am wondering if this issue has been resolved? I 'themerolled' a tab set for the area splitter, however, when I apply my theme, the tabs stack instead of show/hide.

I can manually change the css and js callouts in the controller.php file, and doing so fixes the jquery issue with my tabs, but screws up my editor.

Thanks!

We've been struggling with this too... It seems that several jQuery UI components (dialog included) append stuff to the body tag which puts it outside of any normal css scope that's applied.

We're seeing all kinds of strange things happening with our UI and other css modifying the look of the Concrete 5 dashboard and Concrete's UI modifying our site UI css.

While we can try and add scope on our side without Concrete 5's jquery Ui css being properly scoped we're fighting a losing battle.