UI.X 2

UI.X 2 [Paid] 2025-03-05

No permission to buy ($59.50)
It looks like some people still have the theme enabled then. You'll need to either run a query to update the selected style as I don't think XF has a way to force update it, or just re-enable the addon. The css.php URLs there are still loading UI.X files so it must be in use somewhere.
 
It looks like some people still have the theme enabled then. You'll need to either run a query to update the selected style as I don't think XF has a way to force update it, or just re-enable the addon. The css.php URLs there are still loading UI.X files so it must be in use somewhere.

Doesn't disabling it for user selection effectively do this? I tested it out on another user and it did just that.

I can re-enable it I guess.
 
It still keeps the old selection in the database, on the front end it seems to load the default theme if the selected one isn't available but there may be other instances such as sending emails where it still loads the selected theme.

Clearly somewhere the old theme is still enabled as the logs show that the CSS files are being included which would only happen if the theme was being loaded. Without debugging further at database level there isn't much else I can suggest as how XF loads a selected theme isn't within our control.
 
It still keeps the old selection in the database, on the front end it seems to load the default theme if the selected one isn't available but there may be other instances such as sending emails where it still loads the selected theme.

Clearly somewhere the old theme is still enabled as the logs show that the CSS files are being included which would only happen if the theme was being loaded. Without debugging further at database level there isn't much else I can suggest as how XF loads a selected theme isn't within our control.

Thanks Matt + TH team for your help, I'll look into what to update in the DB to force everyone I guess.
 
Seems to be style ID 7 from the path in the error: internal_data/code_cache/templates/l1/s7/public/setup_custom.less.php

This will likely be the UI.X theme ID.

Can run this query to update users:

SQL:
UPDATE xf_user SET style_id = 0 WHERE style_id = 7;

This will set everyone to track the default theme if they're currently using ID 7.
 
why not just export the style then delete?

According to XF (thanks Paul) - the way it should work (but not quite) is that you disable style for user selection and it should default to the default one.

I did find another gotcha and that's the email template in the XF ACP has it's own styling default that doesn't update when you disable a style so that may have actually been generating some errors.

Anyway, I've archived / deleted styles, updated xf_user and will see if errors go away.
 
I was trying to install your theme in a test forum but it didn't work for me... looking at the active forum I noticed that I also installed the addon "[TH] UI.X" but nowhere on your site does it tell me to download or itallare.

Where can I find it? I need [TH] UI.X 2.2.0 Patch Level 3 and not a later version because the test site is xf 2.2
 
I saw that in the theme download area on your site at the top there is another button to download the right component! Make him download the version for xf 2.3
Where can I find the old versions?
 
ThemeHouse updated UI.X 2 with a new update entry:

Version 2.3.5.0.0 Released

Changelog:
This version of UI.X includes a separate XML in the child_xmls folder; this is a variations-ready version of UI.X that is in beta and is not officially supported. It is designed to be used as a stand-alone style, so don't install it as an actual child of the default UI.X style; install it separately.
Minor bug fixes with some spacing and sizing, updating for XF 2.3.5

Note: This release cannot be used on XenForo 2.2, it is exclusively for XenForo 2.3 only.
Note: This update...

Read the rest of this update entry...
 
If you're running the latest XenForo (2.3.5), you'll need to upgrade to the latest style; You can hit "Upgrade Now" to update to the latest compatible version.

If you're not on XF 2.3.5, however, you won't be able to upgrade the style yet.
 
For now, yes: We were holding off on releasing a variations-ready version of UIX until XF fixed a couple of the color function bugs, but given how long it has been we may be waiting a while, so we may end up removing our reliance on the bugged functions instead (although I'm not particularly excited at that prospect).

I will note we'll probably - at least for the time being - maintain separate versions, just because some folks' customized styles may not translate well to the variations version.
is there any update on that when we could expect a stable version? And is it the same problem for AC.UI or just UI.X? Thank you.
 
is there any update on that when we could expect a stable version? And is it the same problem for AC.UI or just UI.X? Thank you.

Not at this time; For the most part it's only unsupported just because of the bugs with color functions in XF itself.. And yeah, same thing with the AC.UI Variations version. The issues are relatively minor, but we're a bit of a stickler on that sort of thing given whatever XF ends up deciding to do regarding those color functions could dramatically impact variations overall (not likely, of course, but there's always the possibility).
 
Not at this time; For the most part it's only unsupported just because of the bugs with color functions in XF itself.. And yeah, same thing with the AC.UI Variations version. The issues are relatively minor, but we're a bit of a stickler on that sort of thing given whatever XF ends up deciding to do regarding those color functions could dramatically impact variations overall (not likely, of course, but there's always the possibility).
Thanks for your reply. To be honest I am playing around with AC.UI for some hours now and adapting it to my needs and so far I didn't have any problems. So I am not quite sure which color functions are causing problems. But I guess then it would be safe to use it if its only a minor thing. :)
 
Thanks for your reply. To be honest I am playing around with AC.UI for some hours now and adapting it to my needs and so far I didn't have any problems. So I am not quite sure which color functions are causing problems. But I guess then it would be safe to use it if its only a minor thing. :)

It really only becomes obvious on the default versions of the varations-ready UIX style's select arrows on dark mode.. There's the possibility of it occurring elsewhere, but that'll depend on how things are customized and whatnot. AC.UI should be OK unless you end up using a magical combination of color functions that break things, which we amazingly enough didn't use by default this time around (mostly because it's designed to be a little more opinionated than UIX,) :D
 
Back
Top Bottom