Skip to content

Fix a minor issue resulting from #2935.#2949

Merged
dlglin merged 1 commit intoopenwebwork:WeBWorK-2.21from
drgrice1:bugfix/show-top-warn-pgcore-warnings
Apr 21, 2026
Merged

Fix a minor issue resulting from #2935.#2949
dlglin merged 1 commit intoopenwebwork:WeBWorK-2.21from
drgrice1:bugfix/show-top-warn-pgcore-warnings

Conversation

@drgrice1
Copy link
Copy Markdown
Member

There is no longer a pgwarning key set on the controller object for the lib/WeBWorK/ContentGenerator/Problem.pm module and never was a pgwarning key for the returned pg object in the
lib/ContentGenerator/GatewayQuiz.pm module. So use the correct key on the returned pg object in both cases. That is the warning_messages key.

The warning messages were still being shown at the bottom, but not the message at the top of the page notifying of the existence of those warnings. Since the warnings at the bottom might not be visible, the warnings may be missed.

There is no longer a `pgwarning` key set on the controller object for
the `lib/WeBWorK/ContentGenerator/Problem.pm` module and never was a
`pgwarning` key for the returned pg object in the
`lib/ContentGenerator/GatewayQuiz.pm` module.  So use the correct key on
the returned pg object in both cases.  That is the `warning_messages`
key.

The warning messages were still being shown at the bottom, but not the
message at the top of the page notifying of the existence of those
warnings.  Since the warnings at the bottom might not be visible, the
warnings may be missed.
@dlglin dlglin merged commit e8c293f into openwebwork:WeBWorK-2.21 Apr 21, 2026
2 checks passed
@drgrice1 drgrice1 deleted the bugfix/show-top-warn-pgcore-warnings branch April 21, 2026 21:17
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