debug log for AVIF Plugin

  • Resolved Dr. Melvin Temo

    (@temovision)


    2 days, 18 hours ago

    See below the extracts of the debug log for the plugin: seems to be misfiring:

    [15-Jun-2026 00:48:14 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'FROM wp_ipr_avif_conversions' at line 2 for query SELECT PERCENTILE_CONT(0.9) WITHIN GROUP (ORDER BY original_size)
                     FROM wp_ipr_avif_conversions made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, IPR_AVIF_Queue->process_if_due, IPR_AVIF_Queue->process, IPR_AVIF_Queue->estimate_ram_batch
    [15-Jun-2026 00:48:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>disable-dashboard-for-woocommerce</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a>
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Dr. Melvin Temo

    (@temovision)

    2 days, 16 hours ago

    See: https://tmpfiles.org/wawyUJj11Cnh/screenshot2026-06-15064548.png

    Plugin Author Marco Di Giacomantonio

    (@marcodigiacomantonio)

    2 days, 12 hours ago

    Hi Melvin,

    Good news on the log line you pasted earlier: it’s fixed. The RAM batch estimator was running a PERCENTILE_CONT query that MySQL 8 and MariaDB don’t support in that form, so it threw a syntax error into your debug log on every queue run. A fallback was already handling the actual calculation, so conversions were never affected — it was log noise, not a functional bug. I’ve replaced it with a portable percentile calculation, released just now in v1.9.8. Once you update, that error will stop appearing.

    While I was at it I also corrected the declared “Requires PHP” to 8.1 to match the codebase.

    On the second item: as a rule I don’t open files hosted on external/temporary file-sharing links from support threads — nothing personal, it’s just a security practice I keep to. If there’s anything else in your log you’d like me to look at, the best way is to paste the relevant lines directly here as text and I’ll dig into them right away. The PHP notice about the “disable-dashboard-for-woocommerce” text domain, for what it’s worth, comes from that other plugin and isn’t related to this one.

    Thanks again — update to 1.9.8 and let me know if anything still shows up in the log.

    Marco
    I-PR AVIF Converter

    Thread Starter Dr. Melvin Temo

    (@temovision)

    2 days, 10 hours ago

    Excellent thank you. Fixed

    About external file, I use that to demonstrate the bug, without saving the image on my server as this is for demonstration purposes and these files automatically expire later on , on a temp domain. Maybe you could recommend your preferencial temp site. It is worth nothing at wordpress.org does not allow image uploads here, so it tricky.

    Plugin Author Marco Di Giacomantonio

    (@marcodigiacomantonio)

    2 days, 9 hours ago

    Glad it’s fixed! And thanks for explaining — that makes sense, and you’re right that wordpress.org doesn’t allow image uploads in the forum, so I understand the need for an external link.

    For sharing screenshots, my honest recommendation is to skip the temporary file-hosts — some of them wrap the download page in aggressive ads/redirects that can land on sketchy pages, which is the only reason I didn’t open the earlier ones (nothing personal, just a habit I keep). A couple of cleaner options:

    • Imgur (imgur.com) or a GitHub Gist for images — direct, no redirects, free.
    • For logs specifically, the easiest is to just paste the relevant lines as plain text right here in the reply. Text is actually better than a screenshot for me anyway, because I can copy the exact query or error string and search the codebase for it directly.

    So for anything log-related, plain text in the thread is ideal. For visual stuff (UI glitches etc.), an Imgur link works great.

    Thanks again for all the testing — genuinely made the plugin better this week.

    Marco
    I-PR AVIF Converter

    Thread Starter Dr. Melvin Temo

    (@temovision)

    2 days, 9 hours ago

    Great and thanks for you recommendation. Will register at imgur.

    Sure I will paste code errors here if any issues arise

    I am grateful for all the timely fixes. Cheers

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.