Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in SugarFeed: Module name in newsfeed lower case even if localised module name is upper case #2506

Closed
rholighaus opened this issue Oct 28, 2016 · 2 comments
Labels
Status:Requires Updates Issues & PRs which requires input or update from the author

Comments

@rholighaus
Copy link
Contributor

rholighaus commented Oct 28, 2016

Issue

SugarFeed puts module name into lower case even though it's localized name is upper case.

Expected Behavior

Administrator neuer Fall erstellt ... (upper case Fall, German for Case, singular!)

Actual Behavior

Administrator neuer fall erstellt ...

Steps to Reproduce

  1. Install German Language Pack
  2. Log in selecting German language
  3. Goto Admin->Rename Module and correct Singular Case name from "Fälle" (plural!) to "Fall" (note the upper case spelling!)
  4. Create a new case
  5. Verify SugarFeed

Your Environment

  • SuiteCRM Version used: SuiteCRM 7.7.6
  • Language Pack German (Germany) 7.7.5.2 (downloaded from crowdin.com)
  • Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): any
  • Environment name and version (e.g. MySQL, PHP 7): PHP 5.6.27-0+deb8u1, Apache/2.4.10 (Debian)
  • Operating System and version (e.g Ubuntu 16.04): Debian 8.6/jessie
@shogunpol
Copy link

@rholighaus , Is this translations for SuiteCRM are made by: https://crowdin.com/project/suitecrmtranslations
if yes, can be contributed back there, and are unable to be updated in this project on github,
@horus68 may be able to help with this.

@JimMackin JimMackin added the Status:Requires Updates Issues & PRs which requires input or update from the author label Oct 28, 2016
@shogunpol
Copy link

Thank you for raising this issue however due to no activity in the last 14 days this issue will be closed, If this issue still exists and information can be given to allow us to proceed with this it can be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status:Requires Updates Issues & PRs which requires input or update from the author
Projects
None yet
Development

No branches or pull requests

3 participants