Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Γεια σας,
    Ευχαριστούμε για το μήνυμά σας.

    Θα μπορούσατε να μας διευκρινίσετε λίγο περισσότερο τι ακριβώς εννοείτε;

    Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Regarding the issue you mentioned (“checkout options disappear from settings”), based on the behavior you’re describing, this is most likely caused by a conflict with another plugin or with the active theme on your site.

    To help me investigate this further, could you please provide the following details:

    • Your WordPress and WooCommerce versions
    • Whether you are using the Classic Checkout or WooCommerce Blocks Checkout
    • Whether HPOS (High-Performance Order Storage) is enabled
    • Please also try switching temporarily to a default theme (for example Storefront) and disabling all plugins except WooCommerce and IRIS, to check whether the issue still occurs

    With this information, I’ll be able to investigate further and advise you on the next steps.

    Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Hi there,

    Thanks for reporting this. These “Deprecated: Creation of dynamic property” notices are expected on PHP 8.2+ / 8.3 when a plugin sets class properties that haven’t been declared.

    Good news: this has already been addressed. The issue is fixed in plugin version 1.5, where the affected properties (e.g. $instructions, $vat_number, $account_holder, $qr_code, $reference_text, $vat_label, $account_holder_label) are now properly declared to ensure full PHP 8.3 compatibility.

    Please update to v1.5 and the warnings should be gone.

    Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Sure, you found the right solution. The IRIS details are added to WooCommerce emails via the woocommerce_email_order_details hook (callback: irisgw_add_iris_payment_details), so removing that action is the correct approach.

    For best compatibility, it’s recommended to run the removal after plugins are loaded, so the action definitely exists:

    add_action( ‘init’, ‘afentoulis_remove_iris_plugin_email_details’ );
    function afentoulis_remove_iris_plugin_email_details() {
    if ( has_action( ‘woocommerce_email_order_details’, ‘irisgw_add_iris_payment_details’ ) ) {
    remove_action( ‘woocommerce_email_order_details’, ‘irisgw_add_iris_payment_details’, 10 );
    }
    }

    Add it to your child theme (functions.php) or via a snippets plugin, and the IRIS payment details will no longer appear in the order emails.

    Marking this thread as Resolved. 👍

    Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Hello again,

    A quick update!

    The latest version of the plugin now fully supports the new WooCommerce Cart and Checkout Blocks, so it works seamlessly with block-based themes and the default checkout setup in modern WooCommerce installations.

    If you update to the newest release, the IRIS payment method will appear and function normally inside the Block Checkout as expected.

    Thank you once again for your patience and for using the plugin!

    Best regards,
    VGDEV Solutions

    Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Hello and thank you for your feedback!

    A new update is already in development to ensure full compatibility with the new Cart and Checkout Blocks introduced in the latest versions of WooCommerce. It will be released soon.

    Regarding the payment process, yes, the current version works as a manual payment method, and it does not yet integrate directly with the DIAS Portal for IRIS transactions. A direct integration may be considered in the future, but it’s not planned for the immediate roadmap.

    Thank you for your understanding and for using the plugin!

    Best regards,
    VGDEV Solutions

    Plugin Author vgdevsolutions

    (@vgdevsolutions)

    Thank you so much for your kind words and the 5-star review!
    I’m really glad to hear that you find the plugin useful and easy to use, that’s exactly what we aimed for!

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