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
Testing Pods 3.0.3 with PHP 8.1 and WP 6.3; adding a post with a custom wysiwyg field, I get this deprecation warning.
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/removed/wp-content/plugins/pods/classes/fields/wysiwyg.php on line 241
The WYSIWYG field is using the TinyMCE editor and Trim extra whitespace before/after contents option; that might be relevant for the warning (screenshot below)
Version
3.0.3
Testing Instructions
No response
Screenshots / Screencast
Screenshot of deprecation warning:
Screenshot of field settings:
Possible Workaround
It's a deprecation warning, so turning WP_DEBUG off turns off the warning.
Site Health Information
Please reach out to me if that applies.
Pods Package
Please notify me if that applies.
The text was updated successfully, but these errors were encountered:
Description
Testing Pods 3.0.3 with PHP 8.1 and WP 6.3; adding a post with a custom wysiwyg field, I get this deprecation warning.
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/removed/wp-content/plugins/pods/classes/fields/wysiwyg.php on line 241
The WYSIWYG field is using the TinyMCE editor and Trim extra whitespace before/after contents option; that might be relevant for the warning (screenshot below)
Version
3.0.3
Testing Instructions
No response
Screenshots / Screencast
Screenshot of deprecation warning:
Screenshot of field settings:
![image](https://private-user-images.githubusercontent.com/17141205/270158320-f352b207-49f0-4d3d-aa93-f42d3d101969.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEwNTQ4NTMsIm5iZiI6MTcyMTA1NDU1MywicGF0aCI6Ii8xNzE0MTIwNS8yNzAxNTgzMjAtZjM1MmIyMDctNDlmMC00ZDNkLWFhOTMtZjQyZDNkMTAxOTY5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE1VDE0NDIzM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWVlNzRhZjRhNWI4NzQxODFkNTA5NWIwMWU1MTU0NDJiNmJjOTc2NmZjNTZlYzI2NjQ4ZTJhNzJlOTFhOGY0NjImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.etZt1H4L25rCMvUDwep5nMB2Yk-hEN-FIt6pndglfGo)
Possible Workaround
It's a deprecation warning, so turning WP_DEBUG off turns off the warning.
Site Health Information
Pods Package
Please notify me if that applies.
The text was updated successfully, but these errors were encountered: