User tests: Successful: Unsuccessful:
Proposing the fixing of the long term typo of cachable
to be fixed in the new major series of Joomla 4
It shouldn't be a b/c break as its just a variable name but @HLeithner says
Only thing to consider is that this method is abstracted by 3rd party developer and we should check this before we make a b/c break. I don't know if we have property/option arrays with cachable in the code base.
TEST EVERYTHING ;-)
EVERYTHING Works
EVERYTHING Works
Maybe a note in the https://docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_4 ?
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_banners com_categories com_checkin com_config com_contact com_content com_cpanel com_csp com_fields com_finder com_installer com_joomlaupdate com_languages com_login com_menus com_messages com_modules com_newsfeeds com_plugins com_redirect com_tags com_templates com_users com_workflow Front End |
Labels |
Added:
?
|
There are 107 instances in php files before applying the pr and 39 after. As this is a variable name it seems to me it may as well be all or nothing. Only where it occurs as $cachable.
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-11-18 13:08:55 |
Closed_By | ⇒ | PhilETaylor |
After apply the patch on this file remains
cachable
:I think the branch must be updated because you fix it