nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

malformed header from WFconstructor?

Adam Stoller

Environment

)Unfortunately - I'm not on the support contract for this customer - so I don't have direct access to support. I'll probably work around that - but I'm curious if anyone else who ran into this figured out the source of the problem.I'm fairly certain that it's one of those "small", "stupid" things - but those have the habit of taking significantly longer to resolve than the more complex issues.Ideas / solutions anyone?

Find more posts tagged with

Comments

jbonifaci

Adam, I think the problem is with:

print get_job_spec();

You need to change this to:

__INSERT__(get_job_spec());

~Jeff

Adam Stoller

Adam, I think the problem is with:
print get_job_spec();
You need to change this to:
__INSERT__(get_job_spec());
~Jeff

I thought about that a bit - but it shouldn't be (unless I move the entire statement outside the template_script section).

The documentation clearly shows the use of print (within the template_script section) and I'm pretty sure I've done that before ... but ... well, I'll be jiggered. It works!

<template_script><![CDATA[
...
propagate_from_dormant_tasks();
compute_activation_sets();
]]></template_script>
__INSERT__(get_job_spec());

Thanks!

jbonifaci

Haha, no problem. When I was looking through your code I saw you were using print instead of insert, so thought I'd try it out in one of my workflows. Sure enough, I got the same error you were seeing by only changing my code to use print instead of the insert. And btw, you can use __INSERT__ inside your template_script tags (I always do).

~Jeff