In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

View Revisions: Issue #929		[ All Revisions ] [ Back to Issue ]
Summary	0000929: Ability to have Preferred Language for Front-end Users

Revision	2011-12-29 03:10:05 by alex
Additional Information	Plan: 1. add FrontLanguage column (before AdminLanguage column) into PortalUser table 2. in UserHelper::_processInterfaceLanguage / lang:OnChangeLanguage use: - FrontLanguage column instead of AdminLanguage column - PrimaryLang column instead of AdminInterfaceLang column - remove isAdmin check on top of the method of course when login is performed on Front-End 3. add FrontLanguage dropdown to user adding/editing page (admin), to my profile page in "advanced" theme (front-end) 4. add AdminLanguage dropdown to admin adding/editing page (admin) 5. make sure, that available interface languages in dropdown (when displayed on front-end only) only includes languages, that are allowed in current site domain 6. use FrontLanguage as language for Front-End Type e-mail events (if user_id is specified in kApplication::EmailEventUser) 7. use AdminLanguage as language for Admin Type e-mail events (if user_id is specified in kApplication::EmailEventAdmin) 8. make sure that e-mail event language override via "language_id" send parameter (see "_getSendLanguage" method) still works 9. placing all new e-mail event language detection logic inside that "_getSendLanguage" method would be the best choice

Revision	2011-12-29 03:09:54 by alex
Additional Information	Plan: 1. add FrontLanguage column (before AdminLanguage column) into PortalUser table 2. in UserHelper::_processInterfaceLanguage / lang:OnChangeLanguage use: - FrontLanguage column instead of AdminLanguage column - PrimaryLang column instead of AdminInterfaceLang column - remove isAdmin check on top of the method of course when login is performed on Front-End 3. add FrontLanguage dropdown to user adding/editing page (admin), to my profile page in "advanced" theme (front-end) 4. add AdminLanguage dropdown to admin adding/editing page (admin) 5. make sure, that available interface languages in dropdown (when displayed on front-end only) only includes languages, that are allowed in current site domain 6. use FrontLanguage as language for Front-End Type e-mail events (if user_id is specified in kApplication::EmailEventUser) 7. use AdminLanguage as language for Admin Type e-mail events (if user_id is specified in kApplication::EmailEventAdmin) 8. make sure that e-mail event language override via "language_id" send parameter (see "_getSendLanguage" method) still works 9. placing all new e-mail event language detection logic inside that "_getSendLanguage" method would be the best choise

Revision	2011-12-29 03:05:31 by alex
Additional Information	Plan: 1. add FrontLanguage column (before AdminLanguage column) into PortalUser table 2. in UserHelper::_processInterfaceLanguage / lang:OnChangeLanguage use: - FrontLanguage column instead of AdminLanguage column - PrimaryLang column instead of AdminInterfaceLang column - remove isAdmin check on top of the method of course when login is performed on Front-End 3. add FrontLanguage dropdown to user adding/editing page (admin), to my profile page in "advanced" theme (front-end) 4. add AdminLanguage dropdown to admin adding/editing page (admin) 5. make sure, that available interface languages in dropdown (when displayed on front-end only) only includes languages, that are allowed in current site domain

Revision	2011-12-28 23:52:55 by alex
Additional Information

Web Development by Intechnic

In-Portal Open Source CMS