audioscavenger

@asif_rn I only use broken link checker atm, will revisit the others. whisper is not the only one that promises stuff but does not deliver. I have nothing against making money! I make money too, but my take is if you are selling smth just say it, don’t say there is a free version to try out when there is nothing to try.

After thinking it over again, it’s clearly a design issue, and my own fault. Do NOT use widgets taller then the screen height.

The Paste disables Rich text format pastes in classic editor. All lost, formatting, bullets, etc.

Must disable the TinyMCE integration. Just so you know..

Thank you for your reply, you make a lot of sense, and I feel you. Sometimes I too get excited with a new project, starts dev and publish, and then go back to the family routine and forget about it.

Maybe a Github discussion would be better then here…

Conversion method: well, let’s say I got AVIF 100% working but only because of AVIF Support [GrandPlugins] plugin. It adds the well-known AVIF snippet to enable avif, but also a bunch of hooks and filters to call GD or Imagick, as simple as that. When you upload something, it automatically generates all the matching thumbnails in avif format. You still get the same image format thumbnails, that’s WordPress Core. Nothing new under the sun.

The real power in your plugin, as I see it, really, is the .htaccess rules. That’s where the magic happens.

The way I see it, without having you or me re-inventing the wheel, is to simply offer the choice between webp and avif. You cannot offer both, it makes no sense.

• how would you fallback from avif to webp to original, how many htaccess rules will you need?
• if your system accepts webp, it likely also accepts avif
• PHP-Imagick 6.9.11+ supports avif and is likely integrated in most systems
• webp vs avif is a debate I will not start, but webp is pure crap is what I can tell
• only downside of avif is the compute power required to generate them

I think a good chat would be better, to decide the best way to handle this with least amount of effort. Also you have more experience in plugins dev then I do, and already are working on this new plugin converter of yours (not published yet). You should take the lead. I tried renaming all I can in your plugin to get rid of “WebP” in the class/functions/variable names etc but ended up breaking it. Best I could do is alter the “.webp” (webp) and image/webp parts. That’s already a dozen files.

The controversy I think for most people is whether original files should be converted, for the sake of saving a mere 50% of server space. I think the best method is the vary/rewrite rules. Until we can work with avif natively… ALL major browser support avif as of today, including mobiles. I don’t see the point in holding us back.

@oferlaor use my secret gist to update yours lol

now working on adding AVIF paste as well. webp is crap, when you look closely.

Not sure you want or have time to do it, and I seem to be the only one pasting stuff from the clipboard, asking for it.

As a fellow dev, I did the job for you. here is the gist

• makes WebP the default for clipboard pastes
• clicks the matching format after pasting, only if mime detected is png
• does nothing if pasting actual webp/jpeg files, as expected

• This reply was modified 7 months, 3 weeks ago by audioscavenger.

Error reported, analyzed by plugin author, fixed and released immediately by plugin author @farhad0 = KUDOS to him!

Thank you on behalf of all your users.

hi, my audit log table was 1GB and I could not even open the Audit Logs tab. UI just crashes.
TRUNCATE table fixed it. I agree that none of the information in this table is relevant.
Please provide a an option to disable it.

FIXED

Sorry to have suspected your plugin, it was the one that did the most modifications so far, seemed like the culprit!

• your plugin does NOT modify links in the db, I verified that
• culprit was nginx swag proxy: expiry of 1month for files bugged out completely:

location ~* ^.+.(jpe?g|png|gif|webp|ico|eot|otf|woff|woff2|ttf)$ {
expires 1M;
}

Adding heaxpiry headers is recommended eberywhere, so I did. disabling it resolved the situation.

reactivated your plugin, THANK YOU

• disable the WP Hide plugin, done
• Further check the .htaccess file: done, no wp-hide lines?
• check files are on the server and yes they are, owned by www-data, correct permissions

did your plugin modify anything in the image posts inside the db? i am searching for them right now

FYI the zoom function is provided by woocommerce

plugins/woocommerce/assets/js/zoom/jquery.zoom.min.js: Zoom 1.7.21
plugins/woocommerce/assets/js/zoom/jquery.zoom.js: Zoom 1.7.21

thanks for helping! not sure a video would help, but here is what you see on any single product page:

every jpeg images from uploads is correctly served as webp, but not the larger one used for zoom over the product. below is the element:

the best solution would be for WordPress to finally handle webp natively but I am not a decision maker. webp is still a new format only used by 95% of all mobile and desktop web browsers in 2023.

I really don;t know which browser in 2023 cannot handle webp and honestly, the next step is simply to modify your single-product.php functions to server webp natively and be done with it. But hopefully we can figure out a more generic approach that can help others?

okay i gave up and installed the testing version of webp 1.2.4 on the container directly.

trying to compile cwebp myself for arm but troubled with building with static libraries. would you mind share the configure flags with me please? i am almost there, just libjpeg.so.8 is giving me trouble:

./configure LDFLAGS=-static --disable-shared LIBS='-Wl,-static,-ljpeg,-lpng16,-lm,-lz,-lm,-Bdynamic'

binary is valid but still requires jpeg-turbo8 as a shared library…

• This reply was modified 1 year, 7 months ago by audioscavenger.

okay lemme rephrase. Best technologies come from French speakers ??