Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.2.0
-
Fix Version/s: 4.1.0-b1
-
Component/s: Client Interface
-
Labels:None
Description
Currently only the companies default language is displayed throughout non-authenticated client pages. If multiple languages are available for the company, display a language selector on non-authenticated client pages.
More details to follow in terms of design/mockups.
NEW
After thinking about this and reviewing the comments, the language selector should appear in the upper right of the client area and be visible on all pages. This will either be in the upper-right most of the page, or within the navigation bar to the right on either side of the Login link. My preference is in the upper right above the navigation bar. Need to be sure that it doesn't interfere with the "Return to Staff Portal" link, or move that link.
This should appear as a link with a menu, similar to bootstrap's drop down menu, and not a dropdown form.
The selector should only appear if there is more than 1 language installed. By default, it would not appear because Blesta only ships with en_us.
OLD
Use the current footer markup if the language selector is not displayed, otherwise use the following markup:
<div class="row footer">
<hr>
<div class="col-md-10 col-sm-9 col-xs-8">
<p>Powered by <a href="http://www.blesta.com/">Blesta</a>, © Phillips Data, Inc.</p>
</div>
<div class="col-md-2 col-sm-3 col-xs-4 pull-right">
<form>
<select class="form-control">
<option>English, USA</option>
<option>English, UK</option>
</select>
</form>
</div>
</div>
NOTE! The <hr> tag is moved up, directly below the row footer. This change can be made in both cases. If the language selector exists, then we have 2 divs, and the "Powered by" paragraph is no longer centered. It looks better aligned left when there is a drop down aligned right.
This drop down only applies to non-authenticated client pages
Issue Links
- blocks
-
CORE-2254
Override pagination language
-
- Closed
-
Activity
Seems like the selector would need to be in the admin interface too, otherwise they will see the language they chose in the client UI when they go back to the staff portal.
Tyson Phillips (Inactive)
added a comment - Seems like the selector would need to be in the admin interface too, otherwise they will see the language they chose in the client UI when they go back to the staff portal. Perhaps the option should not be displayed to staff who are "logged in as" a client if that is the case. I do not want this feature to have any impact on the staff interface.
Paul Phillips
added a comment - Perhaps the option should not be displayed to staff who are "logged in as" a client if that is the case. I do not want this feature to have any impact on the staff interface. Doesn't that behavior contradict the point of staff logging in to to the client UI to see what they see? I imagine staff may also want to test that clients see the language selector, or could tell them it's there if they were on the phone with them or something. It usually makes sense for UI changes like this to be consistent.
Tyson Phillips (Inactive)
added a comment - Doesn't that behavior contradict the point of staff logging in to to the client UI to see what they see? I imagine staff may also want to test that clients see the language selector, or could tell them it's there if they were on the phone with them or something. It usually makes sense for UI changes like this to be consistent. It's not a big concern that the language selector not appear when staff are "logged in as" a client, but I do agree that consistency across the client interface is ideal. However, I do not want to add any such selector to the staff interface If Staff change the language within the client area, it should be ephemeral, not saved for the client language, and not impacting the admin's language within the staff area.
Paul Phillips
added a comment - It's not a big concern that the language selector not appear when staff are "logged in as" a client, but I do agree that consistency across the client interface is ideal. However, I do not want to add any such selector to the staff interface If Staff change the language within the client area, it should be ephemeral, not saved for the client language, and not impacting the admin's language within the staff area. Markup Attached
There will need to be 2 new Client Theme colors: Top Navigation Text Color, and Top Navigation Text Active Color, whose placement is indicated in the CSS attached. I still need to come up with default colors for the FOUR client theme, and other themes.
Paul Phillips
added a comment - Markup Attached
There will need to be 2 new Client Theme colors: Top Navigation Text Color, and Top Navigation Text Active Color, whose placement is indicated in the CSS attached. I still need to come up with default colors for the FOUR client theme, and other themes. 
Why not just add this to the footer for the core so it can be available everywhere? Otherwise we'll find ourselves receiving requests for it to be on the Support Manager, and every other public facing plugin.