--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAHyrz10LQE2grBT%3Dv8WEbRpGrEiZ4%3DzErxbmVJHcAs7Jr9h6Sg%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CA%2BR-jrf%3DgrUqwvrtTYQgfB9wFcJMnyRd017Z3vde1n8oquMoLQ%40mail.gmail.com.
> But I think PreTeXt will be ready for 2.19 soon.
It should be already! As of a merged PR within the past 24 hours.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAH%2BNcPa-2GJVx97U1EKZ0cpni5bxoW%3DCoznVKqjiioExZJMsKw%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CA%2BR-jreV1wtJ%3DpONWLTsTX4bQtk0uZ6hP5Ckb-8x3S9T_jVb5Q%40mail.gmail.com.
After the upgrade, you will need to rebuild. Starting with a new static representations file, and then also rebuild new HTML.
- Using the CLI:
pretext generate webwork [-t target_name]
pretext build [-t target_name]- Using pretext directly:
pretext/pretext/pretext -p pubfile -c webwork mainfile
pretext/pretext/pretext -p pubfile -c all -f html mainfile
("pubfile" should be a path to your publisher file, and "mainfile" a path to your project's root source file.)
--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/08c75da8-230e-4235-a199-329a4a3a99dcn%40googlegroups.com.
When I go to this page:and open the first checkpoint knowl, I do see an Activate button. Were you saying that you "lost" it in the sense that it's not there? If there is some other exercise where it is missing, can you link to a direct page where that is the case?Then when I click to use the button, it won't load because there is a CORS error. However, this is a distraction and should be resolved because of the following.Looking at the source for the page, your pages are still trying to use 2.17 WeBWorK js. This indicates that you haven't rebuilt the WeBWorK representations (and then the HTML) since the upgrades. Do you follow the pretext-announce mailing list? There was an alert there on August 4th (and 12th) with instructions. Here is the part that may be what you need to do:After the upgrade, you will need to rebuild. Starting with a new static representations file, and then also rebuild new HTML.
- Using the CLI:
pretext generate webwork [-t target_name]
pretext build [-t target_name]- Using pretext directly:
pretext/pretext/pretext -p pubfile -c webwork mainfile
pretext/pretext/pretext -p pubfile -c all -f html mainfile
("pubfile" should be a path to your publisher file, and "mainfile" a path to your project's root source file.)
On Wed, Aug 20, 2025 at 11:43 AM Jane Butterfield wrote:
I have a related question (I thought I had posted it earlier today, but it looks as if I deleted it by mistake, so apologies if this comes through twice).Our PreTeXt project lost the "activate" option on our WeBWorK exercises some time between last August (2024) and yesterday. I have been re-reading the documentation in Chapter 7 and Chapter 38 from the PreTeXt Guide https://pretextbook.org/doc/guide/html/guide-toc.html to try to work out what may have happened. I see from one of the comments in this thread that PreTeXt only recently became compatible with WeBWorK 2.19, and also that the default server used for PreTeXt projects is https://webwork-ptx.aimath.org/ Our sysadmin tells me that AIM has recently changed to WeBWorK 2.20, so I wondered if that could be the problem?Either way, I think we probably want to change our project to use our own WeBWorK server, and I couldn't work out how to do that. Chapter 38 has clear instructions for configuring the server and the course, and Chapter 7 has clear information about how to author the problems themselves. I just couldn't work out how I tell my project that it should look to my server instead of the default one. What am I missing? (It is almost certainly something really obvious and trivial.)Apologies again if this question comes through twice. The project I'm working on is https://web.uvic.ca/~jvbutter/PreCalcReview/
On Friday, July 18, 2025 at 1:40:37 PM UTC-7 wrote:Dear all,
I'm working on a PreTeXt-based textbook project that is currently under active development. So far, we haven’t integrated any interactive exercises, but we plan to focus on this in the coming months and want to make informed decisions early on.
We’ve identified a collection of WeBWorK problems (around 300) that would be pedagogically appropriate. However, we do not currently have access to a dedicated WeBWorK server. This raises a few questions:We’re not planning to host the textbook on Runestone (though we’re open to discussing it). Being based in Canada, we likely wouldn’t be able to use it for full course delivery (some legal stuff).
- Is a running WeBWorK server required only at the time of PreTeXt compilation (e.g., to generate static HTML or embed problems), or is persistent server access needed for the final deployment?
- Are there any community-hosted or lightweight options for testing and rendering WeBWorK problems within a PreTeXt workflow?
The only server we might have permanent access to is running WeBWorK 2.16, which has shown compatibility issues with some existing problems. So even if we manage to set it up, the usable subset of our problem bank may be significantly reduced. I may be able to borrow a newer version, but occasionally only.
Any guidance on best practices, tooling, or hosting options would be greatly appreciated.
Best regards,
JC
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/fc26d9b2-ad32-472b-a780-59ce8f7192b7n%40googlegroups.com.