eclev91
Forum Replies Created
-
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
trunkand it looks like y’all don’t actually use trunk.Premium v1.8.6, which we have active, is still using
action-scheduler3.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 installruns 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
tagsdirectory. 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 18Forum: Plugins
In reply to: [Klaviyo] Behavior when customer updates email address?A customer’s WordPress and WooCommerce accounts are the same thing. But just to verify – nothing in the Klaviyo integration will update a subscriber if they update their email address in WordPress/WooCommerce?
Forum: Plugins
In reply to: [Event Tickets and Registration] PHP 8 deprecationsI appreciate that WP support for newer PHP versions is “beta”, but their usage of that term is not in line with industry usage and is sort of made up and in flux. In fact, one criteria is adoption of newer versions of PHP, and if third-party plugins are noisy on newer versions, developers are less likely to push clients to update to newer versions of PHP. This self-reinforcing cycle perpetuates “beta” support.
I would love to see these items cleaned up to create a more positive developer experience, regardless of the state of core WP.
Forum: Plugins
In reply to: [Easy Notification Bar] please tag releasesRollback in case of emergency, or installing from source with Composer via something like WPackagist.
Forum: Plugins
In reply to: [The Events Calendar] AJAX 403 error when accessing Previous or Next monthWe also ran into this issue on Kinsta. I’m not sure why a REST request for public content needs a nonce? I suppose it’s possible that a version of the page with a nonce got cached but any logged-in sessions should be completely avoiding the cache and not creating cached pages for unauthenticated users.
Forum: Plugins
In reply to: [Autocomplete WooCommerce Orders] Version 7.1.4?Noted and verified, thanks!
@livemesh are there still plans to fix this?
@jamesosborne I would like to follow up on this.
Obviously we can hide deprecation notices, but those of us working in dev environments are likely to keep error reporting on to catch anything we need to be aware of as we continue adapting to the latest versions of PHP, and deprecation notices cause a signal-to-noise ratio problem in dev environments. Further, some plugin developers are one-person teams who may not be formally testing newer versions of PHP, and bringing deprecations to their attention before they start actually breaking sites in newer PHP versions is good for the ecosystem as a whole.
Re: WordPress core support – the “beta” designation for WordPress core support will indefinitely exist for PHP 8.0 and greater given how the core team has defined their “beta” support – in that they’ve said that WordPress core is fully compatible, but they can’t vouch for plugins. So they’ve called it “beta” support. WordPress 6.2, in particular, resolved all outstanding PHP 8.1 deprecation notices in core with the update to Requests 2.0.
Would love to see deprecation notices resolved in this plugin, or at least the issue tracked in the GitHub issue tracker and not closed as “Complete” when it isn’t really.
I’ve seen it in a few places. One site, for example:
Deprecated: base64_encode(): Passing null to parameter #1 ($string) of type string is deprecated in /plugins/event-tickets/src/Tribe/Commerce/PayPal/Main.php on line 2335Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /plugins/the-events-calendar/common/src/Tribe/Repository.php on line 2129So this is an issue across the TEC suite. Though both of those scenarios look like they could be related to empty settings, so may not turn up on all sites depending on configuration.
WordPress: 6.2
TEC: 6.0.12
Event Tickets: 5.5.10
Theme: Divi / 4.20.4