webgen users - Oct 2008 - upgrading from webgen-0.5.3

Am Fri, 10 Oct 2008 16:09:53 +0200
schrieb Michael Franzl <franzl at corporatematters.at>:
> My working webgen-0.5.3 project stopped with the following error in 
> webgen-0.5.4., 0.5.5 and gettalong-webgen.
> 
> An error has occurred:   Error while processing 
> </articles/teil1.en.html>: No such content processor available: false
> 
> There''s nothing ''special'' in this file:
> 
>      ---
>      title: Einleitung
>      in_menu: true
>      sort_info: 100
>      belongs_to: exp
>      identifier: exp-teil1
> 
>      --- name:content
>      ##Teil 1
>      ###Einleitung
>      Text...
> 
> Note: belongs_to: is a custom meta key.
> 
> Unfortunately, I''m without a clue here...
Did you delete the generated cache file before running the new webgen
version? That may help. What do you have in your config.yaml file? Did
you change the default processing pipeline for page files?

If the above does not help, could you send me your webgen website for
further investigation?

-- Thomas

My working webgen-0.5.3 project stopped with the following error in 
webgen-0.5.4., 0.5.5 and gettalong-webgen.

An error has occurred:   Error while processing 
</articles/teil1.en.html>: No such content processor available: false

There''s nothing ''special'' in this file:

     ---
     title: Einleitung
     in_menu: true
     sort_info: 100
     belongs_to: exp
     identifier: exp-teil1

     --- name:content
     ##Teil 1
     ###Einleitung
     Text...

Note: belongs_to: is a custom meta key.

Unfortunately, I''m without a clue here...

Michael

> Did you delete the generated cache file before running the new webgen
> version? That may help.
Yes, didn''t help.

> What do you have in your config.yaml file?
Commented out everything in config.yaml, still the same problem.

> Did you change the default processing pipeline for page files?
Yes.

Ok, now I stripped my project to the bone and isolated the 
problem. webgen 0.5.4 and upwards doesn''t like this 
statement in page files anymore:

     --- pipeline:

It is an empty pipeline. Now I understand why it stops with 
the error

     No such content processor available: false

Anyhow, I''ve learned to circumvent this problem by writing

     --- pipeline:blocks

since I just want webgen to not resolve {relocatable: } 
tags, i.e., to conserve the syntax until it is passed to 
default.template.

Now even gettalong-webgen runs. Thanks,

Michael

> > Did you change the default processing pipeline for page files?
> 
> Yes.
> 
> Ok, now I stripped my project to the bone and isolated the 
> problem. webgen 0.5.4 and upwards doesn''t like this 
> statement in page files anymore:
> 
>      --- pipeline:
> 
> It is an empty pipeline. Now I understand why it stops with 
> the error
> 
>      No such content processor available: false
> 
> Anyhow, I''ve learned to circumvent this problem by writing
> 
>      --- pipeline:blocks
> 
> since I just want webgen to not resolve {relocatable: } 
> tags, i.e., to conserve the syntax until it is passed to 
> default.template.
> 
> Now even gettalong-webgen runs. Thanks,
This bug has been introduced when I changed the block option parsing
code to use YAML to convert the values into proper Ruby classes. I have
fixed this in my local repo and will push a new beta gem to github soon.

-- Thomas