• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
UI.X 2

UI.X 2 [Paid] 2.0.2.1.0

No permission to buy ($35.00)
Hi, I’m not on PC so cant work this out. What is the easiest way to change the link colour of links in posts? Mine are too similar to the text. I can see how to change all link colours but I don’t want this, just the regular post links that would appear in the threads, conversations etc.
 

OperaManiac

Well-known member
I could not find an easy way to do so either so I had to use extra.css.
I am just underlining links here.

Code:
a.link.link--external, a.link.link--internal {
    text-decoration: underline ;
}
.fr-wrapper a { text-decoration: underline; }
 

ThemeHouse

Well-known member
ThemeHouse updated UI.X 2 with a new update entry:

Version 2.0.1.3.0 Released

UI.X 2 2.0.1.3.0 Change Log

Note: The UI.X add-on does not need to be updated in this new release.
  • Added a phrase for the sidebar
  • Added a style property active nav in off canvas
  • Fixed the issue that caused a text font problem with the UI.X collapsed account menu and help menu
  • Fixed the issue with the staff bar when viewing it on mobile
  • Fixed the issue that caused search position (left) to break
  • Fixed the search overlay issue on Android-based devices...
Read the rest of this update entry...
 

Zuse

Active member
Guys, great update but it's ruined my forums and I am getting this error: Please can you confirm the update does not affect the child styles?? Because I edited my child style a lot to get it where I want it and now my forums looks terrible.

Server error log
  • ErrorException: [E_NOTICE] Undefined variable: childStyleNames8
  • src/addons/ThemeHouse/UIX/XF/Admin/Controller/Style.php:444
  • Generated by: Zuse
  • Jan 31, 2018 at 8:17 PM
Stack trace
#0 src/addons/ThemeHouse/UIX/XF/Admin/Controller/Style.php(444): XF::handlePhpError(8, '[E_NOTICE] Unde...', '/home/legendo1/...', 444, Array)
#1 src/addons/ThemeHouse/UIX/XF/Admin/Controller/Style.php(305): ThemeHouse\UIX\XF\Admin\Controller\Style->installUpgradeStyle(Array, Array, Object(ThemeHouse\UIX\XF\Entity\Style))
#2 src/XF/Mvc/Dispatcher.php(249): ThemeHouse\UIX\XF\Admin\Controller\Style->actionThemehouseUpgrade(Object(XF\Mvc\ParameterBag))
#3 src/XF/Mvc/Dispatcher.php(88): XF\Mvc\Dispatcher->dispatchClass('XF:Style', 'ThemehouseUpgra...', 'html', Object(XF\Mvc\ParameterBag), 'styles', Object(ThemeHouse\UIX\XF\Admin\Controller\Style), NULL)
#4 src/XF/Mvc/Dispatcher.php(41): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#5 src/XF/App.php(1880): XF\Mvc\Dispatcher->run()
#6 src/XF.php(328): XF\App->run()
#7 admin.php(13): XF::runApp('XF\\Admin\\App')
#8 {main}
Request state
array(4) {
["url"] => string(63) "/admin.php?styles/themehouse/upgrade&product_id=210&style_id=12"
["referrer"] => string(87) "https://www.gnonline.net/admin.php?styles/themehouse/upgrade&product_id=210&style_id=12"
["_GET"] => array(3) {
["styles/themehouse/upgrade"] => string(0) ""
["product_id"] => string(3) "210"
["style_id"] => string(2) "12"
}
["_POST"] => array(4) {
["version_id"] => string(4) "1070"
["style_id"] => string(2) "12"
["step"] => string(11) "ftp_details"
["_xfToken"] => string(8) "********"
}
}
 

Zuse

Active member
Console errors:

Uncaught TypeError: Cannot read property 'register' of undefined
at d.value (index.min.js:7)
at Object.<anonymous> (index.min.js:3)
at e (index.min.js:1)
at index.min.js:1
at index.min.js:1
defer.min.js:6 Uncaught TypeError: Cannot read property 'register' of undefined
at e.value (defer.min.js:6)
at Object.<anonymous> (defer.min.js:2)
at g (defer.min.js:1)
at defer.min.js:1
at defer.min.js:1


And this big gap wasn't there before?


gap.png
 

imno007

Well-known member
Thanks. It looks like the UI.X addon itself, though, is unchanged: ThemeHouse-UIX-2.0.5_Patch_Level_1. Is that as it should be be? Just checking.
 

Jake B.

Well-known member
Getting this error since installing latest update:
ErrorException: Template error: Template public:uix_socialMedia is unknown
If it only happened during the upgrade, and hasn't happened since it should be safe to ignore -- let us know if it pops back up, however. This is most likely due to this template trying to load on the frontend for someone while the upgrade was running