Skip to content
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.

docs: update troubleshoot_general_tips.rst #1194

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Guilleves
Copy link

Add fix for blank login/signup pages on localhost:18000


I've completed each of the following or determined they are not applicable:

  • Made a plan to communicate any major developer interface changes (or N/A)

@Guilleves Guilleves self-assigned this Oct 3, 2023
Add fix for blank login/signup pages on localhost:18000
Copy link
Contributor

@robrap robrap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. Mostly just some clarifying questions. Thanks.

--------------------------
After starting LMS/CMS (and compiling static assets for both), it's possible you run into a blank page when trying to sign in via http://localhost:18000/login.

This is most likely a cache issue and can be easily fixed in 2 different ways:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to choose your own language, but what do you think of the sentiments I am trying to add here?

Suggested change
This is most likely a cache issue and can be easily fixed in 2 different ways:
If you think that everything is up-to-date, this is most likely a cache issue and might be easily fixed in 2 different ways:

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is some great wording, thanks!

@@ -236,6 +236,15 @@ The fix is to get a new auth session. You can do any of the following:
4. Log in
5. Navigate back to the MFE

Blank login/signup screens
--------------------------
After starting LMS/CMS (and compiling static assets for both), it's possible you run into a blank page when trying to sign in via http://localhost:18000/login.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[question] Does this mean this is for the legacy login experience, and not using an MFE? Would it help to be explicit, or is the port good enough? I'm not sure if the MFE has a different port?

This is most likely a cache issue and can be easily fixed in 2 different ways:

1. Hard reloading the page, or
2. Rebuilding the frontend and giving it another try
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you clarify what "rebuilding the frontend" means?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussing this with Marcos (who pointed me to the fix), looks like this is not relevant to this use case. It was intended to say something along the lines of "try recompiling your assets", but it doesn't have anything to do with the actual fix. Will update

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants