Update en-GB.com_installer.ini#8459
Update en-GB.com_installer.ini#8459roland-d merged 1 commit intojoomla:stagingfrom brianteeman:walloftext2
Conversation
|
I have tested this item ✅ successfully on 4ec62b6 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8459. |
|
RTC as it is a language change. Let the PLT decide to go with it. Thanks. This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8459. |
|
Disagree. But I guess this was expected. |
|
Do we have walls of text for every function in joomla? No. As I quoted the more text you have the less likely someone will read it.
|
|
If you remove all information then reading is not needed at all, if you like to have it short then change it to "Discover extensions that have been uploaded with (S)FTP and install them here." so it is clear what this is for. |
|
Except that isnt technically correct. On 20 November 2015 at 09:51, Robert Deutz notifications@github.com wrote:
Brian Teeman |
|
Whilst I agree that less text is better I'm not convinced the new text actually gives enough information so that people can understand what it actually does. |
|
Agree with Brian. The only other function I found so far is System->Clear Expired Cache. All other functionality in the back-end doesn't tell you what to do! Suggest to use: "Use Discover from the tool bar to find extensions that are not properly registered. Use Install from the tool bar to register them." to instruct the administrator on using this function. As with any of the other functions you need to use Help from the tool bar when you don't know how to use something. That Help provides information that goes further than instructions on what to do (most of the time). |
A newbie would not understand that at all. "register" is dev talk. |
|
Maybe a newbie doesn't understand. A Super user should! And again if he doesn't he should go for the Help. Prefer to have this consistent with the rest of the UI. As mentioned nowhere else this is done. Rather than these tips, proper instructions on what to do are needed. That even includes this case: In addition there is much more functionality missing to correct mistakes in an environment. Not being able to correct these mistakes makes managing a website much more complicated than necessary. Specially for newbies. Providing the missing functionality will help, but improving the quality of the product so users won't run into these situations is much more preferred. Looking at the functionality of Discover, consider it something for a specialist. It would be available to an administrator instead of Super user otherwise! The fact this functionality is needed might explain the downfall, not the fact it is provided (even when it is only half of the functionality needed). |
|
I agree that the current phrase is too long. But I think there is a balance to be found between Brian's proposition and something that works for new users |
|
Perhaps we should have a manual ;) I like the new text. |
|
That is the proposed text: Discover extensions that have not gone through the normal installation process. I don’t like that it is only explaining what it is not instead of explaining what it is and you need to know what is the "normal installation process". If we are going with that proposal we can remove that sentence entirely because it doesn’t help. I 100% agree that we need to avoid to have „walls of text“ but this doesn’t mean that we replace it with „short non have a useful meaning at all sentences“. I think we need more short hints for parts of the CMS. We should not forget that at some point someone installs Joomla! and is just clicking through the interface to look what it is. Some parts don’t need a big explanation what it is. E.g. article manager, it is for managing articles, no need for saying this on the page. Beside the question, if we should change the sentence I would say the bigger questions is what amount of information are we are going to give within the backend. If we say no specific explanation then we can remove it completely, if we say yes then we need to add information also at other places. |
|
Agree with the fact the proposed text by Brian is too abstract. Which is why I suggested concrete instructions on what to do. Similar to what is done at System->Clear expired cache. As mentioned that is the only function I found that provides instructions. Consider those instructions relevant because the user needs to do them first to be able to do something with the results. These are examples of the very few functions that require an action by the user first. In general functions provide information the user can manipulate providing a tool bar with actions to perform on the shown information. Considering these functions are targeted at the Super user I consider it fair to say he should know what to do. Even newbies that don't know should go for the Help on the tool bar. So, the instructions I provided tell you what you already should know. This function allows you to repair a situation where something went wrong ( only half, missing options to remove discovered extensions! ). Guess that someone trying to repair an environment should know what he is doing. So, wouldn't mind removing the obvious instructions. Take it that surprised users about the lack of information would go for the Help button, provided for this reason! |
|
Moving back to Pending. A bit too much contention to be RTC. This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8459. |
|
@joomla-cms-bot please follow @pjwiseman 's descision he is allowed to do this 😄 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8459. |
|
I have tested this item ✅ successfully on 4ec62b6 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8459. |
|
Setting to RTC. This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8459. |

Remove extra text. It really isn't necessary to have a wall of text explaining all the possible uses of Discover.