• Resolved eimaste

    (@eimaste)


    WC Version: 9.7.1
    Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.
    Action Scheduler Version: ✔ 3.9.0
    Log Directory Writable: ✔
    WP Version: 6.7.2
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    WP Cron: ✔
    Language: en_US
    External object cache: – Server Environment

    Server Info: nginx
    PHP Version: 8.2.26
    PHP Post Max Size: 10 MB
    PHP Time Limit: 60
    PHP Max Input Vars: 1000
    cURL Version: 7.88.1
    OpenSSL/3.0.15


    Astra Pro: by Brainstorm Force – 4.9.1
    BytePlugs Invoice Checkout Fields Timologio: by BytePlugs – 1.1.0
    Contact Form 7: by Takayuki Miyoshi – 6.0.4
    Contact Form CFDB7: by Arshid – 1.2.10
    Delete Me: by Clinton Caldwell – 3.2
    Flexible Refund and Return Order for WooCommerce: by WP Desk – 1.0.30
    FluentSMTP: by FluentSMTP & WPManageNinja Team – 2.2.90
    OG — Better Share on Social Media: by Marcin Pietrzak – 3.3.4
    Spectra Pro: by Brainstorm Force – 1.2.0
    Spectra: by Brainstorm Force – 2.19.2
    WooCommerce: by Automattic – 9.7.1

    Hello we have the above configuration. After migrating from local dev to a online host, we started having the situation where on requesting a refund the status of the refund is set as UKNOWN and just the order table is rendered.

    We tried to deactivate/uninstall and setup again the plugin but it seems that the plugin in not cleaning up properly, but either way we get the same error.

    Any ideas on how to resolve it?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support sebastianrybacki

    (@sebastianrybacki)

    Hello,

    Thank you for reaching out to us.

    I tried to replicate the issue in my test environment, but I was unable to reproduce it. This suggests that the problem might be related to your specific environment—possibly due to certain filters or other plugins conflicting with Flexible Refunds and Return Orders.

    To troubleshoot the issue, please follow these steps:

    1. Test with the default Storefront theme – Switch to the Storefront theme and check if the issue persists. If the problem disappears, it may be related to your current theme.
    2. Disable all plugins except WooCommerce and Flexible Refunds – If changing the theme does not help, deactivate all other plugins and keep only WooCommerce and Flexible Refunds enabled. Then, test the refund process again.
    3. Identify the conflicting plugin – If the issue is resolved after disabling other plugins, re-enable them one by one (or in small groups) to determine which plugin is causing the conflict.

    Please let me know the results of these tests. If we can identify a specific plugin causing the issue, I will add it to our compatibility review list for future updates.

    If none of these steps resolve the issue, please let me know.

    Kind regards,

    Thread Starter eimaste

    (@eimaste)

    Thanks for your response!

    I tried with just the storefront theme and Woocommerce/Flexible Refunds as the sole plugins and the issue persists.

    To be honest, I don’t think it is a plugin conflict, since locally I have exactly the same set of plugins and there is no issue.

    I think that maybe some data stored in the database (probably not correctly migrated during the transfer) is the issues. Is there an easy way to clean all the data that the plugin writes to the database? I would like to try to do a to a “hard reset” of the plugin, but the uninstall hooks don’t seem to clear data.

    Plugin Support sebastianrybacki

    (@sebastianrybacki)

    Hello,

    Thank you for your response and for testing with just the Storefront theme and the essential plugins.

    Since the issue persists even after disabling other plugins, and considering that your local environment works fine, it is possible that some metadata related to refunds wasn’t correctly migrated during the transfer.

    To investigate further, could you please check the following:

    1. Does the issue occur with a newly created order?
      If the problem only affects orders that existed before the migration, it might indicate missing or incorrectly migrated metadata.
    2. Check for missing metadata in the order.
      The plugin relies on certain order metadata, such as 'fr_refund_request_status'. If this metadata is missing or incorrect, it could lead to unexpected behavior.
    3. Does a refund note appear in the order notes section?
      When processing a refund, the plugin should log a note in the order’s history. Checking whether this note appears might provide further insights.

    Additionally, please check your WooCommerce logs (WooCommerce > Status > Logs) for any errors related to the refund process. If there are any error messages, they might help identify the root cause.

    Please let me know what you find, and we’ll assist you further!

    Best regards,

    Thread Starter eimaste

    (@eimaste)

    Hello again, yes it seems that some metadata did not migrate correctly to the new host.

    The problem is not appearing on new orders, so consider this resolved. Thanks for your help!

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

The topic ‘REFUND STATUS: UNKNOWN’ is closed to new replies.