Fix PHP warnings when clone field encounters invalid field entries#286
Fix PHP warnings when clone field encounters invalid field entries#286cbravobernal merged 2 commits intotrunkfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #286 +/- ##
============================================
+ Coverage 12.09% 12.21% +0.12%
- Complexity 4285 4287 +2
============================================
Files 284 284
Lines 34692 34693 +1
============================================
+ Hits 4195 4239 +44
+ Misses 30497 30454 -43
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
2 participants
What
Fix PHP warnings in the Clone field when the field array contains null or invalid entries.
Reported in the forum: https://wordpress.org/support/topic/php-warnings-207/
Why
Users migrating from ACF to SCF, which includes PRO functionality, can encounter PHP warnings they didn't have before
How
acf_get_fields()methodTesting Instructions
vendor/bin/phpunit --filter Test_ACF_Field_Clone