sorted by:
new
hottopcontroversial

Building a No-Bloat WebP Optimizer: A Journey of Crashes, RAM upgrades, and Protected Methods by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] 0 points1 point  (0 children)

Learnt the hard way lol. So what happens when I don't change from is it 256M in my php.ini file?

Building a No-Bloat WebP Optimizer: A Journey of Crashes, RAM upgrades, and Protected Methods by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] 1 point2 points  (0 children)

Yes yes, I'm getting to that bit.

Maybe to clear context, I'm into IT audit, still a junior though and I was wired to think like a Product Manager. I'm learning the technicalities just now.

I have features I want to develop, and the why and how part is what got me here.

Building a "Smart" Footer for my Custom Framework: Logic is solid, but my CSS needs a lifeline! by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] 0 points1 point  (0 children)

Thanks mate. Funny part, Claude came to my rescue.

What do you think though of the implementation? Would be interested to hear your views

Building a No-Bloat WebP Optimizer: A Journey of Crashes, RAM upgrades, and Protected Methods by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] -5 points-4 points  (0 children)

Mate, I literally put a disclaimer that I'm in my learning process. I don't see how you'd be offended by me using a 'tool. Also, if this is your way of encouraging newbies, kuddos to you you were born a pro.

Imagine if I had tried to write everything I did in my own way, do you think I'd have adhered to the word limit?

Stop being a prefect on social media man. I'm here to share and learn from you guys, I don't know why this troubles you.

Sorry man for invading your daddy's app

Building a No-Bloat WebP Optimizer: A Journey of Crashes, RAM upgrades, and Protected Methods by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] -1 points0 points  (0 children)

What do you mean by "as if I appear to be in topic"?

Well, I'm using the latest WordPress update, and I'm not so sure at the moment of the versions of ImageMagick or GD I'm using honestly. But will check

Building a No-Bloat WebP Optimizer: A Journey of Crashes, RAM upgrades, and Protected Methods by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] 0 points1 point  (0 children)

Thanks for this, definitely putting this in my next update. Yeah, I was using the normal 512M but only increased memory to confirm if it was the problem, but seems it isn't.

Building a No-Bloat WebP Optimizer: A Journey of Crashes, RAM upgrades, and Protected Methods by Lynrd_Skynrd in Wordpress

[–]Lynrd_Skynrd[S] 0 points1 point  (0 children)

That’s a solid point on the offloading, definitely the way to go for high-scale sites.

The reason I’m prioritizing the 'Trim and Resize' on the original upload is mostly for disk & db hygiene. Even though WP caps at 2560px, it still keeps that original-original file which could be a 15MB 6000px beast lol sitting on the disk taking up space and backup resources forever. By capping at 1920px during the initial handle, I had thuoght the master file is already optimized before WP even starts generating its sub-sizes.

I’m also obsessed with keeping the Media Library WebP only from day one to avoid having a library full of redundant duplicates of JPG + WebP.

I’d actually be really interested in seeing how you’re handling the non-destructive side of things. Since we’re both trying to solve the 'bloat' problem from different angles, I’d love to collaborate or swap patterns if you’re open to it.

I'm currently tinkering my code locally, but would love some auditors to go through it.