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

Support User: localeSlug error when active #3843

Closed
jordwest opened this issue Mar 8, 2016 · 2 comments · Fixed by #6854
Closed

Support User: localeSlug error when active #3843

jordwest opened this issue Mar 8, 2016 · 2 comments · Fixed by #6854
Assignees
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Type] Bug

Comments

@jordwest
Copy link
Contributor

jordwest commented Mar 8, 2016

When support user mode is active, the following error sometimes appears:

983f3604-e440-11e5-805e-132b182f94ea

Originally reported by @dllh in #3820 and #3778

@jordwest jordwest added [Type] Bug [Feature Group] Support All things related to WordPress.com customer support. labels Mar 8, 2016
@jordwest jordwest self-assigned this Mar 8, 2016
@lancewillett
Copy link
Contributor

Does this cause UI issues? Is it repeatable? I'd say let's ignore it unless it causes UI problems. Feel free to reopen if it's important or urgent.

jordwest added a commit that referenced this issue Jul 17, 2016
This change adds a condition to exit the community translator jumpstart
if no user is found, preventing an exception which can halt the boot
process.

Support user starts Calypso with no user, which currently causes
the communityTranslatorJumpstart function to fail with an exception
"Cannot read property 'localeSlug' of undefined" - see #3843.

Any process that used this function was breaking on the exception.

Issue #6645 introduced a notices middleware which indirectly called
the translator jumpstart in the Calypso boot process, before the support
user was loaded. The localeSlug error thus broke the Calypso boot
process.

Closes #3843
@jordwest
Copy link
Contributor Author

Re-opening until #6854 is merged, as it's now causing support user to fail after the reboot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Type] Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants