Forum Replies Created

Viewing 15 replies - 1 through 15 (of 41 total)
  • Thread Starter Andrew Comb

    (@tecazwebdev)

    I will run some more tests on our staging site, but after a cache purge it seems to have fixed the bug in both the minicart and cart page, thanks for your rapid reply!

    Thread Starter Andrew Comb

    (@tecazwebdev)

    I’ve recreated the error on our staging site

    https://snipboard.io/FY41ZC.jpg

    And here are the settings.

    https://snipboard.io/JVgobF.jpg

    Like i said it (now) shows the correct price in checkout, but doesn’t show in the basket or mini-basket – showing as £0.

    I had to disable it on our main sites.

    Sorry about the slow reply.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    I do use the smart composite – I use legacy as the block version does not work with our postage settings. You partially fixed it. It shows add-ons as £0 on the Basket – but it works correctly at checkout. This is obviously a poor customer experience, so we have had to disable your plugin for the time being.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    NMDCCAOY

    Thread Starter Andrew Comb

    (@tecazwebdev)

    It was only inconsistent in the sense that only sometimes a user would make a product edit, then make another one just after, because they missed something. I frequently have to make purges to the site, so a lot of the times the stale cache was just purged, and no one noticed. Once I figured out the pattern, and what was broken, it’s pretty consistent to reproduce:

    Save a product – all product tags ‘gone’
    purge cache – product tags return
    Double save – product tags deleted

    My plugin code was adding an extra hooked save on publish, to store some hidden variables for a third party integration. I suspected my hook was somehow causing corruption through an undocumented WooCommerce behavior, so I refactored it to save those variables without involving the product form at all. The bug persisted, so I knew it wasn’t my code.

    No transients involved.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Ok so basically it reaches x% sometimes 0% or another random value, and it just stops, and it never resumes again. I can see in the woocommerce status > Scheduled actions it’s failed, but the task never resumes or recovers. I have to manually stop it and start it again. Most of the time it will then complete, but having to do an automated process manually is not good!

    I have tested the ‘disable http’ option, but then it just doesn’t seem to complete at all. that is not great.

    Our server limits are quite generous, and I could try and increase them, however, as I said, this has worked up till now, and it’s now not working, without anything being changed, in terms of settings.

    I could maybe try reducing the batch size with a snippet?

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Thanks for checking. That would take quite a while to narrow down, as we have a quite large store, with a lot of functions. If I get anywhere with it, I will update you.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Sure. It’s on a Litespeed server, and I am using the Kadence theme. I’m not seeing anything in the PHP or WooCommerce error logs areas, for this issue, it just silently fails. It’s slightly maddening because it doesn’t do it on all the sites I have tested, and they are all on the same server, so it could be an incompatibility with a third party plugin, but they all have similar plugin ecosystems, as it’s various testing environments.

    You load the page, it does it’s little whirry thing while it loads the table options, asynchronously, and then it just shows blank. So it’s not an error on the page, but in the jquery scripts.

    I wonder if it’s something to do with this area of the script:

    4.4.0 – 12/Dec/2025
    FIX: Fixed a potential fatal error in the WPO_Page_Optimizer class

    Because on 2 of my sites I got a fatal error on my sites (only on this page though, it did not crash my site) on the older version, but on php8.3 – updating to this version fixed it, but on php8.4 i just get a failure to show anything. Reverting to php8.3 allows the plugin to work as usual.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    I am unsure how to run a full plugin conflict test, but everything is running together under PHP 8.3, it’s just this that fails under 8.4, it’s the only thing I have noticed which ‘fails’. There are deprecation notices in Query monitor, but all of those plugins are still running, just using deprecated php code.

    I could record a video, but if you look at my attached screenshot, it pretty much looks like that… you can see there are variations, but all the controls to modify/edit them are gone. It’s hard to show an absence of something, it’s just… gone. No flicker or jankiness, just not there in the editor.

    • This reply was modified 6 months, 1 week ago by Andrew Comb.
    Thread Starter Andrew Comb

    (@tecazwebdev)

    Ok it looks like the last update of WP Crontrol fixed this issue. I’ve tentatively updated all of my Query Monitor plugins to 3.20.0, and none of them are showing anomalous errors in the cron jobs or any tasks crashing in there.

    I had a very similar error with WP-Crontrol.

    https://ww.wp.xz.cn/support/topic/version-3-20-0-causes-php-error/

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Uncaught Error: strpos(): Argument #1 ($haystack) must be of type string, null given in /xxxx/wp-content/plugins/query-monitor/output/Html.php on line 505 Call stack: strpos(NULL, ‘{closure:/’) wp-content/plugins/query-monitor/output/Html.php:505 QM_Output_Html::output_filename(NULL, ‘/xxxx/public_h…hronize_Property.php’, 67) wp-content/plugins/wp-crontrol/src/bootstrap.php:2375 Crontrol\output_callback(array) wp-content/plugins/wp-crontrol/src/event-list-table.php:722 Crontrol\Event\Table::column_crontrol_actions(stdClass) wp-admin/includes/class-wp-list-table.php:1797 WP_List_Table::single_row_columns(stdClass) wp-content/plugins/wp-crontrol/src/event-list-table.php:397 Crontrol\Event\Table::single_row(stdClass) wp-admin/includes/class-wp-list-table.php:1727 WP_List_Table::display_rows() wp-admin/includes/class-wp-list-table.php:1712 WP_List_Table::display_rows_or_placeholder() wp-admin/includes/class-wp-list-table.php:1639 WP_List_Table::display() wp-content/plugins/wp-crontrol/src/bootstrap.php:2122 Crontrol\admin_manage_page(”) wp-includes/class-wp-hook.php:324 WP_Hook::apply_filters(”, array) wp-includes/class-wp-hook.php:348 WP_Hook::do_action(array) wp-includes/plugin.php:517 do_action(‘tools_page_wp-crontrol’) wp-admin/admin.php:260 require_once(‘/xxxx/wp-admin/admin.php’) wp-admin/tools.php:40

    Just for security, I replaced my server paths with xxxx

    I hope this helps. It’s happened on about 4 of my sites, but only one of them started to get all the cronjob errors. Rolling back to 3.19.0 stopped the fatal error and cron errors

    For the latter, you can go into settings>permalinks and alter the brands permalink structure to something else, save, flushing the permalinks, and purge your cache, and your old brand attribute will come back. It’s very frustrating they’ve brought this in, we also have a 3rd party solution to brands, and this is gonna give us a real headache on all of our sites, as there’s no way to disable it, and give us 2 brands columns in the product editor & list view.

    Try going to page optimisation settings > CSS Settings> generate UCSS > OFF

    I got similiar issues, where my theme layout got damaged, but mostly in guest /incognito mode

    I found that with my theme it just didn’t work.

    Also other settings I found broke my site – General settings > Guest Mode > OFF

    Both will cause your google score to be lower, but a broken site is of no use!

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Julianosb: I tried the code snippet. The export worked great, The import didn’t work. Hopefully they “real “official” fix works.

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