Hi Josh,

You will need to modify the below string in file 'JOOMLA/administrator/language/en-GB/en-GB.plg_app_user_article.ini'

APP_ARTICLE_USER_TITLE="Articles"

Hope this help and have a nice day!

I appreciate you finding out exactly where to change the name, but I have to ask why a mod in this case? In ES 1.2.10 and before the title of the app controlled the display of the text which was great. Now the title doesn't "do anything". It's not that I don't mind doing extra work, but we ought to think of this situation for all the folks who use EasySocial. Just trying to make sure the best practices are used.

Hi Josh,

The reason for using the language string is so that when displaying the app title in profile page, the title can be different from the dashboard page, the app stream title

Hope this help and have a nice day

It appears that both the dashboard and the profile app have exactly the same name (articles). So even in the scenario of having string manipulation so that one can be different from the other, we should have at least one of them be respected from the app title. Otherwise what is the point of allowing the admin to change the article app name if it doesn't do anything?

Now if we want a easy method for allowing admins to decide between app filter names and profile app names, why not have another text field for "App Filter Name"? (option appears when editing an app) This way the admin could easily specify what it says on the profile and in the dashboard. That's a win win situation. Modding strings has it's place, but if we expect app filter names to be changed often and expect clean separation from the app name, this is the easiest way to pull this off.

I thought about this a little more and came up with a better name for the field, "Filter Name". Here is a screen shot showing where I propose it be placed:



By adding a filter name, we can have the app title be respected on the profile and have clear separation on the dashboard. This would make it so on the profile I could have it say "My Pages" while on the dashboard it could say "Articles" or "Content".

Also note that the current method is inconsistent. If I open up my profile, you will see the forums app match up with it's permalink. But Articles does not. People shouldn't have to mod their files to change a title. The rest of the app titles seem to change just fine.

hey josh,
in fact it's actually the best solution to handle such language actions inside the respective language files, otherwise when it comes to multi-language sites it looks very unprofessional. just taking your example where you want to name it "content", if you stick to that and have 2 more languages next to english your users would always see that "content" title even if it's of course wrong (meaning it's not in their language) for them. having this controlled by the language files they can see the fitting title in their language which leads to a much better result.

After testing out how language packs work with ES, I realized that you have a very strong point. I wasn't quite sure how it translated before (if at all) for the app title.

Fortunately I have a cool idea of how to solve this issue.

The idea is to have three names instead of two, one being an "App Name", "App Title", and "App Permalink". The App Name never changes no matter what so that the language string could translate it accordingly (just like it does right now). The app title by default could be blank until filled in by the user. This would allow for a quick over ride of the title for that particular app. So if I spoke Spanish I could quickly put in a title I prefer, same goes for English. Finally for the permalink, it would be exactly the same as it is now.

Here is what it could look like by default (notice the title is not filled out but is still obvious what it is):



Benefits:

• Users could easily change the title of an app without needing to use a language over ride and digging around for the language constant.
  


• People who speak other languages could easily change the app title to better fit their vocabulary.
  


• This method would not negatively effect sites that use multi-language.
  


• This method uses already existing methods but re-arranges how they are used to make for an easier to make social site.
  

How to Implement This:

To have an app name it should be stored in the _social_apps table. You would either need a new column called "name" or store the value in the params. What it would store is the name of the app that the user can search for when looking for an app. So for example for Kunena it would store in the name column "Forums". This allows for a blank app title to be searchable in the backend as well as display in the app list.

What it looks like inside the database with this method:



What it looks like when a admin searches the app (looks the same as before):



Then have the app title set to blank by default (upon installation of a fresh version of EasySocial) as well as non required. The value that gets placed into here over rides the language constant (like it did in earlier versions of ES 1.2).

Keep the permalink as it is.

Why this Method?

I chose this method because we want smooth translations, easy changes, consistent practices, and simplicity for implementing these changes. The second half of this proposal already existed until recently. The "hardest part" I suppose is copying the values from the title column (from a fresh installation) and porting them into the name column (after the name column is created).