BrightCherryDesign

Hi,

We’re also getting a critical error since updating to 2.9.1 this morning, so we’ve had to roll back to the previous version.

Side note, we also have a YITH plugin installed.

An error of type E_ERROR was caused in line 244 of the file /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php. Error message: Uncaught TypeError: WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package::addModule(): Argument #1 ($module) must be of type WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Module\Module, YWSBS_WC_PayPal_Payments_Module given, called in /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244
Stack trace: 0 /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule() 1 /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}() 2 /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() 3 /var/www/vhosts/example.co.uk/httpdocs/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce{closure}() 4 /var/www/vhosts/example.co.uk/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 5 /var/www/vhosts/example.co.uk/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action() 6 /var/www/vhosts/example.co.uk/httpdocs/wp-settings.php(555): do_action() 7 /var/www/vhosts/example.co.uk/httpdocs/wp-config.php(155): require_once(‘…’) 8 /var/www/vhosts/example.co.uk/httpdocs/wp-load.php(50): require_once(‘…’) 9 /var/www/vhosts/example.co.uk/httpdocs/wp-login.php(12): require(‘…’) 10 {main} thrown

@hypergolica I found the issue, and it was actually due to a plugin conflict (as initially highlighted as one of the potential issues).

In my case, it was a cookie policy plugin. Essentially, if someone didn’t accept the policy, then Stripes card payment fields wouldn’t display.

So if you have a cookie policy plugin, you might want to try disabling it and see if that fixes your issue?

(I haven’t done it yet, but I’m presuming I need to adjust the cookie policy settings so cookies used by the Stripe plugin are set as “necessary”).

Hope that helps!

• This reply was modified 5 months, 3 weeks ago by BrightCherryDesign.

8.2 doesn’t work for me – the card payment fields appear when I’m logged in as admin, not when I’m logged out.

My console log shows the following log when I’m NOT logged in: Uncaught (in promise) ReferenceError: Stripe is not defined

That error doesn’t appear when I’m logged in.

Update: I reverted back to 8.3 as @hypergolica suggested, but unfortunately the issue is still present for me.

Interestingly though, the card fields show when I’m logged in as admin, but when I log out, they don’t appear.

To clarify, do the fields appear for you when you’re not logged into a user account?

I’m having the exact same issue. On the checkout page, the credit card payment fields aren’t appearing.

I’m running the latest version of the plugin.

Hi @Maybellyne

No, it wasn’t “blog/blog”, it was just one “blog”

The structure was exactly how I wrote it (no extra “blog” or any other prefixes):

Posts page: /blog/
Category: /blog/%category-name%/
Single post: /blog/%post-name%/

Your solution doesn’t work as it adds an extra blog to the structure, so it doesn’t give the structure I wanted.

As mentioned, this worked before the update – the latest update prevents it from being possible.

Many thanks

Hi @Maybellyne

Thanks for responding.

I specified the permalink structure in my original post:

Posts page: /blog/
Category: /blog/%category-name%/
Single post: /blog/%post-name%/

This used to be possible with Strip category base?enabled, and with the following permalink settings:

Custom structure: /blog/%postname%/
Category base: .

(I also created a category with the slug “blog” to get this working.)

In the latest release, it’s no longer possible to have that specific permalink structure – all my category pages returned 404 errors, so I had to roll back the plugin version.

So it would be good to either enable an option to make it optional whether to prevent the blog page from being accessible or not, or provide some code that can once again, prevent the blog page from being accessible.

Please let me know if you require any further details.

Many thanks.

• This reply was modified 9 months, 2 weeks ago by BrightCherryDesign.
• This reply was modified 9 months, 2 weeks ago by BrightCherryDesign.

Ahhh I see. Thanks a lot, Krzysztof. I appreciate your help!

Hi,

Still getting the same error.

Many thanks

Hi Paul,

I’m getting this error:

[05-May-2015 13:29:45 UTC] PHP Fatal error: Cannot access self:: when no class scope is active in /var/www/vhostswebsite.com/httpdocs/wp-content/themes/rgactive/jigoshop/checkout/payment_methods.php on line 7

Is this a totally different issue?

I’m having the exact same problem. This seems to be a bug, which needs addressing asap because no one can make payments.

I have Paypal enabled.

I think there’s an error in the payment_methods.php file. The checkout page isn’t loading properly, it stops after the “payment method” title.

When I remove do_action(‘jigoshop_checkout_payment_methods’); from /checkout/index.php the page loads fine, but obviously the payment methods are missing!!

I’m having the same problems:

1) can’t add variations/attributes to products- the buttons don’t work
2) variable products show as “unavailable”

I tried disabling all other plugins- thought it might be a plugin conflict, but that never resolved anything.

This started happening when I updated to the latest version of JigoShop!

Has anyone got a solution?