Skip to content

docs: update Troubleshooting page with discussion-based fixes#514

Open
rohanmalhotracodes wants to merge 4 commits intooppia:developfrom
rohanmalhotracodes:docs/update-troubleshooting-discussions
Open

docs: update Troubleshooting page with discussion-based fixes#514
rohanmalhotracodes wants to merge 4 commits intooppia:developfrom
rohanmalhotracodes:docs/update-troubleshooting-discussions

Conversation

@rohanmalhotracodes
Copy link
Copy Markdown
Contributor

@rohanmalhotracodes rohanmalhotracodes commented Feb 25, 2026

Summary of Changes

  • Added a note at the top of the troubleshooting page clarifying that it includes solutions from GitHub Discussions updated before February 25, 2026.
  • Added additional troubleshooting entries sourced from relevant GitHub Discussions.
  • Updated the Table of Contents to reflect the newly added sections.
  • Resolved Issue Update docs to reflect removal of config tab #434 by removing outdated references to the Config tab and restructuring the steps to match the current admin workflow.
  • Clarified and expanded multiple steps related to:
    • Populating translation opportunities
    • Populating question opportunities
    • Generating explorations
    • Creating classrooms
  • Ensured the instructions align with the current UI and role assignment process.
  • Cross-verified the updated steps using:
    • The How to access Oppia webpages wiki documentation
    • LEAP team / Contributor Dashboard documentation
    • Admin Roles and Activities workflow
    • Classroom Admin workflow
  • Updated outdated documentation links where necessary.
  • Fixed minor typos and terminology inconsistencies for consistency and professionalism:
    • OpiaOppia
    • GithubGitHub

Although the typo fixes were not explicitly part of the original scope, they were minor consistency corrections and included here to avoid raising separate issues.

Issues Addressed

Fixes #207
Fixes #434

- Added note at top of page
- Added troubleshooting entries from GitHub Discussions
- Updated Table of Contents

Fixes oppia#207
@rohanmalhotracodes rohanmalhotracodes deleted the docs/update-troubleshooting-discussions branch February 25, 2026 16:19
@rohanmalhotracodes rohanmalhotracodes restored the docs/update-troubleshooting-discussions branch February 25, 2026 16:20
Updated instructions for loading data and creating classrooms, including clarifications and reordering of steps.
@rohanmalhotracodes
Copy link
Copy Markdown
Contributor Author

rohanmalhotracodes commented Feb 25, 2026

@HardikGoyal2003 for #434 (comment)
The "Config tab" reference also appears in the Oppia Wiki page How-to-access-Oppia-webpages.md, which is part of the oppia/oppia.wiki repository.
Since this is not in oppia-web-developer-docs, should this issue be moved to the main Oppia repo instead?

I have included the other changes in this PR itself.

PS: Can we maybe raise a new issue in the main repo of Oppia since I have included the fixes needed in docs here itself.

@rohanmalhotracodes
Copy link
Copy Markdown
Contributor Author

@jayam04 PTAL, gentle reminder.

@rohanmalhotracodes
Copy link
Copy Markdown
Contributor Author

@jayam04 gentle ping.

Copy link
Copy Markdown
Member

@jayam04 jayam04 left a comment

Choose a reason for hiding this comment

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

@rohanmalhotracodes Thank you for the updates. I have reviewed your changes.

Comment on lines +349 to +353
2. Run: `python -m scripts.start --dev`
3. If the issue persists, try: `python -m scripts.start --clean`
4. If necessary, run `yarn install` and restart the server.

This is typically a frontend build or caching issue rather than a backend problem.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@rohanmalhotracodes There is no option --dev

Comment on lines +363 to +368
1. Start the dev server.
2. Go to: `http://localhost:8181/admin`
3. Assign yourself the **admin role** from the roles tab.
4. Restart the server if necessary.

After assigning the admin role, the `/admin` page should load correctly.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Specify, you must use email suggested on login for the first time to access /admin page.

Comment on lines +398 to +402
### oppia-angular-build container exits during install/run

If the Oppia installation (e.g., `make build`, Docker startup, or `python -m scripts.start`) fails because the `oppia-angular-build` container exits unexpectedly or the build does not complete:

**Possible fixes:**
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This was part of Docker setup, which we have already dropped. So, you can remove this.

@rohanmalhotracodes
Copy link
Copy Markdown
Contributor Author

Gentle ping @jayam04 sir anything else you'd like me to addre

@jayam04
Copy link
Copy Markdown
Member

jayam04 commented Mar 19, 2026

@rohanmalhotracodes Give me a day, I will review it.

Copy link
Copy Markdown
Member

@jayam04 jayam04 left a comment

Choose a reason for hiding this comment

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

@rohanmalhotracodes Sorry for late review, left few comments.

6. Navigate back to the Admin page, then go to the Activities tab. Click Load Data under Load dummy new structures data.
7. For the question opportunities to be valid, their corresponding topics must be part of a classroom topic. Navigate to the classroom admin page: `http://localhost:8181/classroom-admin`.
8. Click **Add New Classroom** (or edit an existing classroom), and add the relevant **topic IDs** to the classroom. Save your changes.
9. To enable the “Submit Question” tab for your user, make sure your signed-in user is allowlisted for submitting question suggestions.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you add this back?

Click Add element under [topic_id] (in the “The details for each classroom page.” section) and enter the topic id for the new topics that were created. (You can find a topic’s ID in its page URL from the Topic and Skills Dashboard). Make sure to click save at the bottom of the config page.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done

Comment on lines +380 to +393
### Webpack “Cannot resolve module ‘fs’” frontend error

If your frontend build fails with an error like:
`Module not found: Error: Can't resolve 'fs' in ...`

it means your frontend code is trying to import a **Node-only module (`fs`)** that cannot be bundled for the browser.

**Cause:**
Frontend code shouldn’t import modules that only work in Node environments (like `fs`).

**Solution:**
1. Remove the import of `fs` or other Node-only modules from the frontend code.
2. If you need file access or Node functionality, move that logic to backend code or expose it via an API.
3. Rebuild (`yarn` / `python -m scripts.start --clean`) after fixing the import.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I am not sure about this. Can you link to Discussions/Issues that shows this approach helps troubleshoot the problem.

Copy link
Copy Markdown
Contributor Author

@rohanmalhotracodes rohanmalhotracodes Mar 26, 2026

Choose a reason for hiding this comment

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

Removed the section as the points I wrote were too generic and there was no reliable way to determine whether they fix the issue

@rohanmalhotracodes
Copy link
Copy Markdown
Contributor Author

PTAL @jayam04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants