Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter Daniel Harper

    (@danhrpr)

    No problem, thanks for fixing it so quickly.

    Thread Starter Daniel Harper

    (@danhrpr)

    This is the issue,

    Error: PHP warning/error — Array to string conversion in Renderer.php when building inline styles for <code class=””>–wp–style–block-gap.

    Carousel detection scans $block_content for “<code class=””>abcs”, so a parent block (e.g. core/columns) is treated as a carousel when a nested carousel is inside it;

    Carousel gap logic then runs on that parent, whose blockGap is an object like “<code class=””>{ “top”: “0” }” instead of a string.

    If you put a carousel query loop inside any of the following and update the block gaps you get the warning in the log file or on the screen if you have them set to dispaly.

    core/columnscore/column, or core/group

    I have a patch for it if you want I can send it to the support email address?

    I would not give random admin access to a plugin maintainer, that’s ridiculous.

    Thread Starter Daniel Harper

    (@danhrpr)

    Thanks for the quick resposne,

    I can see the nonce is cached in the html but I do need to cache the html on the product pages, it’s easier with cart etc because I have cache exclusions. I also have exclusions when specific cookies exist so not sure how I can get around this one.

    do you have any pointers on that?

    If I reduce the cache time and page is refreshed every 4hrs then it should work?

    Cheers Dan

    Thread Starter Daniel Harper

    (@danhrpr)

    Hi @alexmigf

    This is working perfectly and the plugin status page is really great.

    Thanks again Dan

    Thread Starter Daniel Harper

    (@danhrpr)

    Thanks very much for this, I will try and get it tested this week.

    Thread Starter Daniel Harper

    (@danhrpr)

    Hi @alexmigf ,

    Unfortunately that hasn’t worked, I get the following message when the FS_METHOD option is removed from the config file with the file setting set to PHP

    Fatal error: Uncaught Error: Call to undefined function WPO\IPS\Compatibility\wcpdf_log_error() in /app/web/app/plugins/woocommerce-pdf-invoices-packing-slips/includes/Compatibility/FileSystem.php:94 Stack trace:
    #0 /app/web/app/plugins/woocommerce-pdf-invoices-packing-slips/includes/Compatibility/FileSystem.php(62): WPO\IPS\Compatibility\FileSystem->initialize_wp_filesystem()
    #1 /app/web/app/plugins/woocommerce-pdf-invoices-packing-slips/includes/Compatibility/FileSystem.php(46): WPO\IPS\Compatibility\FileSystem->__construct()
    #2 /app/web/app/plugins/woocommerce-pdf-invoices-packing-slips/woocommerce-pdf-invoices-packingslips.php(150): WPO\IPS\Compatibility\FileSystem::instance()
    #3 /app/web/app/plugins/woocommerce-pdf-invoices-packing-slips/woocommerce-pdf-invoices-packingslips.php(185): WPO_WCPDF->includes()
    #4 /app/web/wp/wp-includes/class-wp-hook.php(324): WPO_WCPDF->load_classes('')
    #5 /app/web/wp/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #6 /app/web/wp/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #7 /app/web/wp/wp-settings.php(704): do_action('init')
    #8 /app/web/wp-config.php(9): require_once('/app/web/wp/wp-...')
    #9 /app/web/wp/wp-load.php(55): require_once('/app/web/wp-con...')
    #10 /app/web/wp/wp-admin/admin.php(34): require_once('/app/web/wp/wp-...')
    #11 /app/web/wp/wp-admin/plugins.php(10): require_once('/app/web/wp/wp-...')
    #12 {main} thrown in /app/web/app/plugins/woocommerce-pdf-invoices-packing-slips/includes/Compatibility/FileSystem.php on line 94

    If I have “FS_METHOD=direct” in the config file I can go in and change the setting to PHP file system in the plugin but as soon as I remove the FS_METHOD i get the issue again.

    Seemingly if I have “FS_METHOD=direct” in the config everything seems work and if I try to update plugins through the UI they just fail which is what I want.

    Cheers Dan

    Thread Starter Daniel Harper

    (@danhrpr)

    I am not using elementor.

    Although harmless I want the log file as clean as possible so when we get real errors it’s easier to find them rather than wading through notices and exceptions. Other than this and one other plugin adding an exception the log file is clean.

    Are you saying that this plugin registers everything correctly as per the docs?

    Thread Starter Daniel Harper

    (@danhrpr)

    I will double check how the order status is being changed in the order system plugin, perhaps they are changing it with their own custom API instead of the default Woo one.

    Thread Starter Daniel Harper

    (@danhrpr)

    Just to add, the order status change is being triggered through the an api.

    It’s an order system that’s changing the order status not a user.

    Thread Starter Daniel Harper

    (@danhrpr)

    Hi @mrclayton,

    This does seemed to have solved the issue.

    Is this a bug or is it just something that can’t technically be solved?

    Cheers Dan

    Did you find the issue with this?

    I seem to have a similar problem, no config changes that I recall and no code changes either.

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