• Received the following warnings on the frontend, and the payhub option never loads at checkout:

    Warning: include_once(/com/payhub/ws/extra/includeClasses.php): failed to open stream: No such file or directory in /home/bestfur6/public_html/wp-content/plugins/payhub-payment-gateway-for-woocommerce/woocommerce-payhub.php on line 10

    Warning: include_once(): Failed opening ‘/com/payhub/ws/extra/includeClasses.php’ for inclusion (include_path=’.;/path/to/php/pear’) in /home/bestfur6/public_html/wp-content/plugins/payhub-payment-gateway-for-woocommerce/woocommerce-payhub.php on line 10

    While activated, cannot access /wp-admin. When deactivated and reactivated from backend, receive the same warnings as well as:

    The plugin generated 560 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    Tried deleting and reinstalling the plugin, as well as testing for conflicts with the theme and other plugins. Continuing to troubleshoot. Last update says it was 2 days ago, but it’s the same release version from November on the changelog. Could this be a WordPress 4.7 compatibility error?

    Any help is appreciated.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Same issue here…

    Plugin Author PayHub, Inc

    (@payhub)

    Hi, we are working in a new release to solve this path error.

    Thread Starter atransmit

    (@atransmit)

    Thanks!

    Updated the plugin to 1.0.14 and tried it out, but received an invalid API token error when attempting to check out, and the test connection option just registers “not connected”. Continuing to troubleshoot.

    Could the conflict/update be causing any issue with recognizing the API token? Nothing has changed with the payhub account or virtual terminal credentials since the last transaction on 12/8 (before the WP 4.7 update).

    • This reply was modified 7 years, 4 months ago by atransmit. Reason: Update
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error with update to WordPress 4.7’ is closed to new replies.