[AP] Style Suite

[AP] Style Suite [Paid] 2.16.15

No permission to buy (€15.00)
Overview Updates (118) Reviews (13) History Discussion
FadedMartian said:
i appreciate the pointers. i have wrapped all 4 of those templates, but now that i have done, it is doing the below:
PICS

any idea how to remove the remainder of the (non-linked) gradient text? so its just showing the normal username hyperlinked? thanks!
Click to expand...
No solution for this as of now, but I'll try get back to you in the next day or two about it.

FadedMartian said:
sorry, also, I noticed that while hex and HSL-type values work for colors, typing basic colors like "red" do not work... yet the color picker box to the right of the color field shows the color & in the preview of the style at the top of the style tabs does. is this as intended? is it possible to make basic colors via their words not error out?

PIC

the error is as follows when one tries to save the color (when the color word itself is the typed value):
PIC
Click to expand...

Thats an oversight on my part, color names should certainly be accepted. I'll have a hotfix out soon addressing this.
 
apathy said:
No solution for this as of now, but I'll try get back to you in the next day or two about it.



Thats an oversight on my part, color names should certainly be accepted. I'll have a hotfix out soon addressing this.
Click to expand...
thanks. it appears for some reason that the color names are case-sensitive.. for example if you type in aqua for the color name it works, but not if you type in Aqua.

assuming this is not as intended? thanks!
 
FadedMartian said:
i appreciate the pointers. i have wrapped all 4 of those templates, but now that i have done, it is doing the below:

any idea how to remove the remainder of the (non-linked) gradient text? so its just showing the normal username hyperlinked? thanks!
Click to expand...
Edit ap_ss_user_style_text.less, add this to the top of the file:

Code: 
:not([data-template="member_view"]) .ap-ss-textClip {
    display: none;
}
 
I've been getting this error intermittently on my live install: ErrorException: [E_WARNING] Undefined array key "class" src/addons/apathy/StyleSuite/Template/TemplaterSetup.php:207.

It happens when the RSS feed is being generated and there's a user mention in a post. Looking at the stack trace, the issue comes from BBCode rendering a [USER] tag. Did some digging and I think I found what's going on.

In fnTextIcon, the $attributes parameter defaults to an empty array. When it gets called from certain contexts (like the RSS renderer), the array doesn't have the class key set. Then on line 204 and 207 the code tries to concatenate to $attributes['class'] which doesn't exist yet - PHP 8 throws a warning for that.

Same thing seems to happen in Templater.php around line 155 in fnUserTitle. I believe the fix would be to initialize $attributes['class'] before concatenating to it (the ??= operator would work). Just wanted to flag this since it's been popping up occasionally in my error logs. Cheers
 
apathy said:
Yes, I just got to try it today.
I'm going to have an update out tomorrow that addresses one small issue during the 2.15.0 regarding icons, so first off I'd wait until thats out. But there's some quick steps you'll need to take to work around a filename conflict.

  • Mark board as inactive as users will otherwise see errors during the process
  • Using FTP, delete the folder src/addons/apathy/StyleSuite
  • Upload the 2.16.13 src/addons/apathy/StyleSuite
  • Delete src/addons/apathy/StyleSuite/hashes.json
  • Swap back to admin panel -> click "Upgrade"
  • Upload 2.16.13 hashes.json
Alternatively you can try upgrade in steps but I honestly think the solution above is easiest/cleanest
Click to expand...

Did not work.

UnhandledMatchError: Unhandled match case '...' in src/addons/apathy/StyleSuite/Install/Helper.php at line 94
  1. apathy\StyleSuite\Setup->getAssetHandlerByType() in src/addons/apathy/StyleSuite/Install/Upgrade2150030.php at line 326
  2. apathy\StyleSuite\Setup->upgrade2150030Step7() in src/XF/AddOn/StepRunnerUpgradeTrait.php at line 124
  3. apathy\StyleSuite\Setup->upgradeStepRunner() in src/XF/AddOn/StepRunnerUpgradeTrait.php at line 73
  4. apathy\StyleSuite\Setup->upgrade() in src/XF/Admin/Controller/AddOnController.php at line 617
  5. XF\Admin\Controller\AddOnController->actionUpgrade() in src/XF/Mvc/Dispatcher.php at line 362
  6. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 264
  7. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 121
  8. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 63
  9. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2826
  10. XF\App->run() in src/XF.php at line 806
  11. XF::runApp() in admin.php at line 15

Botched up pretty badly, had to restore the /src/apathy directory, then do a rebuild then re-enable. Still lost some inline styling but back to 2.13.8.

At this stage I'm going to take my losses and have done a clean uninstall (your uninstaller doesn't seem to remove ALL files so manually deleted data/apathy and src/apathy). Will do a fresh install.

After a fresh install of 2.16.15 I still do not see the custom frames (constant issue since the beginning). So will try adding those manually again.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom