[AP] Style Suite

[AP] Style Suite [Paid] 2.16.8

No permission to buy (€15.00)
Hello I get this:
Code:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /src/XF/Db/AbstractStatement.php on line 106

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 65536 bytes) in /src/addons/SV/RedisCache/Traits/Cm_Cache_Backend_Redis.php on line 533

Trying to delete the files of the addon from admin panel:
An unexpected error occurred. Please try again later.

The site is now offline.
 
Hello I get this:
Code:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /src/XF/Db/AbstractStatement.php on line 106

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 65536 bytes) in /src/addons/SV/RedisCache/Traits/Cm_Cache_Backend_Redis.php on line 533
Are you trying to install the addon for the first time? I've never run into this specific error but I've hit the odd timeout while it was processing animated assets. Generally it just continues on in the background.

I'd double-check your Appearance -> Avatar Frames, Sparkles, Fonts etc in about 15 minutes, if everything looks like it imported ok then I'd ignore the error you received. If it looks like it failed then get back to me and we can discuss it further.
 
Are you trying to install the addon for the first time? I've never run into this specific error but I've hit the odd timeout while it was processing animated assets. Generally it just continues on in the background.

I'd double-check your Appearance -> Avatar Frames, Sparkles, Fonts etc in about 15 minutes, if everything looks like it imported ok then I'd ignore the error you received. If it looks like it failed then get back to me and we can discuss it further.
He could increase his memory limit within php to compensate.
 
Are you trying to install the addon for the first time? I've never run into this specific error but I've hit the odd timeout while it was processing animated assets. Generally it just continues on in the background.

I'd double-check your Appearance -> Avatar Frames, Sparkles, Fonts etc in about 15 minutes, if everything looks like it imported ok then I'd ignore the error you received. If it looks like it failed then get back to me and we can discuss it further.
The site is completely dead. Even admin panel.
It just says "An unexpected error occurred. Please try again later."

That happened after trying to delete the plugin from admin panel.
Out of desperation I deleted addons/apathy/StyleSuite
But that didn't bring the site back online.

Now I found that setting $config['enableListeners'] = false;
the site will load, but I can't remove that.
 
The site is completely dead. Even admin panel.
It just says "An unexpected error occurred. Please try again later."

That happened after trying to delete the plugin from admin panel.
Out of desperation I deleted addons/apathy/StyleSuite
But that didn't bring the site back online.

Now I found that setting $config['enableListeners'] = false;
the site will load, but I can't remove that.
Is this with the beta build (2.14.0) or the latest stable (2.13.9)

I just tried installing the former on my staging site and didnt run into anything like this. Do you see any other errors in your admin panel, before the "Fatal error: Allowed memory size" ones?
Additionally does it say anything like "One or more addons are stuck in an inconsistent state"?
 
It was the beta build. I didn't read I shouldn't use it.
I increased the memory limit to 512MB.
Since I have removed the files from /addons I uploaded them manually from 2.13.9 zip
I tried to install it, but it said.
Code:
XF\Db\Exception: MySQL query error [1364]: Field 'css' doesn't have a default value in src/XF/Db/AbstractStatement.php at line 230
XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 207
XF\Db\Mysqli\Statement->getException() in src/XF/Db/Mysqli/Statement.php at line 83
XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 96
XF\Db\AbstractAdapter->query() in src/XF/Db/AbstractAdapter.php at line 219
XF\Db\AbstractAdapter->insert() in src/XF/Mvc/Entity/Entity.php at line 1572
XF\Mvc\Entity\Entity->_saveToSource() in src/XF/Mvc/Entity/Entity.php at line 1300
XF\Mvc\Entity\Entity->save() in src/addons/apathy/StyleSuite/Install/Asset.php at line 203
apathy\StyleSuite\Setup->saveAssetEntity() in src/addons/apathy/StyleSuite/Install/Asset.php at line 126
apathy\StyleSuite\Setup->importAssetsFromFilesystem() in src/addons/apathy/StyleSuite/Setup.php at line 135
apathy\StyleSuite\Setup->postInstall() in src/XF/AddOn/AddOn.php at line 575
XF\AddOn\AddOn->postInstall() in src/XF/Admin/Controller/AddOnController.php at line 799
XF\Admin\Controller\AddOnController->actionFinalize() in src/XF/Mvc/Dispatcher.php at line 362
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 264
XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 121
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 63
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2826
XF\App->run() in src/XF.php at line 806
XF::runApp() in admin.php at line 15

Then I did "delete files". It completed wihtout errors.
I removed $config['enableListeners'] = false;

But the site still doesn't work: "An unexpected error occurred. Please try again later."

It's hard for me to find any error cos the logs get many per second.








EDIT: I found the entry for the beta in addons with "files missing" flag, i sucessfully uninstalled it and removed the files.
I was able to remove $config['enableListeners'] = false; and the site is live.
I will try to install the apathy-StyleSuite-2.13.9-adc5932c version
 
It was the beta build. I didn't read I shouldn't use it.
I increased the memory limit to 512MB.
Since I have removed the files from /addons I uploaded them manually from 2.13.9 zip
I tried to install it, but it said.
~CODE~

Then I did "delete files". It completed wihtout errors.
I removed $config['enableListeners'] = false;

But the site still doesn't work: "An unexpected error occurred. Please try again later."

It's hard for me to find any error cos the logs get many per second.
I don't know what to do to completely eliminate the plugin if uninstall didn't do it.

Okay, let's try this
  1. Download 2.14.0 Beta again
  2. Modify /src/addons/apathy/StyleSuite/Setup.php,
    1. Find this line: $this->importAssetsFromFilesystem();
    2. Change it to this: //$this->importAssetsFromFilesystem();
  3. Delete /src/addons/apathy/StyleSuite/hashes.json file
  4. Re-upload /src/addons/apathy/StyleSuite to your server
  5. Try install -> uninstall
This should remove all of the columns, whereas your method wouldn't remove the columns added in 2.14.0

Nvm i see you got it, well done. Try with 2.13.9 and the higher memory limit (though I'd say 512MB is too much, so revert it once the addon is installed)
 
Nvm i see you got it, well done. Try with 2.13.9 and the higher memory limit (though I'd say 512MB is too much, so revert it once the addon is installed)
Ok so I downloaded the zip, installing. and this step takes a long time:
"apathy/StyleSuite - Finalizing..."
There's a xenforo orange installing animation so up until this point it's fine. But then at some point the loading animation disappears.
And this happens:
Untitled.webp

The add-on shows up as "Installed" though I doubt it finished correctly.
These are the latest errors;

Untitled1.webp
 
Ok so I downloaded the zip, installing. and this step takes a long time:
"apathy/StyleSuite - Finalizing..."
There's a xenforo orange installing animation so up until this point it's fine. But then at some point the loading animation disappears.
And this happens:
~PIC~

The add-on shows up as "Installed" though I doubt it finished correctly.
These are the latest errors;

~PIC~

I wouldnt worry about the timeout too much, the assets should continue importing in the background and the timeout shouldn't interrupt the logic flow

Check the db and see if theres __conflict tables, if not then those errors are from your previous failed attempts.
If there are, uninstall the addon again, delete the tables, and reinstall.
 
Another thing, avatar frames do not match my avatar size well.
The images are 192x192 displayed at 140x140
On standard frames you can see under it:

avatar1.webp
and animated shows up too small:
avatar3.webp

EDIT:
  • The first issue seem to only happen on preview after all!
  • The second one happens also on posts.
Might need css tweaks?
 
Ok I uninstalled it, deleted the tables, reinstalled (it timed out again).
No errors on log. I think I might be good?
Should be good to go!

Another thing, avatar frames do not match my avatar size well.
The images are 192x192 displayed at 140x140
On standard frames you can see under it:

View attachment 318880
and animated shows up too small:
View attachment 318881

EDIT:
  • The first issue seem to only happen on preview after all!
  • The second one happens also on posts.
Might need css tweaks?
You would use CSS to fix these

in ap_ss_asset_avatar_frame.less you can add frame-specific tweaks by adding something like this to the bottom of the template:

Code:
.ap-ss-avatarFrame--10::after
{
    transform: scale(2);
}

this would double the size of avatar frame #10, the ID of each frame is visible in the URL bar when viewing their "edit" page
 
@apathy is this just me?
View attachment 318889
Code:
<script>
XF.ready(() =>
{

        XF.extendObject(true, XF.config,
        {
           
                apSsAvatarFrameStyle: 'square',
           
           
           
        ,
            "svStandardLib_time.day": "{count} day",
works for me, check if you have any JS minifiers / defer scripts or settings set.

Mine doesnt say "XF.ready()" though, not sure where thats coming from for you

Code:
<script>
window.addEventListener('DOMContentLoaded', () =>
{

        XF.extendObject(true, XF.config, 
        {
            
                apSsAvatarFrameStyle: 'square',
            
            
            
        });
    
})
</script>
 
I think it's related to Standard Library by @Xon ?
The issue is the extra comma, full code on page:


Code:
<script>
XF.ready(() =>
{

        XF.extendObject(true, XF.config,
        {
           
                apSsAvatarFrameStyle: 'square',
           
           
           
        ,
            "svStandardLib_time.day": "{count} day",
            "svStandardLib_time.days": "{count} days",
            "svStandardLib_time.hour": "{count} hour",
            "svStandardLib_time.hours": "{count} hours",
            "svStandardLib_time.minute": "{count} minutes",
            "svStandardLib_time.minutes": "{count} minutes",
            "svStandardLib_time.month": "{count} month",
            "svStandardLib_time.months": "{count} months",
            "svStandardLib_time.second": "{count} second",
            "svStandardLib_time.seconds": "{count} seconds",
            "svStandardLib_time.week": "time.week",
            "svStandardLib_time.weeks": "{count} weeks",
            "svStandardLib_time.year": "{count} year",
            "svStandardLib_time.years": "{count} years"

        });
   
})
</script>
 
I think it's related to Standard Library by @Xon ?
The issue is the extra comma, full code on page:

I have that addon as well and it's working fine so I'm uncertain that's the issue.
If you have no JS minifiers etc set up in the likes of Cloudflare or other addons then I'd start disabling addons one-by-one to see if it persists.
Also, check if it happens on the default theme.
 
There's no minification that I'm aware of.
If I disable standard library it turns into this: (no error):

Code:
<script>
XF.ready(() =>
{

        XF.extendObject(true, XF.config,
        {
          
                apSsAvatarFrameStyle: 'square',
          
          
          
        });
  
})
</script>

If I disable this plugin, the whole block disappears. I was expecting this portion to be there but no:


Code:
            "svStandardLib_time.day": "{count} day",
            "svStandardLib_time.days": "{count} days",
            "svStandardLib_time.hour": "{count} hour",
            "svStandardLib_time.hours": "{count} hours",
            "svStandardLib_time.minute": "{count} minutes",
            "svStandardLib_time.minutes": "{count} minutes",
            "svStandardLib_time.month": "{count} month",
            "svStandardLib_time.months": "{count} months",
            "svStandardLib_time.second": "{count} second",
            "svStandardLib_time.seconds": "{count} seconds",
            "svStandardLib_time.week": "time.week",
            "svStandardLib_time.weeks": "{count} weeks",
            "svStandardLib_time.year": "{count} year",
            "svStandardLib_time.years": "{count} years"

Other plugins don't seem to have an effect.
 
Would you add a field to frames to specify a class?
Or maybe allow "grouping" frames and add a class with the group name to all the frames in same group.

So we don't have to edit extra.less to add same rule to a different frame?
 
There's no minification that I'm aware of.
If I disable standard library it turns into this: (no error):

If I disable this plugin, the whole block disappears. I was expecting this portion to be there but no:
Odd, I'm really unsure of why that'd be, I've never had an issue running the standard library alongside style suite. I'll try look into it.

Would you add a field to frames to specify a class?
Or maybe allow "grouping" frames and add a class with the group name to all the frames in same group.

So we don't have to edit extra.less to add same rule to a different frame?
I'll try add custom classes into 2.14.0 if possible.
It already allows for inputting custom CSS without having to edit .less templates, but you would be re-specifying the same rules over and over, so I agree custom classes would work nicely alongside this.
 
I think it's related to Standard Library by @Xon ?
The issue is the extra comma, full code on page:
Make sure you have updated StandardLib to the latest version as it updates how it injects phrases which doesn't conflict with this add-on

I think it's related to Standard Library by @Xon ?
The issue is the extra comma, full code on page:


Code:
<script>
XF.ready(() =>
{

        XF.extendObject(true, XF.config,
        {
          
                apSsAvatarFrameStyle: 'square',
          
          
          
        ,
            "svStandardLib_time.day": "{count} day",
            "svStandardLib_time.days": "{count} days",
            "svStandardLib_time.hour": "{count} hour",
            "svStandardLib_time.hours": "{count} hours",
            "svStandardLib_time.minute": "{count} minutes",
            "svStandardLib_time.minutes": "{count} minutes",
            "svStandardLib_time.month": "{count} month",
            "svStandardLib_time.months": "{count} months",
            "svStandardLib_time.second": "{count} second",
            "svStandardLib_time.seconds": "{count} seconds",
            "svStandardLib_time.week": "time.week",
            "svStandardLib_time.weeks": "{count} weeks",
            "svStandardLib_time.year": "{count} year",
            "svStandardLib_time.years": "{count} years"

        });
  
})
</script>

@apathy newer versions of StandardLib uses a string replacables targetting;
Code:
<!--[XF:js_global:xf_phrase_start]-->
And then adding:
Code:
$0
"svStandardLib_time.day": "{{ phrase('time.day')|escape('json') }}",
"svStandardLib_time.days": "{{ phrase('time.days')|escape('json') }}",

This is much more reliably than the previous behavior which used a regex.
 
Back
Top Bottom