webmastermd
Forum Replies Created
-
Ok, thanks.
I would not really care if I talk about the maintenance mode which returns a 503 anyways. But the Coming Soon mode returns a 200 and thus the page gets indexed.
That’s the reason most Coming Soon plugins have SEO options as it’s important to feed the search engine from the beginning with relevant data.
Now it’s really neat that Elementor has a Coming Soon mode which makes those plugins obsolete, but only if I can use a SEO plugin.
So let this be a feature request, to make TSF compatible with Elementor Coming Soon mode.
Best regards
Forum: Plugins
In reply to: [LuckyWP Table of Contents] German umlauts insufficient transliteration@theluckywp Any news on this?
Forum: Plugins
In reply to: [LuckyWP Table of Contents] German umlauts insufficient transliterationThanks you for looking into it.
Thanks, this works.
Forum: Plugins
In reply to: [Companion Auto Update] No update reminder emailIt’s not fixed for me, noting changed. I reinstalled the plugin and it still does not work.
Forum: Plugins
In reply to: [Companion Auto Update] No update reminder emailYes, I also checked the servers PHP setting for timezone. Both are set to Berlin/BrΓΌssel (GMT+1). The time your plugin shows for next mail is GMT time.
I also checked the real cron time with a plugin (WP Crontrol) and the cau_set_schedule_mail cron-slug is set correctly to hourly and shows the GMT+1 time. I used the plugin to run the cron event instantly but still no mail appears.
Lightning-fast as always. The fix works.
Thank you very much.Best regards
Forum: Plugins
In reply to: [Enhanced Media Library] Plugin abandoned?WordPress Real Media Library, which is very good, but only available from codecanyon and there are no multi-licenses. But in the end I think it is a good investment, as my less tech-savvy customers can get used easier to an OS-like folder structure instead of a tagging-like scheme for files.
I would like this changed too.
It’s confusing if you not know what it means, thus it’s not intuitive.Thanks
Cool. You are the best π
Thanks and happy coding.
Thanks for the quick response.
Right now, I have no time to test this, maybe next week, then I come back to you.
As I think about it, it’s most probably the ngrok tunnel I had to use for testing on my smartphone, as I have installed all Google fonts as system fonts on my development pc.As you have to save the image as a file again after resize and before upload to resmush.it, you use a quality factor for the image.
I just looked at your source code by myself and you use wp_get_image_editor which returns a Wp_Image_Editor instance with the image loaded. Then you set no quality before using ->save again, thus the default quality is chosen.
As I’ve read about different default values, like 90, 92 or 82, I can only see that in the current 5.0 trunk the default value in the class is declared by 82 (see: https://core.trac.ww.wp.xz.cn/browser/tags/5.0/src/wp-includes/class-wp-image-editor.php#L14) which is a bit less.
So can you please check in your code which quality is really used at execution time or set it explicitly to something over 90, not that you have unnecessary double compression by resize and then resmush.it.
—–
As for the qualities, I’ve looked at you source too and am a bit surprised.
Actually you use:
Lossless: 90
Lossy: 75
High: 50I don’t think this is a good idea, and I would suggest to change this, as “Lossless” normally means no compression at all. I know, setting 100 is generally a bad Idea, but 90 is a bit less for “Lossless”, I actually thought “Lossy” would be at 90.
Now I know that I must use “Lossless” to get the compression to my liking.
That being said, I can only second my request to implement a free choosing of the quality factor.
Thanks and best regards,
ManuelThanks, but can you please look again at my first question, I think you misunderstood. I asked about the compression (side-effect) of the resize algorithm.
Hi. Thanks for the fast reply.
to 1. It was more a question, if this is intentional (maybe to simplify things or because you use another algorithm or similar). But if it is possible to add more flexible compression settings, then this can be a suggestion.
to 2. This was also more a question, as there could be a reason to backup all. But if there is no reason, then of course this should be considered to change.
to 3. Glad to hear.
to 4. The plugin I use for this, is “Imsanity”, which lets you define freely the width and height for resize and even in different context (e.g. uploaded directly to media gallery or uploaded in post). But as there are so many micro plugins slowing down the site, it’s always welcome to have plugins which can replace multiple of them.
Best regards,
ManuelI second that and would even like to see multiple auto-resize settings for upload locations like in the famous Imsanity plugin (there you can set different sizes for images uploaded while post editing or while directly uploaded to the media library).
And as I think about it, there pops this question up: I guess you use the default WordPress resize mechanism using the PHP GD image processing framework.
Which quality you choose for the resized image?This is also something I miss at the lossy setting, there should be a quality setting like in the reSmush.it plugin.
Thanks