knubew
Forum Replies Created
-
Currently Woody Snippets only supports up to PHP 7.4, but PHP 7.4 has reached the End Of Live (EOL) already on 28-NOV-2022. Even for PHP 8.0 there will no longer be any security patches from November 26th, 2023 (25 days from today!).
It would be really great if you could let us users know whether you plan to support at least PHP 8.1 (or better 8.2) in the near future or not?
Thank you in advance for the information.
Thank you very much, but read https://github.com/pods-framework/pods/issues/7089 please. It’s related to an old error https://github.com/pods-framework/pods/issues/6971
>> The plugin does not yet support PHP 8.2.
Many thanks for your response. But then it would be better if the plugin description didn’t say “Supports PHP 7.0 or higher”, right?! – For example “Supports PHP up to 7.4.x” I think would be more appropriate.
And by the way:
PHP 7.4.x has reached EOL on 28-NOV-2022.- This reply was modified 1 year, 9 months ago by knubew.
Forum: Plugins
In reply to: [W3 Total Cache] Tons of “PHP Deprecated” messages in error_log under PHP 8.2Thank you.
F.y.i. I just found another one:
PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in .../wp-content/plugins/pods/classes/PodsField.php on line 907;Resolved in Pods 2.9.14 (to be released this week)
That’s great. Thank you very much.
Hello,
I can well imagine that the use of “strlen” in the entire pods code could possibly be checked, because there are so many error messages under PHP 8.x – or what do you think?
The patch works. The error message no longer occurs. Thanks very much.
However, I encountered some other error messages in the error_log file involving pods. I’ll list them here now (with shortened paths):
PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in .../wp-content/plugins/pods/includes/general.php on line 1408;PHP message: PHP Deprecated: strlen(): Passing null to par
ameter #1 ($string) of type string is deprecated in .../wp-content/plugins/pods/includes/general.php on line 1577;Got error '.../wp-content/plugins/pods/includes/general.php on line 1577; PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in …/wp-content/plugins/pods/includes/general.php on line 1585;PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in .../wp-content/plugins/pods/includes/general.php on line 1589;PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in .../wp-content/plugins/pods/includes/general.php on line 1592;Thank you very much for the patch. I will test it and then report to you.
Done ??
Sorry, it turned out that the error was in the plugin I was using and not in W3TC. The plugin author has now fixed the error. Nevertheless, many thanks for your quick support response.
I just installed the new version 3.1.8. Saving settings seems to be working again. I’ll keep watching it anyway. ??
Did you try clearing your W3 cache?
Yes. I also tried it with a disabled W3 cache plugin.
Can you submit support ticket/submission on my site to discuss this further?
Done.
I’ve updated from v3.1.5 to v3.1.7 and strange things happened.
- After the update I tried to disable the Legacy News Ticker and got an error message (see screenshot: https://imgur.com/hp25qep). The setting could not be saved.
By the way: I was missing the: (“Legacy”) - Then I disabled my “W3 Total Cache” plugin but no change. The setting could not be saved.
- Then I tried to debug the error and used in the file “config.php”…
define('WP_DEBUG', true); define('WP_DEBUG_DISPLAY', false); define('WP_DEBUG_LOG', true);- Then I tried to save the setting again and it seemed that the setting was saved because no error message was displayed anymore (see screenshot: https://imgur.com/jCX5fH8).
- After disbling the debug mode in config.php and refreshing the site I saw, that the new setting was NOT saved (see screenshot: https://imgur.com/BQOkCJH) and neither “Activated” nor “Disabled” had any value.
- This reply was modified 1 year, 11 months ago by knubew.
Are you still seeing this issue with the latest version of Ditty (v3.1.5)?
Yes. This morning the Legacy News Ticker was activated again (see screenshot please).
https://imgur.com/a/v4y3n4gDo the rest of your settings stay updated on the Settings page when you modify them?
Yes, at least I haven’t noticed any other errors so far.
In regards to your legacy CSS, if the legacy News Ticker is disabled you can leave this be. But, if the legacy toggle isn’t saving for you and you don’t need that CSS anymore, then yes, you might as well delete it and save the legacy settings.
Okay, thx for this info.