User tests: Successful: Unsuccessful:
Pull Request for Issue #39829.
Added missing "items" text to the Joomla update view.
After the patch is applied you have to update your Joomla without reverting the code change of the patch!
Maybe there is an easier/better approach to do but you could follow these steps:
In the third column only the number of extracted/processed items is visualized:
In the third column the number of extracted/processed items is visualized with an additional text "items":
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Category | ⇒ | Administration com_joomlaupdate Language & Strings JavaScript Repository NPM Change |
Status | New | ⇒ | Pending |
Title |
|
Labels |
Added:
Language Change
NPM Resource Changed
PR-5.0-dev
|
I have tested this item
I have tested this item
See comment
a folder is just a special kind of file,
Also plausible reasoning to consider files as a collective name of files and folders. It keeps the text short.
2 ways:
Using "Files" for Folders and Files maybe not completely wrong but I think we could use a more common wording.
2 ways:
- Call it "Objects" or "Entries"
- Only show files as counter.
items
choose whatever
we are postponed the problem to the translators
It's not content in English
And content is not countable.
When I unzip a .zip file in MS Windows, the progress dialog shows "items" (English) and, for example, "Elements" in German. I think we can reuse this phrase, some of you have already suggested it. And for other languages we would have a template.
When I unzip a .zip file in MS Windows, the progress dialog shows "items" (English) and, for example, "Elements" in German. I think we can reuse this phrase, some of you have already suggested it. And for other languages we would have a template.
so you have your answer please use items, then this can be merged.
thanks
I have tested this item
Title |
|
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-06-10 14:46:23 |
Closed_By | ⇒ | HLeithner | |
Labels |
Added:
?
|
thanks
@beni71 There is not really the need to build your own package for testing. Our automated ci tool drone already does that for every pull request. When you use the „show all checks“ at the bottom of the pull request on GitHub, the ci checks are shown, among of them is a „Download“ step. Follow that link and you come to a page where you can find a custom update url and links to installation and update packages which contain the fix from this pull request.