Conversation
- Added note at top of page - Added troubleshooting entries from GitHub Discussions - Updated Table of Contents Fixes oppia#207
Updated instructions for loading data and creating classrooms, including clarifications and reordering of steps.
|
@HardikGoyal2003 for #434 (comment) 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. |
|
@jayam04 PTAL, gentle reminder. |
|
@jayam04 gentle ping. |
jayam04
left a comment
jayam04
left a comment
There was a problem hiding this comment.
@rohanmalhotracodes Thank you for the updates. I have reviewed your changes.
| 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. |
| 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. |
There was a problem hiding this comment.
Specify, you must use email suggested on login for the first time to access /admin page.
| ### 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:** |
There was a problem hiding this comment.
This was part of Docker setup, which we have already dropped. So, you can remove this.
|
Gentle ping @jayam04 sir anything else you'd like me to addre |
|
@rohanmalhotracodes Give me a day, I will review it. |
jayam04
left a comment
jayam04
left a comment
There was a problem hiding this comment.
@rohanmalhotracodes Sorry for late review, left few comments.
| ### 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. |
There was a problem hiding this comment.
I am not sure about this. Can you link to Discussions/Issues that shows this approach helps troubleshoot the problem.
There was a problem hiding this comment.
Removed the section as the points I wrote were too generic and there was no reliable way to determine whether they fix the issue
|
PTAL @jayam04 |
|
@HardikGoyal2003 it has been a while and for some reason I am unable to tag Jayam sir, any idea on how to address this further. All changes which I was told have been added. |
jayam04
left a comment
jayam04
left a comment
There was a problem hiding this comment.
LGTM, thank you @rohanmalhotracodes
|
Please merge whenever possible @HardikGoyal2003 @jayam04 . Thanks |
3 participants
Summary of Changes
Opia→OppiaGithub→GitHubAlthough 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