Mom Page Map

When to Use

• User asks how to get to a specific MyOpenMath teacher page
• Another MOM skill needs exact URL patterns or selector anchors
• A workflow must move between course home, question editor, assessment settings, add/remove questions, or gradebook pages
• Browser automation keeps failing on native dropdowns, block menus, TinyMCE fields, or preview/test pages

When NOT to Use

• Grading logic on gradeallq2.php where the dedicated grading selectors skill should drive DOM details
• Aeries workflows or cross-system sync logic that belongs to gb-compare, gb-new-assignment, gb-sync, or gb-pipeline
• Student-facing usage instructions unrelated to instructor automation

Guardrails

⚠️ Must NOT:

• Never lose or rewrite the exact MOM URL patterns; reuse them exactly as documented in references/navigation-patterns.md.
• Never treat testquestion2.php as a student page. It is an instructor-only authoring/verification tool.
• Never treat blockh{bid} as the block URL id. DOM ids use blockh{bid}; URLs use the hierarchical path like 0-1.
• Never .click() native <option> elements inside the course-page Add An Item dropdown. Use direct URL navigation or selectOption() with a pre-captured navigation wait.
• Never declare a question working from testquestion2.php until Submit returns a Correct result.
• Never set hidden editor fields such as #qtype or #libs directly when the UI flow is required to keep MOM state consistent.
• Never assume a hardcoded canvas id or fixed assessment entry point when the page can be reached more safely by URL construction.

Quick Start

1. Extract cid from the current MOM URL, then derive aid, qid, or block path from stable links or toggleblock(...) data.
2. Navigate by exact URL first; only use DOM controls when the URL depends on current page state.
3. If the target page writes or validates content, use the page-specific selector and verification notes in references/navigation-patterns.md.

Workflow

Phase 1: Identify the Current MOM Context

• INPUT: Any instructor-side MOM page
• ACTION:
  • Read cid from location.href.
  • Extract aid from assessment links or addassessment2.php?id={aid}.
  • Extract qid from moddataset.php?id={qid} or preview links.
  • Extract both block identifiers from toggleblock(event,'{bid}','{path}') when working with folders/sections.
• OUTPUT: Stable ids for URL construction

const url = new URL(state.page.url());
const cid = url.searchParams.get('cid');

const ids = await state.page.evaluate(() => {
  const settings = document.querySelector('a[href*="addassessment2.php"]');
  const aid = settings ? new URL(settings.href).searchParams.get('id') : null;
  return { cid: new URL(location.href).searchParams.get('cid'), aid };
});

Phase 2: Navigate by Direct URL Whenever Possible

• INPUT: cid plus any page-specific ids
• ACTION:
  • Build the exact target URL from the preserved MOM patterns.
  • Prefer direct goto() for course tools, question editor pages, assessment settings, block edit pages, gradebook pages, and URL-only routes.
  • Use DOM interaction only when you must discover an id or when the UI performs a stateful action that cannot be reconstructed safely.
• OUTPUT: Correct instructor page loaded with fewer fragile clicks

Common examples:

For assessment settings reached from the course page, block={block} uses the hierarchical block path (0, 0-1, 0-2, ...) rather than the DOM bid / blockh{bid} id.

Phase 3: Use Page-Specific Navigation Patterns

• INPUT: Loaded MOM page plus target action
• ACTION:
  • On course.php, treat Add An Item as a native <select> and use the safe dropdown rules.
  • For blocks, target the anchor with role button named Options for {Block Name} or skip menus with direct URLs.
  • On manageqset.php, moddataset.php, addassessment2.php, and addquestions2.php, use the preserved selectors for search, edit, save, and add/remove operations.
  • For TinyMCE-backed fields and hidden inputs, follow the editor-specific caveats instead of assuming standard .fill() behavior.
• OUTPUT: Safe page mutations or stable read-only extraction

Key selectors to keep handy:

Phase 4: Respect Teacher vs Student Views and Validation Rules

• INPUT: Assessment or question-verification workflow
• ACTION:
  • Use testquestion2.php?cid={cid}&qsetid={qid} for instructor preview and author verification.
  • Use assess2/?cid={cid}&aid={aid} only when you explicitly need the student-facing assessment view.
  • Use moasettings.php?cid={cid}&aid={aid} for per-student settings/dates/exceptions.
  • On testquestion2.php, submit an answer and confirm MOM returns Correct before reporting success.
• OUTPUT: Correct page choice and verified authoring result

await state.page.goto(
  `https://www.myopenmath.com/course/testquestion2.php?cid=${cid}&qsetid=${qid}`,
  { waitUntil: 'domcontentloaded' }
);
await state.page.locator('input[type="button"][value="Submit"]').click();
const resultText = await state.page.locator('.scoredisplay, .correct, .incorrect').first().textContent();
if (!/1\/1|Correct/i.test(resultText || '')) {
  throw new Error(`Preview validation failed: ${resultText || 'no result shown'}`);
}

Error Handling

Common Mistakes

Selectors / References

• Full URL tables, navigation formulas, block DOM patterns, editor selector maps, TinyMCE notes, teacher/student page differences, AJAX behavior, and draw-question validation details live in references/navigation-patterns.md.
• If another MOM skill needs a page route, copy the exact pattern from that reference instead of rewriting it from memory.