greenlight
greenlight copied to clipboard
Error 500
Describe the bug when selecting Arabic in user profile, error 500 is displayed. v2.13.0
To Reproduce Steps to reproduce the behavior:
- Go to user profile
- Click on language
- Scroll down to Arabic
- Save the update
- click on home
Expected behavior Arabic home screen
Actual behavior error 500 is displayed
Screenshots
Thank you, however, the error was on the link of the v2.13 email announcement and not on our local server.
Ali
On 8/24/22 9:07 AM, GUFFMHRZ wrote:
500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong.
I think i have the same issue.
Something to note: I have no trouble on our testservers, which have a single Greenlight instance with its own postgres container. In our production environment, where the error occurs, 2 greenlight instances share one postgres-db(non-docker)
— Reply to this email directly, view it on GitHub https://github.com/bigbluebutton/greenlight/issues/3800#issuecomment-1225240220, or unsubscribe https://github.com/notifications/unsubscribe-auth/AR6ACJZQ57VENWA55E7RBFLV2W32BANCNFSM57MWXDGA. You are receiving this because you authored the thread.Message ID: @.***>
issue is that the locale yml file is wrong for both arabic and iraqi arabic. it uses b as a token when it should be %b. config/locales/ar.yml
The fix is like the following json, it requires removing the % from the end and adding it behind the b like so:
both files: ./config/locales/ar.yml ./config/locales/ar_IQ.yml
time:
formats:
default: "%b %d, %Y %-I:%M%P"
Likely caused by some editor dealing with RTL.
https://github.com/bigbluebutton/greenlight/pull/4055
Please note: Greenlight v3 has been released. With this new version, many of the issues and bugs that were present in v2 have been resolved.
As a result, we will no longer be providing updates or support for v2 (except for major security issues), and we will be closing any outstanding bug reports / feature requests related to v2. While we understand that some of you may still be using v2, we highly encourage you to upgrade to v3 to take advantage of the improved features and stability. If your request/bug still applies to v3, please open a new issue for it