You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a test site, when updating to PHP 8.1, and with WP_DEBUN on, I get these deprecation warnings: Deprecated: substr(): Passing null to parameter #1 ($string) of type string is deprecated in /home/removed/wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 174
and
Deprecated : strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /home/removed/wp-content/plugins/pods/classes/Pods.php on line 741
Is that something you can reproduce?
I'm using Pods Templates with MagicTags™. Please tell me, if I should put some effort into pinpointing exactly what query triggers the warning.
Version
3.0.1
Testing Instructions
No response
Screenshots / Screencast
No response
Possible Workaround
Downgrading to PHP 8.0 gets rid of the warnings.
Site Health Information
No response
Pods Package
No response
The text was updated successfully, but these errors were encountered:
Description
On a test site, when updating to PHP 8.1, and with WP_DEBUN on, I get these deprecation warnings:
Deprecated: substr(): Passing null to parameter #1 ($string) of type string is deprecated in /home/removed/wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 174
and
Deprecated : strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /home/removed/wp-content/plugins/pods/classes/Pods.php on line 741
Is that something you can reproduce?
I'm using Pods Templates with MagicTags™. Please tell me, if I should put some effort into pinpointing exactly what query triggers the warning.
Version
3.0.1
Testing Instructions
No response
Screenshots / Screencast
No response
Possible Workaround
Downgrading to PHP 8.0 gets rid of the warnings.
Site Health Information
No response
Pods Package
No response
The text was updated successfully, but these errors were encountered: