← Help Center

Troubleshooting

ScholarForge
ScholarForge helps teachers share classroom-ready resources and collaborate on units that work.
Built by educators. Designed for classrooms, homeschoolers, and lifelong learners—anywhere.

Troubleshooting

Most issues are small and fixable. Start with the quick checks, then use the section that matches your problem.
Quick checks (do these first)
  • Refresh the page (yes, really).
  • Try Chrome if you’re using something else.
  • Turn off browser extensions (ad blockers can break buttons sometimes).
  • If you’re on a phone, rotate to landscape for drag/drop questions.
  • If something looks “stuck,” log out and log back in.
🔐 Login / Access problems
  • Can’t log in: confirm email/password, then try reset if available.
  • Keeps sending me to login: cookies may be blocked—enable cookies for this site.
  • I’m logged in but can’t see Teacher Area: your account may not be marked as teacher yet.
If you’re a teacher and don’t have teacher access, send a quick message and we’ll fix it.
🔎 “Page not found” (404)
  • Double-check the URL (typos happen).
  • If someone sent you a link, try going to the main page and navigating there instead.
  • If you just created a new file, confirm the filename is exactly right (no hidden .txt, no trailing spaces).
If a help page 404s but a text file loads, the PHP filename is usually the culprit.
📤 Upload problems (Lesson Library)
  • Upload fails: try a smaller file or export as PDF.
  • Upload “works” but doesn’t show: refresh, then check you’re in the correct section/category.
  • Weird characters in filenames: rename the file on your computer to something simple (letters/numbers).
🔑 Quiz code problems
  • Code doesn’t work: confirm it’s typed exactly (letters/numbers only).
  • Still not working: the teacher may not have the session set to Open.
  • Wrong quiz: the teacher may have shared an old code—ask for the correct one.
🧩 Drag & drop / Matching feels “broken”
  • On phones, rotate to landscape and try again.
  • Use Chrome if possible.
  • Close extra tabs (low memory can cause glitches).
These question types are more sensitive to screen size and browser behavior.
🧾 Something “looks wrong”
  • Try a hard refresh (Ctrl+F5 on Windows).
  • If a button is missing, scroll—on small screens content can stack.
  • If text overlaps, zoom back to 100% in your browser.
Admin notes (site-wide issues)
If multiple users report the same breakage, it’s likely a deploy/change, a database column mismatch, or a permissions/file-path issue.
  • Check error logs first (PHP/Apache).
  • Confirm document root and file paths.
  • When adding new pages, watch for hidden filename characters (.txt, trailing spaces).
Still stuck?
Send a message. Include what page you were on and what you expected to happen.
The “Report a bug” link in the site footer also includes page/time details automatically.