Finding an extension for which there is an update available is a bit of a problem. I installed one of my own and then used phpMyAdmin to change its version number in the manifest cache of the #__extensions table. I could then use that method to update from either the backend or cli as often as needed.

The patch appears to work as required. However, I have two other extensions installed that are not set up properly. In the backend I get explicit warning messages telling me which extensions are causing the problem. In the cli I get a text key string. Does this need fixing or is that a separate issue?

it can be fixed on the plugin adding the missed $language->load('lib_joomla', JPATH_ADMINISTRATOR);

$language->load('lib_joomla', JPATH_ADMINISTRATOR);

I needed to move this block of code to line 70 in UpdatefromcliCommand.php to get it to report which updates were triggering warnings.

            // Load com_installer's language
            $language = $this->getApplication()->getLanguage();
            $language->load('lib_joomla', JPATH_ADMINISTRATOR);
            $language->load('com_installer', JPATH_ADMINISTRATOR, 'en-GB', false, true);
            $language->load('com_installer', JPATH_ADMINISTRATOR, null, true);

yes i'll fix it in the plugin repo https://github.com/alikon/testcom/blob/main/src/plugins/console/updatefromcli/src/CliCommand/UpdatefromcliCommand.php when back from work

I have tested this item ✅ successfully on 4c49e07

Without patch i got an error message and the update was successful
With patch i got no error message and the update was successful

I have not tested this item.

I have not tested this item.

I have not tested this item.

I have tested this item ✅ successfully on 4c49e07

Without patch i got an error message and the update was successful.
With patch i got no error message and the update was successful.
Same result as @ThomasFinnern.

I have tested this item ✅ successfully on 4c49e07

Without patch i got an error message and the update was successful.
With patch i got no error message and the update was successful.
Same result as @ThomasFinnern.

Note that only the error message is gone but the update works correctly before and after the PR.

RTC

RTC

✅ Final test before merge with JBT

• Installed PLG_CONSOLE_UPDATEFROMCLI and zitat-service.de 2.0.2
• Seen module is updated to 2.0.3 by cli, but also red ERROR messages are printed
• Uninstalled module, applied PR with gh pr checkout 47203 and installed zitat-service.de 2.0.2 again
• Module is updated w/o red ERROR messages

Thank you very much @alikon for your contribution. Thanks to @ceford, @CSGoat0 and @ThomasFinnern for testing.