[AP] Style Suite

  • Thread starter Thread starter apathy's icon apathy apathy
  • Start date Start date
  • 319
  • 18,443
I think you quoted the wrong post :shell: I fixed the issue where the avatars were appearing square when "round" was selected in the settings.
The effect you showed me in this screenshot is simply what will happen you choose "round" with the vanilla frames, we don't provide any round ones so we have "square" enabled by default.
hehe I upgraded to the new version, and set avatar frames to sq in your mod, as well as in my theme's settings. Here's the results. You can still need rounded edges behind the avatars, but only in certain areas. Is this my theme? You showed me code before when you tried to fix it, but it buggered up my templates. lol

bug01.jpgbug02.jpg
 
AH yes that's the box-shadow property which exists in your theme, at least that's how it looked when I gave it a check a few weeks ago... Try it out on the default theme and see if it persists.
I decided to just disable avatar frames (since no one was using them) and I set avatar radius in style settings to 25% to produce an interesting semi-rounded effect. That works. :)

Thanks!
 
  • Allow limiting a user groups color selection
Thank you my dear brother
How do I use this feature
No problem! To use it you go to Groups & permissions > User groups, click on the group you want to edit (e.g. Moderator) and then scroll down to the "Selectable username colors" row. You can choose up to 5 colors for a user group. Once set, they'll be able to pick those 5 colors for their username.
 

Attachments

  • username_colors.webp
    username_colors.webp
    45.7 KB · Views: 4
  • username_colors_settings.webp
    username_colors_settings.webp
    8.2 KB · Views: 4
Hi @apathy! Running the newest version, and got this when I tried to delete a test member:

TypeError: apathy\StyleSuite\Service\User\Postbit::__construct(): Argument #3 ($style) must be of type apathy\StyleSuite\Entity\Postbit, null given, called in /var/www/vhosts/bloodofsouls.com/httpdocs/src/XF/Container.php on line 276 src/addons/apathy/StyleSuite/Service/User/Postbit.php:45

Stack trace

#0 src/XF/Container.php(276): apathy\StyleSuite\Service\User\Postbit->__construct(Object(XF\Admin\App), Object(SV\SearchImprovements\XF\Entity\User), NULL)
#1 src/XF/App.php(1725): XF\Container->createObject('apathy\\StyleSui...', Array)
#2 src/XF/Container.php(234): XF\App->XF\{closure}('apathy\\StyleSui...', Array, Object(XF\Container))
#3 src/XF/App.php(3158): XF\Container->create('service', 'apathy\\StyleSui...', Array)
#4 src/addons/apathy/StyleSuite/XF/Entity/User.php(24): XF\App->service('apathy\\StyleSui...', Object(SV\SearchImprovements\XF\Entity\User), NULL)
#5 src/XF/Mvc/Entity/Entity.php(1659): apathy\StyleSuite\XF\Entity\User->_postDelete()
#6 src/XF/Service/User/Delete.php(71): XF\Mvc\Entity\Entity->delete(true, false)
#7 src/XF/Admin/Controller/User.php(723): XF\Service\User\Delete->delete(NULL)
#8 src/XF/Mvc/Dispatcher.php(352): XF\Admin\Controller\User->actionDelete(Object(XF\Mvc\ParameterBag))
#9 src/XF/Mvc/Dispatcher.php(258): XF\Mvc\Dispatcher->dispatchClass('XF:User', 'Delete', Object(XF\Mvc\RouteMatch), Object(SV\AlertImprovements\XF\Admin\Controller\User), NULL)
#10 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\AlertImprovements\XF\Admin\Controller\User), NULL)
#11 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#12 src/XF/App.php(2483): XF\Mvc\Dispatcher->run()
#13 src/XF.php(524): XF\App->run()
#14 admin.php(13): XF::runApp('XF\\Admin\\App')
#15 {main}

Request state

array(4) {
["url"] => string(32) "/admin.php?users/ytret.20/delete"
["referrer"] => string(45) "Administrator login | Blood of Souls"
["_GET"] => array(1) {
["users/ytret_20/delete"] => string(0) ""
}
["_POST"] => array(7) {
["_xfToken"] => string(8) "********"
["rename"] => string(1) "1"
["rename_to"] => string(17) "Deleted member 20"
["_xfRedirect"] => string(45) "Administrator login | Blood of Souls"
["_xfRequestUri"] => string(21) "/admin.php?users/list"
["_xfWithData"] => string(1) "1"
["_xfResponseType"] => string(4) "json"
}
}

I remember seeing something similar several versions ago. I disabled your add-on and then the deletion worked. Thanks!
 
I just wanted to come in and mention that I found the problem with the post fonts not working. Apparently, if the fonts "display order" is set to the same number as another, it will disable all of the fonts. I just went through and did a while lot of tests to see what was causing the issue, and I just happened to notice the order looked very similar to the numbers that were being displayed in my "inspection", so I changed them, and behold! Fixed.
 
Hello, i have this error:

  • XF\CssRenderException: Error rendering template public:app.less: ParseError: Unexpected input in public:app.less on line 5598, column 3 (on or near line 5598)
  • src/XF/CssRenderException.php:89
  • Generado por: Cuenta desconocida
  • 29 Jun 2023 a las 4:25 PM

Seguimiento​

5595 |
5596 |
5597 |
*5598*| }
5599 |
5600 | @keyframes ap-animated-uglow--3
5601 | {
------------

#0 src/XF/CssRenderer.php(418): XF\CssRenderException::createFromLessException(Object(Less_Exception_Chunk), 'public:app.less', '// Note that th...')
#1 src/XF/CssRenderer.php(352): XF\CssRenderer->renderToCss('public:app.less', '// Note that th...')
#2 src/XF/CssRenderer.php(260): XF\CssRenderer->renderTemplate('public:app.less', NULL)
#3 src/addons/ThemeHouse/UIX/XF/CssRenderer.php(40): XF\CssRenderer->renderTemplates(Array, Array, Array)
#4 src/XF/CssRenderer.php(118): ThemeHouse\UIX\XF\CssRenderer->renderTemplates(Array, Array, Array)
#5 src/XF/CssWriter.php(55): XF\CssRenderer->render(Array)
#6 css.php(30): XF\CssWriter->run(Array, 52, 5, 'de0a02e5fabb2c0...')
#7 {main}

-------------

Previous Less_Exception_Chunk: ParseError: Unexpected input in anonymous-file-0.less on line 5598, column 3
5596|
5597|
5598| }
5599|
5600| @keyframes ap-animated-uglow--3
5601| { - src/vendor/oyejorge/less.php/lib/Less/Parser.php:677
#0 src/vendor/oyejorge/less.php/lib/Less/Parser.php(621): Less_Parser->GetRules(NULL)
#1 src/vendor/oyejorge/less.php/lib/Less/Parser.php(449): Less_Parser->_parse()
#2 src/XF/CssRenderer.php(414): Less_Parser->parse('// Note that th...')
#3 src/XF/CssRenderer.php(352): XF\CssRenderer->renderToCss('public:app.less', '// Note that th...')
#4 src/XF/CssRenderer.php(260): XF\CssRenderer->renderTemplate('public:app.less', NULL)
#5 src/addons/ThemeHouse/UIX/XF/CssRenderer.php(40): XF\CssRenderer->renderTemplates(Array, Array, Array)
#6 src/XF/CssRenderer.php(118): ThemeHouse\UIX\XF\CssRenderer->renderTemplates(Array, Array, Array)
#7 src/XF/CssWriter.php(55): XF\CssRenderer->render(Array)
#8 css.php(30): XF\CssWriter->run(Array, 52, 5, 'de0a02e5fabb2c0...')
#9 {main}

any help please? :c
 
apathy updated [AP] Style Suite with a new update entry:

2.11.3

  • Stop filter from appearing if a postbit style exists has no background image set
  • Fix separator not being styled by Tooltip border color
  • Fix padding of image uploader in certain instances
  • Some internal consistency cleanups
  • Convert post style font size admin options into style properties
  • Change default value of Post style font size column from 0 -> 12

Read the rest of this update entry...
 
I'll post this here too:

Hi @apathy ,

I'm getting a server error after updating?
SS_error_latest_2213.webp

Seems to happen when I view profiles, also, my profile's styling doesn't seem to be there anymore? I think everyone's styling is gone now after update?

URL: Smokey

URL that originally produced the error: GlamVonGrimm
 
I'll post this here too:

Hi @apathy ,

I'm getting a server error after updating?

Seems to happen when I view profiles, also, my profile's styling doesn't seem to be there anymore? I think everyone's styling is gone now after update?

URL: Smokey

URL that originally produced the error: GlamVonGrimm
All the template names were renamed for consistency in this update, and that error is telling you it's trying to find the old profile style template. It turns out there's a leftover mention of the old template name hardcoded in one of the PHP files, but it will be an easy fix for the next update.

In the meantime, you could try duplicate the ap_ss_user_style_profile.less template and call it ap_ss_profile_style.less (which is the old template name).
 
That fixed worked :pika: Will this be included in the next update automatically? Thanks! :-)
In the next update the line thats calling the old template name will simply be updated to call the new one, but it will not delete your new duplicated template on its own - so when the update releases you should delete your duplicated ap_ss_profile_style.less template to avoid confusion.
 
Hello @apathy I already solved my previous problem, I just reinstalled from the other versions but now I get this error:
  • XF\Db\Exception: MySQL statement prepare error [1054]: Unknown column 'ap_username_style' in 'field list'
  • src/XF/Db/AbstractStatement.php:230
  • Generado por: myusername
  • 15 Ago 2023 a las 1:32 AM

Follow-up​

UPDATE `xf_user` SET `ap_username_style` = ? WHERE `user_id` = 3
------------

#0 src/XF/Db/Mysqli/Statement.php(198): XF\Db\AbstractStatement->getException('MySQL statement...', 1054, '42S22')
#1 src/XF/Db/Mysqli/Statement.php(41): XF\Db\Mysqli\Statement->getException('MySQL statement...', 1054, '42S22')
#2 src/XF/Db/Mysqli/Statement.php(56): XF\Db\Mysqli\Statement->prepare()
#3 src/XF/Db/AbstractAdapter.php(96): XF\Db\Mysqli\Statement->execute()
#4 src/XF/Db/AbstractAdapter.php(324): XF\Db\AbstractAdapter->query('UPDATE `xf_use...', Array)
#5 src/XF/Mvc/Entity/Entity.php(1521): XF\Db\AbstractAdapter->update('xf_user', Array, '`user_id` = 3')
#6 src/XF/Mvc/Entity/Entity.php(1248): XF\Mvc\Entity\Entity->_saveToSource()
#7 src/XF/Mvc/FormAction.php(71): XF\Mvc\Entity\Entity->save(true, false)
#8 src/XF/Mvc/FormAction.php(189): XF\Mvc\FormAction->XF\Mvc\{closure}(Object(XF\Mvc\FormAction))
#9 src/addons/apathy/StyleSuite/Pub/Controller/Styles.php(112): XF\Mvc\FormAction->run()
#10 src/XF/Mvc/Dispatcher.php(352): apathy\StyleSuite\Pub\Controller\Styles->actionIndex(Object(XF\Mvc\ParameterBag))
#11 src/XF/Mvc/Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('apathy\\StyleSui...', 'Index', Object(XF\Mvc\RouteMatch), Object(apathy\StyleSuite\Pub\Controller\Styles), NULL)
#12 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(apathy\StyleSuite\Pub\Controller\Styles), NULL)
#13 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#14 src/XF/App.php(2353): XF\Mvc\Dispatcher->run()
#15 src/XF.php(524): XF\App->run()
#16 index.php(20): XF::runApp('XF\\Pub\\App')
#17 {main}
could you help me please?
 
apathy updated [AP] Style Suite with a new update entry:

2.11.4

  • Templates are still looking for un-minified Util JS
  • Fix Cannot call method getIconUrl on a non-object (array)
  • Rename phrase IDs and option IDs for consistency
  • Set all assets to "enabled" by default during install
  • Generate animated glow stylesheets from regular style caches and deprecate glow caches
  • Fix unknown template ap_ss_profile_style.less

Read the rest of this update entry...
 
Hey @apathy , after the last update. I get an error when I try to edit a user in the admin CP: I can confirm it's the style suite add-on as I disabled it and editing users worked again. Here is the error I get an error saying to enter a number that is at least 8?

I can't seem to post a pic here of it (not sure why) but it is definitely due to the style suite add-on. I posted a message on XF w/ a picture. When i disable the style suite add-on the error goes away and i'm able to edit users in my admin CP once more.

running PHP8.
 
@apathy I bought Nobita's Social Groups add-on and installed it, in addition to the above issues/bugs i reported in 2.11.4, I encountered this bug after installing the social groups add-on and trying to create a group:
groups_apathy_error.webp

Hopefully this issue can be fixed in the next update along with the issue I encountered in the admin panel unable to switch tabs or edit user accounts when the style suite is enabled.
 
@apathy I bought Nobita's Social Groups add-on and installed it, in addition to the above issues/bugs i reported in 2.11.4, I encountered this bug after installing the social groups add-on and trying to create a group:


Hopefully this issue can be fixed in the next update along with the issue I encountered in the admin panel unable to switch tabs or edit user accounts when the style suite is enabled.
Sorry, I read your post on XF earlier but forgot to reply!

I'm actually planning on dropping support for the group styles since
  1. the latest version I have access to is years old now, so I could only guarantee it works with that version or earlier
  2. I've never seen anybody actually use the group styles on their sites
The next update should be out in maybe a week / a week and a half, mostly (other than this issue youre reporting) it just needs to be tested.

I'll send you a preview build when it's ready so we can see if it's fixed the user editing bug because I was never able to reproduce it personally.
 
Sorry, I read your post on XF earlier but forgot to reply!

I'm actually planning on dropping support for the group styles since
  1. the latest version I have access to is years old now, so I could only guarantee it works with that version or earlier
  2. I've never seen anybody actually use the group styles on their sites
The next update should be out in maybe a week / a week and a half, mostly (other than this issue youre reporting) it just needs to be tested.

I'll send you a preview build when it's ready so we can see if it's fixed the user editing bug because I was never able to reproduce it personally.
The group add-on is on sale now for 30% off with a coupon code, i paid $35 for it yesterday which is why i jumped on it....... i could send you my copy but idk if it'd work properly with the licensing and such so you can keep it updated? If you feel it'd be worth it? totally your call though.
 
Back
Top