Shane Bishop
Forum Replies Created
-
Forum: Plugins
In reply to: [Imsanity] Fatal Error with 2.9.1 updateVersion 2.9.2 with the fix has been released. Unfortunately, ww.wp.xz.cn just instituted a new 24-hour waiting period for plugin updates. From what I understand, this will prevent automatic updates for 24 hours, and may also prevent it from showing in your wp-admin for 24 hours. It looks like 2.9.2 can be manually downloaded and installed from https://ww.wp.xz.cn/plugins/imsanity/ though.
You can also delete Imsanity and reinstall it from the wp-admin to get the latest version.
Forum: Plugins
In reply to: [Imsanity] Fatal Error with 2.9.1 update@glycymeris Thanks for your report, see my prior reply.
Forum: Plugins
In reply to: [Imsanity] Fatal Error with 2.9.1 updateWe’ve identified the source of the issue in Imsanity and will push out an Imsanity bugfix release early next week. Fix currently available at https://github.com/nosilver4u/imsanity/
We’ve identified the source of the issue in Imsanity and will push out an Imsanity bugfix release early next week. Fix currently available at https://github.com/nosilver4u/imsanity/
Forum: Plugins
In reply to: [Query Monitor] memory issuesWell, I remembered an issue I had way back on my staging site that I strongly suspect could be related. It had to do with Query Monitor sending data via response headers–because naturally you can’t pollute an admin-ajax.php response or various POST requests in the wp-admin.
Anyway, I had the error replicated, then put in that constant, and it went away. I removed the constant, and now I can’t get the issue to come back…
Well, anyway, here’s what I remember from when it happened on my staging site. I was having a similar issue, I think it was also causing 502 errors. There was some fix related to increasing the fastcgi_buffers and fastcgi_buffer_size settings. My staging site is on a different server setup, but now I can’t seem to replicate it there either.
Either way, I don’t think those settings can be changed on WPE, so I wonder if there’s any way to detect such a situation and limit the amount of data returned in the admin-ajax.php headers?
Not a huge issue, if I can just remember it for next time the issue crops up, but if you have any ideas, that’d be great.
Forum: Plugins
In reply to: [Query Monitor] memory issuesHmm, while that isn’t ideal, it might help narrow things down. Besides error reporting, it’s entirely possible the issues are related to db queries or something else that is happening on those requests.
I’ll try it out and see if the issue is indeed from the error handler, or somewhere else. Thanks!
You’re very welcome, glad to help!
Hi Piet,
You can always find our minimum supported PHP at https://ww.wp.xz.cn/plugins/force-regenerate-thumbnails/
Currently, we support all the way back to PHP 7.4, and you can use any newer version, including PHP 8.5. I specifically tested PHP 8.5 for the 2.3.0 release back in February, which you can see on the changelog: https://ww.wp.xz.cn/plugins/force-regenerate-thumbnails/#developers
Unfortunately, the plugin repository doesn’t give us any official way to declare what versions of PHP we support beyond the minimum, but if you ever have issues on any newer version of PHP, please let us know!
Forum: Plugins
In reply to: [Image Regenerate & Select Crop] double thumb generation?Looks good, no double regen anymore!
Forum: Plugins
In reply to: [LiteSpeed Cache] LSC deleting .webp images it did not createHmm, that does appear to solve the conflict as the IR&SC plugin appears to be running at a priority higher (later) than 0.
However, I don’t know it’s a great idea, as we’ve run image optimization at a priority higher than 10 for a long time due to other plugins running at the default of 10 and doing various image manipulation things–not that I can remember what those were anymore 🙂
Also, it doesn’t address my concern that LSC shouldn’t be messing with .webp images when it isn’t even doing any image optimization to an image. Specifically, why does $img_optm->has_optm_record() return true for an image that LSC didn’t alter?
To be fair, EWWW IO blindly removes .webp images also, BUT generally only when deleting an image entirely. Whereas this is a hook that runs for every single image upload, and it seems a bit odd to delete the .webp files at this stage unless LSC can confirm that it did indeed create those .webp images. Just my two cents anyway!
Forum: Plugins
In reply to: [LiteSpeed Cache] LSC deleting .webp images it did not createOh yes, of course! I was going to write that out and forgot…
To my knowledge, this is all that is required:
- Install Litespeed Cache plugin, disable all Image Optimization settings.
- Install Image Regenerate & Select Crop plugin. Defaults should be fine there.
- Install EWWW IO, enable WebP conversion. Use version 8.5.0, since the next release will include a change related to IR&SC.
- Add this to your wp-config.php:
define( ‘EWWW_DISABLE_ASYNC’, true ); - Upload an image via Media->Add New (can probably do it anywhere).
- Go to the Media Library, put it in List mode. You should see in the Image Optimizer column that there is a WebP size listed that links to the full-size .webp version->
- Click that link, and it should be broken.
Likewise, one can watch via ftp or file manager and refresh during the upload to see .webp images created, and then removed at the end of the upload process.
And yes, EWWW IO does normally name the files the same way as Litespeed. EWWW IO does have the option to replace the extension, but the default is to append .webp.
I noticed in Admin::wp_generate_attachment_metadata() it uses $img_optm->has_optm_record() to see if LSC has optimized the image before running $img_optm->reset_row(). In this case, there shouldn’t be any records, but somehow it still evaluates to true and runs the reset_row() method, as I verified by enabling debugging in LSC:
05/06/26 00:29:17.414 [x.x.x.x:56120 1 rkj] 👮 Image replaced, resetting optimization data [pid] 262
05/06/26 00:29:17.414 [x.x.x.x:56120 1 rkj] 🗜️ _reset_row [pid] 262
05/06/26 00:29:17.415 [x.x.x.x:56120 1 rkj] 🗜️ deleting 2026/05/photo-1465152251391-e94453ee3f5a.jpg
05/06/26 00:29:17.415 [x.x.x.x:56120 1 rkj] 📺 deleted /home/xyz/public_html/wp-content/uploads/2026/05/photo-1465152251391-e94453ee3f5a.jpg.webp
and so on...Forum: Plugins
In reply to: [Username Changer] bogus data collection?Thanks for the clarification, and for the prompt response.
I don’t remember 100% now that I dismissed the prompt, but it seems the name/email were enabled by default, so it might help to have that turned off, but with an explanation about how they might be useful/needed.
Forum: Plugins
In reply to: [Admin Color Schemes] needs update for 7.0Great, glad to hear it! And that was “Using the latest beta…”, my fingers have not been following instructions very well lately 🙂
Forum: Themes and Templates
In reply to: [OceanWP] x.com icon doesn’t seem to work?Ah, I didn’t realize Elementor was still on v5, that makes sense. I was curious if they had a way to disable the FA bits altogether, and I didn’t find anything like that. However, I found that if I enable their “inline icons” feature, then everything works just fine (as does your solution).
It’d be great though if OceanWP had a feature like that. We inline our icons on another site and it works really well to minimize the bloat from FA. It’d be even better for this site, as there’s just a handful of icons across two different font sets, and 450kb of font files loaded just for that.
Thanks for the help!
- This reply was modified 3 months, 1 week ago by Shane Bishop.
Forum: Plugins
In reply to: [Apocalypse Meow] can’t search by subnetAnd it worked, thanks!