Forum Replies Created

Viewing 15 replies - 1 through 15 (of 21 total)
  • Thread Starter Mattis

    (@ecomsight)

    Hi @mrclayton

    I just figured out the issue, it is coming from Cross Origin Opener Policy that was set to same-origin-allow-popups. Changing it to unsafe-none works well, popup is automatically reloaded with Secret key / Client ID saved.

    Not sure if it is something that could be improve later on (the loading throughout popup) or if it is Paypal constraint.

    Thanks! (your Stripe / Paypal plugins are excellent)

    Thread Starter Mattis

    (@ecomsight)

    Hi @mrclayton

    Thanks for your reply

    What happens when you click the “Return to the Test Store website”?

    It reloads the popup where the connection with Paypal was done, and loads the wordpress backoffice inside the popup (the Paypal API settings page), and all fields remain empty.

    On Paypal side new application is well created, and if I complete Secret key / Client ID fields manually on Paypal API settings page and click on Create Webhook button, Webhook ID is well fetched and saved.

    Would it be something on wordpress admin side blocking this automatic loading / fetching from Paypal? Did you already experience this type of issue?

    Edit:

    I did additional testing and found the following error on Paypal side before clicking on “Agree and connect” button:

    HF_ERR_HeaderNotFound {errorMsg: '[header-footer] could not find .merchant-header element. Cannot render header.', timestamp: '1705692427467'} hf.js:2

    Thank you for your support

    • This reply was modified 2 years, 2 months ago by Mattis.
    Thread Starter Mattis

    (@ecomsight)

    Hi Chris,

    Ok thank you for the explanation and your quick reply!

    Hello,

    Thank you but unfortunately it still does not work for sub sites, it creates new following fatal error (admin / front can not be loaded):

    Fatal error: Uncaught Error: Call to undefined function Code_Snippets\Cloud\wp_generate_password() in /home/clients/1/sites/clients-1-stg.com/wp-content/plugins/code-snippets-pro/php/cloud/class-cloud-api.php:239 Stack trace: #0 /home/clients/1/sites/clients-1-stg.com/wp-content/plugins/code-snippets-pro/php/cloud/class-cloud-api.php(82): Code_Snippets\Cloud\Cloud_API->init_oauth_sync() #1 /home/clients/1/sites/clients-1-stg.com/wp-content/plugins/code-snippets-pro/php/class-plugin.php(126): Code_Snippets\Cloud\Cloud_API->__construct() #2 /home/clients/1/sites/clients-1-stg.com/wp-content/plugins/code-snippets-pro/php/load.php(65): Code_Snippets\Plugin->load_plugin() #3 /home/clients/1/sites/clients-1-stg.com/wp-content/plugins/code-snippets-pro/code-snippets.php(62): require_once('/home/clients/7...') #4 /home/clients/1/sites/clients-1-stg.com/wp-settings.php(418): include_once('/home/clients/7...') #5 /home/clients/1/sites/clients-1-stg.com/wp-config.php(110): require_once('/home/clients/7...') #6 /home/clients/1/sites/clients-1-stg.com/wp-load.php(50): require_once('/home/clients/7...') #7 /home/clients/1/sites/clients-1-stg.com/wp-blog-header.php(13): require_once('/home/clients/7...') #8 /home/clients/1/sites/clients-1-stg.com/index.php(17): require('/home/clients/7...') #9 {main} thrown in /home/clients/1/sites/clients-1-stg.com/wp-content/plugins/code-snippets-pro/php/cloud/class-cloud-api.php on line 239

    It works with version 3.5.1.

    Thank you for your support.

    • This reply was modified 2 years, 4 months ago by Mattis.

    Hello,

    I also have Fatal error when updating to latest Pro version 3.6.1. I did a fresh installation, WP 6.4.1 X PHP 8.2 X multi-site mode and it crashes when plugin is activated. There is no other plugin activated. Version Pro 3.5.1 is working.

    Fatal error: Uncaught Error: Undefined constant "SECURE_AUTH_COOKIE" in /home/clients/web/sites/clients-1-domain.com/wp-includes/pluggable.php:929 Stack trace: #0 /home/clients/web/sites/clients-1-domain.com/wp-includes/pluggable.php(694): wp_parse_auth_cookie(false, '') #1 /home/clients/web/sites/clients-1-domain.com/wp-includes/class-wp-hook.php(324): wp_validate_auth_cookie(false) #2 /home/clients/web/sites/clients-1-domain.com/wp-includes/plugin.php(205): WP_Hook->apply_filters(false, Array) #3 /home/clients/web/sites/clients-1-domain.com/wp-includes/user.php(3628): apply_filters('determine_curre...', false) #4 /home/clients/web/sites/clients-1-domain.com/wp-includes/pluggable.php(70): _wp_get_current_user() #5 /home/clients/web/sites/clients-1-domain.com/wp-includes/l10n.php(98): wp_get_current_user() #6 /home/clients/web/sites/clients-1-domain.com/wp-includes/l10n.php(152): get_user_locale() #7 /home/clients/web/sites/clients-1-domain.com/wp-includes/l10n.php(1300): determine_locale() #8 /home/clients/web/sites/clients-1-domain.com/wp-includes/l10n.php(1331): _load_textdomain_just_in_time('code-snippets') #9 /home/clients/web/sites/clients-1-domain.com/wp-includes/l10n.php(185): get_translations_for_domain('code-snippets') #10 /home/clients/web/sites/clients-1-domain.com/wp-includes/l10n.php(297): translate('Success', 'code-snippets') #11 /home/clients/web/sites/clients-1-domain.com/wp-content/plugins/code-snippets-pro/php/class-licensing.php(170): __('Success', 'code-snippets') #12 /home/clients/web/sites/clients-1-domain.com/wp-content/plugins/code-snippets-pro/php/class-licensing.php(64): Code_Snippets\Licensing->override_strings() #13 /home/clients/web/sites/clients-1-domain.com/wp-content/plugins/code-snippets-pro/php/class-plugin.php(134): Code_Snippets\Licensing->__construct() #14 /home/clients/web/sites/clients-1-domain.com/wp-content/plugins/code-snippets-pro/php/load.php(65): Code_Snippets\Plugin->load_plugin() #15 /home/clients/web/sites/clients-1-domain.com/wp-content/plugins/code-snippets-pro/code-snippets.php(62): require_once('/home/clients/7...') #16 /home/clients/web/sites/clients-1-domain.com/wp-settings.php(418): include_once('/home/clients/7...') #17 /home/clients/web/sites/clients-1-domain.com/wp-config.php(102): require_once('/home/clients/7...') #18 /home/clients/web/sites/clients-1-domain.com/wp-load.php(50): require_once('/home/clients/7...') #19 /home/clients/web/sites/clients-1-domain.com/wp-admin/admin.php(34): require_once('/home/clients/7...') #20 /home/clients/web/sites/clients-1-domain.com/wp-admin/network/admin.php(13): require_once('/home/clients/7...') #21 /home/clients/web/sites/clients-1-domain.com/wp-admin/network/plugins.php(11): require_once('/home/clients/7...') #22 {main} thrown in /home/clients/web/sites/clients-1-domain.com/wp-includes/pluggable.php on line 929
    

    Thank you for your support

    • This reply was modified 2 years, 4 months ago by Mattis.

    Hello @virtual03

    FYI the following temporary solution resolves the issue.

    In file woocommerce/includes/shortcodes/class-wc-shortcode-checkout.php, line 390, replacing true by false.

        if ( ! empty( $_POST ) && ! wp_verify_nonce( $_POST['check_submission'] ?? '', 'wc_verify_email' ) ) {
            return false;
        }

    Thanks

    Thread Starter Mattis

    (@ecomsight)

    Hello @babylon1999

    Thank you for your answer but adding this line to functions.php does not work in case, but I found the following solution to resolve it.

    In file woocommerce/includes/shortcodes/class-wc-shortcode-checkout.php, line 390, replacing true by false.

        if ( ! empty( $_POST ) && ! wp_verify_nonce( $_POST['check_submission'] ?? '', 'wc_verify_email' ) ) {
            return false;
        }

    Now guest customers get thank you page with order details information after they pay the order.

    Thank you

    Thread Starter Mattis

    (@ecomsight)

    Hello,

    Yes 2nd option, to make it multilingual and send emails to users in different countries in their respective native languages. 

    Will wait for the upgrade.

    Thank you!

    Thread Starter Mattis

    (@ecomsight)

    Hello @ppjessie

    I have updated plugin with latest version 3.2.1 which supports WPML but email subject does not still translate with the right language.

    String is well translated in WPML plugin but the subject is still in english when email is sent.

    See screenshots here

    WPML integration is checked in ParcelPanel > Integrations, and tracking page is well translated now.

    Is there something to do to have the right translations for email subjects?

    Thank you

    Thread Starter Mattis

    (@ecomsight)

    Hello @solstudioim

    Apoloogies for the delay. Yes exactly, all guests are redirected to thank you page, but they’re asked to supply an email.

    There is currently this development on-going > https://github.com/woocommerce/woocommerce/pull/39758

    Hope it will fix this annoying issue!

    Thank you

    Thread Starter Mattis

    (@ecomsight)

    Hello @xue28 , @anastas10s

    I went through additional testing with Elementor support team and also throughout this feed https://wordpress.org/support/topic/thanks-page-changed/ but at the end it points to the following commit which was done along the release of Woo version 7.8 > https://github.com/woocommerce/woocommerce/commit/1cd947a32064bf3b716521110eae2856711ab775

    Also there is an ongoing discussion there > https://github.com/woocommerce/woocommerce/pull/38983 highlighting the way this new piece of code was done, and impacting thank you page for all guest customers.

    Do you know if a fix would be done there?

    This issue is quite annoying as it is impacting the use of other plugins and displaying a log-in request for all guest customers which is not expected at all there.

    Thank you for your support!

    • This reply was modified 2 years, 8 months ago by Mattis.

    Hello @mrclayton

    We went through additional testing / debugging with Cartbounty support team and it seems that the following lines impact this issue where guest customers are requested to log-in on order confirmation page (after order is paid).

    In file woo-stripe-payment\includes\class-stripe.php, from lines 428 to 430

    if ( ! did_action( 'before_woocommerce_init' ) ) {
    return false;
    }

    When these lines are commented, the issue does not happen anymore. But what is confusing is that this issue is happening since Woocommerce did the following commit > https://github.com/woocommerce/woocommerce/commit/1cd947a32064bf3b716521110eae2856711ab775

    Is this hook triggered from lines 428 to 430 is mandatory to be triggered on order confirmation page? (as it seems to handle fields on checkout page).

    Thank you for your support (FYI when the other Stripe plugin is activated instead the issue does not happen as well).

    Hello @virtual03

    Indeed issue appears since Woocommerce 7.8 (issue is not there with version 7.7.X)

    But are you using Elementor as well?

    Thanks

    Hello @virtual03

    Thank you, I also have CartBounty plugin installed, and issue does not appear when it is deactivated. But it also seems to be related to Elementor pro plugin. When CartBounty plugin is activated with Gutenberg editor instead of Elementor pro, issue is not there…

    Are also using Elementor pro? (I have open a ticket with elementor support, they are currently looking at it)

    Thanks

    Thread Starter Mattis

    (@ecomsight)

    Hello @anastas10s

    Thank you for your reply, Im still investigating the issue but seems related to Elementor Pro. Website impacted is bymattis.com and there is no plugin like deposit or subscription installed there.

    Will keep you updated.

    Thanks!

Viewing 15 replies - 1 through 15 (of 21 total)