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
Step 1 - Manage in php code the both field fk_status and status and set old one as deprecated. So existing modules are compatible and can be updated using the new field name being also compatible.
Step 2 - when we are sure that step 1 us completed (we can use ->oldname and ->newname in code, for both create,update and read, with the same result), then in a next version n+x, we update field in databse with the new name and update sql requests in core code.
Proposal step to follow by @eldy in (#27929)
Step 1 - Manage in php code the both field fk_status and status and set old one as deprecated. So existing modules are compatible and can be updated using the new field name being also compatible.
FIX #26920 replace fk_statut by status #27930
Step 2 - when we are sure that step 1 us completed (we can use ->oldname and ->newname in code, for both create,update and read, with the same result), then in a next version n+x, we update field in databse with the new name and update sql requests in core code.
FIX #26920 use status instead of fk_statut #27929
Step 3 - Then in a next version n+y, we remove the duplicated code related to fk_status.
Old proposal by @lmag and FHenry
*/
public $fk_statut; )
The text was updated successfully, but these errors were encountered: