Skip to content

Make sure to account for an undefined ANSWER_ENTRY_ORDER in the single problem grader. (Hotfix of #3195) - #3196

Merged
somiaj merged 1 commit into
openwebwork:mainfrom
drgrice1:bugfix/grader-undef-answer-order-hotfix
Sep 7, 2026
Merged

Make sure to account for an undefined ANSWER_ENTRY_ORDER in the single problem grader. (Hotfix of #3195)#3196
somiaj merged 1 commit into
openwebwork:mainfrom
drgrice1:bugfix/grader-undef-answer-order-hotfix

Conversation

@drgrice1

@drgrice1 drgrice1 commented Sep 3, 2026

Copy link
Copy Markdown
Member

Previously the problem grader could only be made visible when the problem successfully rendered. Now that it is always visible, a little more care is needed. The ANSWER_ENTRY_ORDER array in the PG flags will not be defined if the problem does not successfully render.

This fixes issue #3194.

@Alex-Jordan

Copy link
Copy Markdown
Contributor

I can't merge this and #3195 without rebasing first. Can you check on things? I don't want to cause any git headaches.

…gle problem grader.

Previously the problem grader could only be made visible when the
problem successfully rendered.  Now that it is always visible, a little
more care is needed.  The `ANSWER_ENTRY_ORDER` array in the PG flags
will not be defined if the problem does not successfully render.

This fixes issue openwebwork#3194.
@drgrice1
drgrice1 force-pushed the bugfix/grader-undef-answer-order-hotfix branch from dd18db4 to 62003d4 Compare September 7, 2026 01:26
@somiaj
somiaj merged commit 18f18e7 into openwebwork:main Sep 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants