lkraav

Duplicate of https://www.ads-software.com/support/topic/argumentcounterror-kadence_woomail_designeradd_email_header/ and others.

Contact RightPress plugin developers and point them at these forum URLs.

I’ve received confirmation from Memberships team they will patch templates upstream (y)

Yes, WooCommerce 3.5.6, Storefront 2.4.3 theme.

Yes, confirmed – just ran into the same issue, and multisite-activated Quicklink was the reason.

True, it’s quite useful.

This sounds like you haven’t experienced PhpStorm + Xdebug, yet, though. Probably should.

Same. This UX left a massively bad taste of the plugin build quality.

@kleepeka forgot to mention, XHTML Strict compliance is not a concern. We’re curious, who even cares about it anymore?

Github feature branch would a be more suitable avenue than zips, if possible?

First, tracebacks show this is related to is_user_logged_in() condition.
I’m profiling my text-only front page load (post type “page”).

Here’s the traceback to this plugin’s enqueue_scripts() call https://plugins.trac.www.ads-software.com/browser/woocommerce-gateway-paypal-powered-by-braintree/trunk/lib/skyverge/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php#L319

class-sv-wc-payment-gateway.php:319, WC_Gateway_Braintree_Credit_Card->__construct()
class-wc-gateway-braintree-credit-card.php:77, WC_Gateway_Braintree_Credit_Card->__construct()
class-sv-wc-payment-gateway-plugin.php:1136, WC_Braintree->get_gateway()
class-sv-wc-payment-gateway-plugin.php:1096, WC_Braintree->get_gateways()
class-sv-wc-payment-gateway-plugin.php:370, WC_Braintree->tokenization_enabled()
class-sv-wc-payment-gateway-plugin.php:354, WC_Braintree->maybe_init_my_payment_methods()
class-wp-hook.php:286, WP_Hook->apply_filters()
class-wp-hook.php:310, WP_Hook->do_action()
plugin.php:453, do_action()
wp-settings.php:450, require_once()
wp-config.php:163, require_once()
wp-load.php:37, require_once()
wp-blog-header.php:13, require()
index.php:17, {main}()

maybe_init_my_payment_methods() does not seem to be adequately restricted:

https://plugins.trac.www.ads-software.com/browser/woocommerce-gateway-paypal-powered-by-braintree/trunk/lib/skyverge/woocommerce/payment-gateway/class-sv-wc-payment-gateway-plugin.php#L347

if ( $this->supports_my_payment_methods() && $this->tokenization_enabled() && is_user_logged_in() ) has no checks towards any post types and this does not look strong enough.

PS I happened to also get in touch w/ SkyVerge about this today https://github.com/skyverge/wc-plugin-framework/issues/326

• This reply was modified 6 years, 4 months ago by lkraav.
• This reply was modified 6 years, 4 months ago by lkraav.

Thanks, looking forward to it.

I’m fairly certain I reported the same thing at https://github.com/10up/restricted-site-access/issues/53

We’re working on it.

Thanks, exactly what I needed to know.

Perhaps this info could be reflected in READMEs of your plugins?

They are still working on a responsive column system.

https://github.com/WordPress/gutenberg/issues/6048

> 1. The Classic Editor is core and Gutenberg is a plugin
> 2. Both the Classic Editor and Gutenberg are core
> 3. Gutenberg is core and the Classic Editor is a plugin

Unsurprisingly, that’s exactly what’s happening. Have you received some faulty information from somewhere?

WP5 is going launch at “stage 2” and will highly likely stay there for a leeeeeengthy while.

I was also wondering why this was necessary. There doesn’t seem to be any legit looking tech explanation given.