Instead of opening the problem using the editMode hack of the usual problem page, render the problem directly in its own page via the render_rpc endpoint. This means the style hacks in the PGML-lab problem are also not needed since the elements that were being hidden are not present in the page to begin with.
The PGMLLab link in a course's templates directory is not needed as the problem source is read directly from the assets directory, and submitted to the render_rpc endpoint via the uriEncodedProblemSource parameter.
Also, add examples of using PGML tags to the PGML lab problem. The examples are in the "Substitutions" drop down menu of "Examples". In particular there is an exmaple demonstrating how to use PGML tags for placement of the feedback button with MultiAnswer problems that use singleResult => 1.
Instead of opening the problem using the
editModehack of the usual problem page, render the problem directly in its own page via therender_rpcendpoint. This means the style hacks in the PGML-lab problem are also not needed since the elements that were being hidden are not present in the page to begin with.The PGMLLab link in a course's templates directory is not needed as the problem source is read directly from the assets directory, and submitted to the
render_rpcendpoint via theuriEncodedProblemSourceparameter.Also, add examples of using PGML tags to the PGML lab problem. The examples are in the "Substitutions" drop down menu of "Examples". In particular there is an exmaple demonstrating how to use PGML tags for placement of the feedback button with MultiAnswer problems that use
singleResult => 1.