Austin
Forum Replies Created
-
Also tracking here: https://github.com/sailthru/sailthru-wordpress-plugin/issues/108
Came to say 2.0.7 did not resolve the deprecation notice in PHP 8.2.
See: https://php.watch/versions/8.2/partially-supported-callable-deprecation for more information on self callables.
It looks like you updated a method callback which was not the issue (https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3023346%40cdn-enabler&old=3010495%40cdn-enabler&sfp_email=&sfph_mail=).
You’ll need to change the
CDN_Enabler_Engine::start()
method to not instantiateself()
. (https://php.watch/versions/8.2/partially-supported-callable-deprecation)- This reply was modified 2 months, 1 week ago by Austin.
Forum: Plugins
In reply to: [Custom Login] Custom Login v4.1 Vulnerable ?Unfortunately that is how WordPress’ plugin update system works.
Forum: Plugins
In reply to: [Custom Login] Custom Login v4.1 Vulnerable ?Version(s) 4.0.12 & 4.1.1 have been pushed to the repo.
Forum: Plugins
In reply to: [Custom Login] Custom Login v4.1 Vulnerable ?I am unaware of a vulnerability. That page doesn’t have any information on what is vulnerable, nor has any service reached out about one.
Forum: Plugins
In reply to: [Custom Login] Problems with Matomo PluginThere is not much I can do since Matomo is supporting PHP DI v6 which is using a PHP 7 Container interface. I imagine once they update to DI v7 and psr/container v2 this issue will be resolved.
I have chosen not to support PHP <= 8.0 in Custom Login.
Forum: Plugins
In reply to: [Custom Login] incompatible php when updatingUnsure how WordPress allowed the update to 4.1.0, unless you manually updated. But since PHP 7.3 has been end-of-life since Jan of ’22 I would suggest you reach out to your host to upgrade.
PHP 8.0 reached end-of-life this month, and I have no plan to support anything less than 8.0.
If you need it to work, I suggest rolling back to 4.0.11.
Version 4.0.11 has been push up.
I see, looks like the package I was using won’t get updates for PHP 8.1+ support. I’ll get a fix in.
What PHP version are you running?
Forum: Plugins
In reply to: [REST API Toolbox] PHP Fatal error: Uncaught Error: Call to undefined methodYeah, it’s for sure strange. I am unsure how to replicate it as well.
Not sure why the code is allowing WP_Error to continue as the new response object…
Forum: Plugins
In reply to: [REST API Toolbox] PHP Fatal error: Uncaught Error: Call to undefined methodI haven’t been able to replicate it locally on my local box, but I am able to in my stage and prod servers.
So far the only setting I have enabled is “Require Authentication for Users”. As soon as that box is checked any REST response fails with he error mentioned above.
Right now the only difference between my local box and host apps free/pro Redis plugin; I am using Redis Cache on local, and Object Cache Pro in stage/prod (if this makes a difference).
I will try to get the pro plugin installed to verifyStill works locally with the PRO version.- This reply was modified 9 months ago by Austin.
Forum: Plugins
In reply to: [Custom Login] Fatal Error v4.0.8This will likely be the last PHP 7.4 release, as I no longer working with PHP less than 8.0.
Forum: Plugins
In reply to: [Custom Login] Fatal Error v4.0.8@wpdev2022 I didn’t say it was resolved for PHP 8.0+, rather in an upstream package the underlying issue was resolved but required PHP >= 8.0. So I was unable to update Custom Login with the dependency.
Regardless, I have back ported the fix and pushed Custom Login 4.0.9.
This will likely be the last PHP 7.4 release, as I no longer with with PHP less than 8.0.
- This reply was modified 1 year ago by Austin.
Forum: Plugins
In reply to: [Custom Login] Fatal Error v4.0.8I have a fix in place already, but it needs to be back ported for PHP < 8.0 support which I haven’t had the time to execute yet. I am hoping I can in the next week or two.