eclev91
Forum Replies Created
-
I can’t speak to the wide variety of issues encountered by users here, but seeing a fix to dynamically declared properties would really be appreciated.
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$button_appearance_title is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$enable_paypal_credit is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$button_preview is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$connection_settings is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$pay_later_messaging_logo_type is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$pay_later_messaging_logo_position is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$pay_later_messaging_text_color is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] Can’t upgrade connection without logging outDeprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in .../wp-includes/functions.php on line 7300
Call Stack
# Time Memory Function Location
1 0.0010 408416 {main}( ) .../index.php:0
2 0.0012 445136 require_once( '...wp-admin/admin.php ) .../index.php:10
3 0.3560 37487320 require( '...wp-admin/menu.php ) .../admin.php:158
4 0.8579 40405536 require_once( '...wp-admin/includes/menu.php ) .../menu.php:412
5 0.8596 40444528 do_action( $hook_name = 'admin_menu', ...$arg = variadic('') ) .../menu.php:161
6 0.8596 40444744 WP_Hook->do_action( $args = [0 => ''] ) .../plugin.php:517
7 0.8596 40444744 WP_Hook->apply_filters( $value = '', $args = [0 => ''] ) .../class-wp-hook.php:348
8 0.8623 40567392 Tribe__Tickets__Commerce__PayPal__Orders__Report->register_orders_page( '' ) .../class-wp-hook.php:324
9 0.8623 40567640 add_submenu_page( $parent_slug = NULL, $page_title = 'PayPal Orders', $menu_title = 'PayPal Orders', $capability = 'edit_posts', $menu_slug = 'tpp-orders', $callback = [0 => class Tribe__Tickets__Commerce__PayPal__Orders__Report { public $orders_page = NULL; public $orders_table = NULL }, 1 => 'orders_page_inside'], $position = ??? ) .../Report.php:163
10 0.8623 40567640 plugin_basename( $file = NULL ) .../plugin.php:1478
11 0.8623 40567640 wp_normalize_path( $path = NULL ) .../plugin.php:769
12 0.8623 40567640 wp_is_stream( $path = NULL ) .../functions.php:2182
13 0.8623 40567640 strpos( $haystack = NULL, $needle = '://' ) .../functions.php:7300This is me copying and pasting the XDebug output. But I’ve linked the line in your source code that is problematic. Regardless of whether or not WordPress gracefully handles what comes next (see above – it does not), you’re calling
add_submenu_page
in an unexpected and unintended way.This can be traced back to a fatal error the plugin is throwing:
PHP Fatal error: Uncaught TypeError: implode(): Argument #1 ($array) must be of type array, string given in .../wp-content/plugins/events-block-for-the-events-calendar/includes/ebec-block.php:93
I run into a similar, perhaps related, issue every time I update the plugin. On my first page load or attempt to do something with WP-CLI, I get the same JSON feedback reported above:
{"success":false,"data":{"message":"You're not allowed to do this","from":"mailchimp-for-woocommerce"}}
This happens on a few different sites. Worth noting that “updating” the plugin is not being done via the WP interface or WP-CLI, but via Composer.
Forum: Plugins
In reply to: [WooCommerce] Coupon Usage Restriction email field broken in Safari@shameemreza Do you ask non-technical users to submit tickets on GitHub?
Seems like the minimal thing that the WP.org plugin support team for Woo could do is translate technical bugs over to the GitHub repo.
But now that I’ve debugged the issue that your support did not debug on a previous thread, I will also report it on the GitHub repo. I look forward to being asked to implement the fix as well.
- This reply was modified 4 months ago by eclev91.
Forum: Plugins
In reply to: [WooCommerce] Coupon Usage Restriction email field broken in SafariFWIW, the workarounds in the linked article are more complicated than they need to be. It has nothing to do with space or semi-colons. Just getting the browser to repaint the field will fix it. I went ahead and hooked into
admin_print_scripts
to get this working for us in the meantime:add_action('admin_print_scripts', function() {
?>
<script>
document.addEventListener('DOMContentLoaded', function() {
var emailInput = document.getElementById('customer_email');
if (emailInput && navigator.userAgent.indexOf('Safari') != -1 && navigator.userAgent.indexOf('Chrome') == -1) {
var emails = emailInput.value;
emailInput.value = emails;
}
});
</script>
<?php
});- This reply was modified 4 months, 4 weeks ago by eclev91.
I figured this out. Someone before me had set the global content area spacing to 0 in the Customizer, which is what the setting described above handles on a page-by-page basis.
Moving to unboxed removed the spacing I was concerned about.
Forum: Themes and Templates
In reply to: [Kadence] Support for group layout settingsPerfect, thank you so much!
Forum: Plugins
In reply to: [Coupons & Add to Cart by URL Links for WooCommerce] PHP deprecationI’ve installed 1.7.0 but this issue persists. Looking at the source code, I don’t see any class properties that were added to resolve this issue.
Forum: Plugins
In reply to: [Custom Adobe Fonts (Typekit)] Block editor supportFSE + block editor, yes. Right now, for instance, this plugin doesn’t make fonts available to your FSE theme, Spectra.
Hey folks, I’m using the premium version. I was mistaken about the lite version because I was looking in
trunk
and it looks like y’all don’t actually use trunk.Premium v1.8.6, which we have active, is still using
action-scheduler
3.4.2.Forum: Plugins
In reply to: [Easy Notification Bar] please tag releasesI wouldn’t get hung up on populating old ones at this point unless someone specifically needed them.
Our WP sites are managed with Composer, so plugins are all required at specific versions via a lockfile. If the source disappears, then future
composer install
runs fail because the code is no longer out there. We run updates about monthly, but in between those updates ,if we want to spin up a copy of the site without updating dependencies and this plugin has updated since then, it can’t install this plugin.Forum: Plugins
In reply to: [Easy Notification Bar] please tag releasesFollowing up on this @wpexplorer – it looks like you’re only tagging the latest release. This breaks any install operations from source locked to an older version.
Ideally old releases would continue to be in the
tags
directory. It’s possible that this is just a side-effect of starting to tag releases though. I can’t see the dates of the latest releases and can’t say for sure.Forum: Plugins
In reply to: [Event Tickets and Registration] PHP 8 deprecationsIt does look like that resolved many PHP 8 deprecations. We have since moved toward using 8.2 on our sites, since 8.0 is officially EOL while 8.1 is now security updates only with 11 months until EOL.
On 8.2, there are still outstanding deprecations. But I appreciate your continued attention to the codebase and keeping it updated!
Deprecated: Creation of dynamic property Tribe__Tickets__Main::$plugin_slug is deprecated in /plugins/event-tickets/src/Tribe/Main.php on line 146 Deprecated: Creation of dynamic property Tribe__Tickets__Main::$registered is deprecated in /plugins/event-tickets/src/Tribe/Main.php on line 452 Deprecated: Creation of dynamic property Tribe__Tickets__Tickets_Handler::$path is deprecated in /plugins/event-tickets/src/Tribe/Tickets_Handler.php on line 108 Deprecated: Creation of dynamic property Tribe__Tickets__REST__V1__Messages::$messages is deprecated in /plugins/event-tickets/src/Tribe/REST/V1/Messages.php on line 18