http://aspen.io/ gives internal error messages

[techtonik]

Pretty much every page after the main one is failing.

For example, http://aspen.io/api/website/

[chadwhitacre]

[techtonik]

Traced to #297

[techtonik]

@whit537 how often is OTP (one time python) vs PPP (per page python) optimization is needed? It is the first time I hear about the difference. Does it worth to maintain a third section with that?

If optimization is needed, the OTP can be achieved with some first_time flag passed to simplate code.

I liked that simplates could be plain HTML files. That simplifies transition from pure web apps and back.

[techtonik]

• And also, shouldn't we bump major aspen version for that backward-incompatible change?

[techtonik]

• And also, resources must have at least three pages is very confusing - simplates must have at least three sections - is it what it means?

[chadwhitacre]

And also, shouldn't we bump major aspen version for that backward-incompatible change?

No. We're still pre-1.0. See #357 for the definition of 1.0.

[chadwhitacre]

The fix for this ticket is simple grunt work: we need to add another section separator ([---]) to all simplates on the site.

[techtonik]

Obligatory sections make simplates less attractive. Is there short explanation why it is not suitable anymore?

[pjz]

There's ambiguity if there's only two sections and no template header specified. We can DWIM if there's a template header (content type and/or renderer) specified, and we should do that - I'll work on a patch for that now, but if we're handed two sections with no template headers, it's unclear if the second page is meant to be python or a template using the default renderer and content type.

[pjz]

Fixed with #517

[chadwhitacre]

Confirmed fixed: http://aspen.io/api/website/.

!m @pjz