Conversation
supportI was wondering if your plugin supports PHP 8.0? I updated and when I edit a plugin which uses typography fields I get a WP Critical error
@eoinsprint I never tried with PHP 8.0? Could you share the error you received?
Hi, thanks for getting back. I am not sure what I can share other than the message “There Has Been a Critical Error on Your Website” when I try to update any of my settings in my other plugin that uses ACF Typography Field I’d love to give more info, please let me know anything I can do to help you find this issue here. Kind regards
Hi there, Can I get an update on this? Thanks!
I’ve tested this plugin with PHP 8.0, 8.1, and 8.2 Using a fresh install WP 6.0.2 site with only ACF Pro 5.12.3, ACF Tyopography 3.2.3, and DebugPress 2.0, and adding a Field Group with ALL ACF Typography Fields on the default “Post” post type and creating/editing test post entries – these are the results I get: – 8.0 – no errors at all (previously got a ton WP Core errors but they have since been patched) – 8.1 – These errors appear site-wide front-end and back-end, with multiple occurrences of each. setcookie(): Passing null to parameter #5 ($domain) of type string is deprecated ( /wp-includes/option.php ) rtrim(): Passing null to parameter #1 ($string) of type string is deprecated ( /wp-includes/formatting.php ) This error only occurs on the front-end when viewing a created post. wp-includes/functions.php is deprecated since version 3.0.0. – 8.2 – same as 8.1 – Results – ZERO fatal errors, like you’re describing. The 3 repeating errors are only deprecated messages (not errors), and remain even with ACF Pro and ACF Typography disabled. – Conclusion – ACF Typography is working fine with PHP 8.0, 8.1, & 8.2 If there’s something specific you’re trying to do when you encounter fatal errors, let me know and I’ll try it on my test site. There’s likely a conflicting plugin of some sort, but it doesn’t appear to be ACF Typography. This reply was modified 3 years, 7 months ago by codejp3 . This reply was modified 3 years, 7 months ago by codejp3 . Reason: spacing for easier reading
Thank you @codejp3 for your detailed testing. Appreciate it.
@eoinsprint I never tried with PHP 8.0? Could you share the error you received?
Hi, thanks for getting back. I am not sure what I can share other than the message “There Has Been a Critical Error on Your Website” when I try to update any of my settings in my other plugin that uses ACF Typography Field I’d love to give more info, please let me know anything I can do to help you find this issue here. Kind regards
Hi there, Can I get an update on this? Thanks!
I’ve tested this plugin with PHP 8.0, 8.1, and 8.2 Using a fresh install WP 6.0.2 site with only ACF Pro 5.12.3, ACF Tyopography 3.2.3, and DebugPress 2.0, and adding a Field Group with ALL ACF Typography Fields on the default “Post” post type and creating/editing test post entries – these are the results I get: – 8.0 – no errors at all (previously got a ton WP Core errors but they have since been patched) – 8.1 – These errors appear site-wide front-end and back-end, with multiple occurrences of each. setcookie(): Passing null to parameter #5 ($domain) of type string is deprecated ( /wp-includes/option.php ) rtrim(): Passing null to parameter #1 ($string) of type string is deprecated ( /wp-includes/formatting.php ) This error only occurs on the front-end when viewing a created post. wp-includes/functions.php is deprecated since version 3.0.0. – 8.2 – same as 8.1 – Results – ZERO fatal errors, like you’re describing. The 3 repeating errors are only deprecated messages (not errors), and remain even with ACF Pro and ACF Typography disabled. – Conclusion – ACF Typography is working fine with PHP 8.0, 8.1, & 8.2 If there’s something specific you’re trying to do when you encounter fatal errors, let me know and I’ll try it on my test site. There’s likely a conflicting plugin of some sort, but it doesn’t appear to be ACF Typography. This reply was modified 3 years, 7 months ago by codejp3 . This reply was modified 3 years, 7 months ago by codejp3 . Reason: spacing for easier reading
Thank you @codejp3 for your detailed testing. Appreciate it.