Changes needed to accomodate changes to the PG POD and sample problem generation.#2842
Merged
somiaj merged 1 commit intoopenwebwork:developfrom Feb 1, 2026
Merged
Conversation
drgrice1
force-pushed
the
pod-and-sample-problem-updates
branch
from
3c3611f to
cb7eab7
Compare
drgrice1
force-pushed
the
pod-and-sample-problem-updates
branch
2 times, most recently
from
bffe412 to
8c27517
Compare
drgrice1
force-pushed
the
pod-and-sample-problem-updates
branch
from
8c27517 to
0182051
Compare
drgrice1
force-pushed
the
pod-and-sample-problem-updates
branch
3 times, most recently
from
c340cbe to
59991bc
Compare
… generation. First, there are some minor tweaks to the POD and sample problem viewers: * Fix the wording on the sample problem viewer index page for "Sample Problems by Macro". It current says, "For many macros, this lists all sample problems used by the macro." However, macros do not use sample problems. Sample problems use macros. So the wording is now, "For many macros, this lists all sample problems that use the macro." * Update the version of bootstrap in the POD templates to 5.3.7 which is currently the latest. * Update the links in the pod templates to wiki.openwebwork.org. * Remove the `favicon` links. Those are not explicitly needed. Browser's now load the favicon even if the page does not contain the link. The link only needs to be added if the file is not named favicon.ico. The following are the actual changes needed to accomodate changes to the PG POD and sample problem generation: * Remove files that are now used from the PG repository. * Remove the PODViewer js and css files, the PODParser.pm and PODtoHTML.pm modules, and category-index.mt and pod.mt templates, all of which are now provided by PG. * Make the necessary changes to the generate-ww-pg-pod.pl script so that it can use those files from the PG repository. * Update the SampleProblemParser module usage for its changes and namespace change. * The `WeBWorK::PG::SampleProblemParser` module now handles generation of the actual search data with its `getSearchData` method. So the `WeBWorK::ContentGenerator::SampleProblemViewer` just calls that method. * The `assets/stop-words-en.txt` file is now in the PG repository so that the `WeBWorK::PG::SampleProblemParser::getSearchData` method can get at it easily. * The `htdocs/js/SampleProblemViewer/documentation-search.js` file is now in the PG repository, and webwork2 uses it from there. PG also copies it to the PG docs github pages site in its new workflow. The options are passed in via the script in `templates/ContentGenerator/SampleProblemViewer.html.ep`.
drgrice1
force-pushed
the
pod-and-sample-problem-updates
branch
from
59991bc to
bafd2a0
Compare
pstaabp
approved these changes
Jan 31, 2026
Member
pstaabp
left a comment
pstaabp
left a comment
There was a problem hiding this comment.
All looks good. Had tested this on the PG side earlier.
somiaj
approved these changes
Feb 1, 2026
Contributor
somiaj
left a comment
somiaj
left a comment
There was a problem hiding this comment.
POD and Sample problem generation works without issue.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First, there are some minor tweaks to the POD and sample problem viewers:
Fix the wording on the sample problem viewer index page for "Sample Problems by Macro". It current says, "For many macros, this lists all sample problems used by the macro." However, macros do not use sample problems. Sample problems use macros. So the wording is now, "For many macros, this lists all sample problems that use the macro."
Update the version of bootstrap in the POD templates to 5.3.7 which is currently the latest.
Update the links in the pod templates to wiki.openwebwork.org.
Remove the
faviconlinks. Those are not explicitly needed. Browser's now load the favicon even if the page does not contain the link. The link only needs to be added if the file is not named favicon.ico.The following are the actual changes needed to accomodate changes to the PG POD and sample problem generation:
Remove files that are now used from the PG repository.
Remove the PODViewer js and css files, the PODParser.pm and PODtoHTML.pm modules, and category-index.mt and pod.mt templates, all of which are now provided by PG.
Make the necessary changes to the generate-ww-pg-pod.pl script so that it can use those files from the PG repository.
Update the SampleProblemParser module usage for its changes and namespace change.
The
WeBWorK::PG::SampleProblemParsermodule now handles generation of the actual search data with itsgetSearchDatamethod. So theWeBWorK::ContentGenerator::SampleProblemViewerjust calls that method.The
assets/stop-words-en.txtfile is now in the PG repository so that theWeBWorK::PG::SampleProblemParser::getSearchDatamethod can get at it easily.The
htdocs/js/SampleProblemViewer/documentation-search.jsfile is now in the PG repository, and webwork2 uses it from there. PG also copies it to the PG docs github pages site in its new workflow. The options are passed in via the script intemplates/ContentGenerator/SampleProblemViewer.html.ep.Note that this depends on openwebwork/pg#1346.