Please wait ...


Loading...

FAQ for WooCommerce

  • Notification service
  • Get updates in your inbox.
    Sign up here.



Troubleshooting

Search for your problem or error in the above search field.

If we receive several questions on the same issue, we will add content accordingly.

General troubleshooting

If you are experiencing problems with the payment module, there are a couple of things you can try yourself to solve the problem:


1. Update to the latest version of the ePay module.


2. Change the visual theme on your shop to one for the standard WooCommerce themes. Unfortunately, some visual themes are conflicting with our payment module, so please try a standard theme.


3. Deactivate all other installed plugins/modules. Most of the support received for WooCommerce is caused by other plugins conflicting with the functionality of our payment module. Try deactivating other plugins, either all at once, or one by one to find the plugin causing the problem. Please refer to the section "Incompatible plugins" further below, for a list of plugins known to cause problems.


Please contact us regarding specific plugins that cause problems with our payment module, so we can work on improving compatibility with those plugins.

    How do I govern which payment window to use?

    To open different payment windows (with, for instance, different logos) from your shops/domains, use the setting Window ID to govern which payment window to open from the relevant domain.


    For WooCommerce, this is easy: Go to the settings for the ePay module, and put the setting Window ID at the ID of the window you want to use (default = 1).

    If this doesn’t work, remove the value completely and save. Then add it again, and  save your settings.

    What causes the error message ”Call to undefined function message”?

    When you’ve activated remote interface (API) in your module settings, you might receive the following error description:

    “Fatal error: Call to undefined function message() in .../frontend/wp-content/plugins/woocommerce-gateway-epay-dk/gateway-epay-dk.php on line 543”

    Depending on the cause, there are two possible solutions to this problem:

    1. The password you’ve indicated under remote password in WooCommerce doesn’t match the password you’ve indicated in your ePay administration under API/Webservices -> Access. To solve this, change both passwords to match each other.

    2. You haven’t added the IP address on which your e-store is located in API/Webservices -> Access in your ePay administration. Please do so.

    What does error code 403 mean?

    Error code 403 might occur when you’re using the iTgems Security plugin.

    Solve the problem by deactivating Hackrepair.com’s blacklist feature in the section ‘Banned users’-

    Contact iThemes Security here for more information.