-
-
Notifications
You must be signed in to change notification settings - Fork 6
Version 6 Migration
Mat Lipe edited this page Apr 17, 2026
·
14 revisions
Version 6 is a major release with many breaking changes. This guide to show you how to migrate your project from version 5 to version 6.
It is strongly recommended to use PHPStan to detect type inconsistencies as version 5 introduces a large number of strict types.
The majority of changes have called out using _deprecated functions and phpdocs in version 5.10.0 of the library. It is recommended to follow this procedure before updating to version 6.
- Update to version 5.10.*
- Enable
WP_DEBUG. - Return
trueon thedeprecated_class_trigger_errorfilter (if applicable). - Run through your normal unit/regression testing and follow any prompts from the
_deprecatedsystem.
6.6.0 is now the minimum support version of WordPress core.
PHP 8.4 is now the minimum supported version. This was done to support async visibility in class properties and therefore cleanup a lot of associative array spaghetti.
- All properties have been made protected in favor of using the methods with the same name as the properties.
- Some of the
Registeredbarely used methods have been removed. Unlikely to affect you. -
Default_Callbackclass has been moved toField\Default_Callback -
Field_Typeclass has been moved toField\Field_Type. -
Event_Callbacksclass has been moved toField\Event_Callbacks. -
BoxTypetrait has been moved toBox\BoxType. -
Displaytrait has been moved toField\Display. - All
callablehave been changed to\Closure. migrate existing usage via first class callable.
- All deprecated Handle class constants have been removed.
- The
Resources::unpkg_integritymethod has been removed. - The
Resources::use_cdn_for_resourcesmethod has been removed. -
ResourceHandlesinterface now requires aget_manifestmethod.
-
\Lipe\Lib\Post_Type\Custom_Post_Typeis now\Lipe\Lib\Post_Type\Post_Type -
\Lipe\Lib\Post_Type\Custom_Post_Type\Register_Post_Typeis now\Lipe\Lib\Post_Type\Register_Post_Type