webwork/task heading level bug

[Mitch Keller]

Working on updating Active Calculus Single Variable to handle the update that writes out each webwork exercise as its own file, and I’m running into issues with the WW exercises that are authored in the PTX source and structured with task. These mostly appear within the Preview Activities, which are #exploration but also on a handful of #exercise that were written into the PTX source and use #task.

Generation runs fine, but when trying to build HTML output, I get the following error message repeated for each webwork/task:

"hN" template reached without a $heading-level parameter on element <task> at pretext/book/chapter/section/subsection/exploration/webwork-reps/static/task; defaulting to h2

Hopefully someone can run this down relatively quickly. In case it helps, source for a problematic file can be found at https://github.com/mitchkeller/active-calculus-single-mbx/blob/deprec2026/source/previews/PA-8-1-WW.xml, which shows the branch that I’m working off of.

Thanks!

Mitch

-- 
Mitch Keller
mi...@rellek.net

http://www.rellek.net/

[Rob Beezer]

Will investigate at some point, unless somebody beats me to it.

Likely benign, at worst there may be some "hN" stuff that are wrong for
accessibility purposes.

A small example that is fubar'ed could help speed things along. And if you put
it nicely formatted as code on an issue, my assistant would be even happier.

Thanks,
Rob

On 7/6/26 13:46, Mitch Keller wrote:
> Working on updating Active Calculus Single Variable to handle the update that
> writes out each webwork exercise as its own file, and I’m running into issues
> with the WW exercises that are authored in the PTX source and structured with
> task. These mostly appear within the Preview Activities, which are #exploration
> but also on a handful of #exercise that were written into the PTX source and use
> #task.
>
> Generation runs fine, but when trying to build HTML output, I get the following
> error message repeated for each webwork/task:
>
> "hN" template reached without a $heading-level parameter on element <task> at
> pretext/book/chapter/section/subsection/exploration/webwork-reps/static/task;
> defaulting to h2
>
> Hopefully someone can run this down relatively quickly. In case it helps, source
> for a problematic file can be found at https://github.com/mitchkeller/active-

> calculus-single-mbx/blob/deprec2026/source/previews/PA-8-1-WW.xml <https://
> github.com/mitchkeller/active-calculus-single-mbx/blob/deprec2026/source/
> previews/PA-8-1-WW.xml>, which shows the branch that I’m working off of.

>
> Thanks!
>
> Mitch
>
> --
> Mitch Keller
> mi...@rellek.net
>
> http://www.rellek.net/
>

> --
> 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 <mailto:pretext-
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> support/9DF36AD9-F896-4D1F-968C-437E4467596E%40rellek.net <https://
> groups.google.com/d/msgid/pretext-support/9DF36AD9-
> F896-4D1F-968C-437E4467596E%40rellek.net?utm_medium=email&utm_source=footer>.

[Mitch Keller]

While the output does look OK, I suspect the level of error reporting will cause Runestone to deem the build failed:

critical: There were errors during the build.  See above.

critical: Failed to build without errors.  Exiting…

I can definitely post an issue with some nicely formatted code. Would an exercise or exploration be enough, or do I need to supply a division around it?

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/MTAwMDAxMy5iZWV6ZXI.1783371851%40pnsh.

[Rob Beezer]

On 7/6/26 14:10, Mitch Keller wrote:
> I can definitely post an issue with some nicely formatted code. Would an
> exercise or exploration be enough, or do I need to supply a division around it?

Unless you think you have it in a weird place, just teh #exercise or
#exploration should be fine. My assistant can be very flexible some of the time.

[Mitch Keller]

Location complies with schema, so shouldn’t be a weird spot. Posted issue at https://github.com/PreTeXtBook/pretext/issues/3008.

--
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/MTAwMDAyMy5iZWV6ZXI.1783372749%40pnsh.

[Rob Beezer]

Does your version contain commit 25b65361?

On 7/6/26 14:10, Mitch Keller wrote:

> While the output does look OK, I suspect the level of error reporting will cause
> Runestone to deem the build failed:
>
> critical: There were errors during the build.  See above.
> critical: Failed to build without errors.  Exiting…
>
> I can definitely post an issue with some nicely formatted code. Would an
> exercise or exploration be enough, or do I need to supply a division around it?
>

>> On Jul 6, 2026, at 16:04, 'Rob Beezer' via PreTeXt support <pretext-

> C9D5CFB6-6095-4F41-8FAF-1A4EF75679C0%40rellek.net <https://groups.google.com/d/
> msgid/pretext-support/C9D5CFB6-6095-4F41-8FAF-1A4EF75679C0%40rellek.net?
> utm_medium=email&utm_source=footer>.

[Mitch Keller]

Yes. I’m on CLI 2.43.1, which reports 73e61ec2c3f91468a80a12ce249fa69a734e6d26 as the core resources commit.

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/MTAwMDAzOC5iZWV6ZXI.1783377464%40pnsh.

[Rob Beezer]

Well, that sent Claude Code into a tailspin. Eventually gave up and claimed you
had an out-of-date version. When that was refuted, it soldiered on and
eventually found it was in the Runesone manifest creation where headings were
being manufactured (for the #task, I believe). That's why you were seeing good
heading-levels in the mainstream output - just looking in the wrong place it
turns out.

And we fixed up one undiscovered, similar bug.

Can you confirm with a nightly?

Thanks for the report, and for feeding my assistant a good example for testing.

https://github.com/PreTeXtBook/pretext/issues/3008
https://github.com/PreTeXtBook/pretext/issues/3009

On 7/6/26 16:22, Mitch Keller wrote:
> Yes. I’m on CLI 2.43.1, which reports 73e61ec2c3f91468a80a12ce249fa69a734e6d26
> as the core resources commit.
>

>> On Jul 6, 2026, at 17:37, 'Rob Beezer' via PreTeXt support <pretext-

> support/4B6404BC-86B8-40B9-9658-8D2E814037C6%40rellek.net <https://
> groups.google.com/d/msgid/pretext-
> support/4B6404BC-86B8-40B9-9658-8D2E814037C6%40rellek.net?
> utm_medium=email&utm_source=footer>.

[Mitch Keller]

Rebuilt using development CLI using latest PreTeXt XSL from Github and the error went away. When an updated CLI with that commit gets released, then we can finalize updates to get Runestone’s builds working again.

Thanks!

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/MTAwMDAwNS5iZWV6ZXI.1783436297%40pnsh.