Forum Replies Created

Viewing 15 replies - 1 through 15 (of 48 total)
  • Thread Starter BDR Bros.

    (@bdrbros)

    @tonyrobins @nicholas2019 @keysuck

    I’ve done my tests and in addition to solving the transparency issues in PNG, with the latest version of Imagick we get much better quality JPGs at almost identical size. I think this could be interesting and motivating to upgrade Imagick.

    Compression comparison for Imagick 6.9.X and 7.1.X
    Thread Starter BDR Bros.

    (@bdrbros)

    Hello @keysuck

    Unfortunately, a lot depends on the environment / web hosting control panel you are using. The configuration files are located in different places and unfortunately there is no universal solution for everyone. I use CyberPanel (OpenLiteSpeed) + Ubuntu 22.04 + Imagick extension for PHP 8.3. By default, Imagick is version 6.9.X. To get version 7.1.X I had to do a lot of research and it took me a few days.

    Best,
    Alex

    Thread Starter BDR Bros.

    (@bdrbros)

    Many thanks again for reporting and for helping resolve the issue!

    It’s my pleasure. We are in touch.

    Thread Starter BDR Bros.

    (@bdrbros)

    @tonyrobins I have forwarded to Nicholas the information that the problem is due to the implementation of EXIF ??data removal. With the EXIF ??data removal option enabled, the image is additionally processed. Please confirm that you received my email with the information.

    Best,
    Alex

    Thread Starter BDR Bros.

    (@bdrbros)

    Przyk?adowy scenariusz.

    Mamy w sklepie 100k produktów. Zanim plugin wype?ni baz? pocz?tkowymi danymi i b?dzie mo?na go u?ywa? minie przynajmniej kilka godzin. Tabela wp_postmeta zostanie ju? na start zbombardowana zapychaj?cymi j? rekordami.

    Przed wersj? 2.0 (gdy nie by?o “pierwszego skanowania”), gdy ustawili?my:

    – “Day before product went on sale (excludes promotional price)”
    – “Number of days to use when counting minimal price: 30”

    A nast?pnie ustawili?my promocj?, to jako najni?sz? cen? pokazywa?o aktualn? cen? (cen? promocyjn?), zamiast wcze?niejszej ceny (ceny przed promocj?). Dlatego jak rozumiem stworzy?e? mechanizm, który pobiera wszystkie aktualne ceny produktów po aktywacji pluginu, aby by?o si? do czego odnosi?.

    Czy nie lepsz? logik? by?oby pobieranie starej ceny i timestampa dopiero w momencie edycji ceny (wprowadzania promocji), a nie robienie tego ju? na starcie dla wszystkich produktów?

    Pozdrawiam ??

    Thread Starter BDR Bros.

    (@bdrbros)

    We’ve just released a new version of the plugin to fix the issue. You can update the plugin and check it out.

    Checked. Method: Imagick. Compresion: Lossless

    • Original size : 137,78 KB
    • Webp size : 46,46 KB Saved : 66.28%
    • AVIF size : 25,91 KB Saved : 81.19%

    So… It’s probably worse, i.e. even Webp now bypasses the compression level settings.
    I also tested other compression levels (e.g. 85%) and the results are the same/similar.

    _____

    Thank you for such great involvement. I really like your project. I use WPVivid and I support you. I will wait for further development of the plugin. I hope that the most important problems will be removed soon.

    • This reply was modified 3 months, 1 week ago by BDR Bros..
    Thread Starter BDR Bros.

    (@bdrbros)

    @tonyrobins

    1. You’re right, it’s related to Imagick version 6 (1691, ImageMagick 6.9.11-60) + AVIF. People who use shared servers may not be able to update Imagick, so I don’t know if the option to exclude formats wouldn’t be a good solution (but I’m not pushing this option).
    2. It’s good that you know where the problem lies, that’s half the battle ??

    New thoughts:
    B1. Some sections have a “Save Changes” button and some don’t. This inconsistency sometimes makes me wonder if when I press an option, it’s saved and if I can refresh the page.

    B2. It’s possible to optimize a specific image in the media library, but I don’t see the option to delete optimized versions for a specific image (only deleting all images via the “Delete Images Generated by CompressX” option). Did I miss something, or is it not implemented? If it’s not implemented, will it be implemented in the future?


    Best,
    Alex

    Thread Starter BDR Bros.

    (@bdrbros)

    Can you do such a test yourself? This won’t seem correct.

    https://screenrec.com/share/MdJc3k6DuA

    https://screenrec.com/share/2ZO4TfVp1i

    Thread Starter BDR Bros.

    (@bdrbros)

    There is no need. I now know how to fix this problem myself.

    I thought it might be a problem in the plugin code, if not I will fix my snippets to make them compatible.

    Thank you again for your help ??

    Thread Starter BDR Bros.

    (@bdrbros)

    Out of several thousand subpages, the critical error occurs only on the “/wp-admin/edit.php?post_type=site-review” subpage, so I concluded that the conflict is on the WPCodeBox <-> Site Reviews line.

    The name of the function does not matter, it can be completely random and it is still performed several times on this subpage. If there is no other solution, they will modify their snippets according to your recommendation. Thank you for your tips.

    Thread Starter BDR Bros.

    (@bdrbros)

    Exaple:

    add_action( 'template_redirect', 'my_redirect_author_page_to_home' );
    
    function redirect_author_page_to_home() {

    to:

    add_action( 'template_redirect', function() {

    And then it works properly.

    • This reply was modified 9 months, 1 week ago by BDR Bros..
    Thread Starter BDR Bros.

    (@bdrbros)

    [16-Feb-2024 10:33:24 UTC] PHP Fatal error: Cannot redeclare redirect_author_page_to_home() (previously declared in /home/domain.pl/public_html/wp-content/plugins/wpcodebox2/src/Runner/QueryRunner.php(126) : eval()'d code:10) in /home/domain.pl/public_html/wp-content/plugins/wpcodebox2/src/Runner/QueryRunner.php(126) : eval()'d code on line 9
    

    I spoke to the developer of WPCodeBox and he is unable to do anything about this fact. I can only anonymize the function or change the hooks.

    Thread Starter BDR Bros.

    (@bdrbros)

    Ajajaj. Faktycznie, mój b??d ?? Ju? ticket polecia? w odpowiednie miejsce.

    Przepraszam, pozdrawiam, ?ycz? mi?ego dnia.
    Aleksander

    • This reply was modified 11 months, 3 weeks ago by BDR Bros..
    Thread Starter BDR Bros.

    (@bdrbros)

    Ohhh. Only Cache level: cache everything. Should I add Bypass Cache on Cookie: user_platform?

    Should this help?

    Thread Starter BDR Bros.

    (@bdrbros)

    Great news! So I take back my words about forcing WEBP.

Viewing 15 replies - 1 through 15 (of 48 total)