I''m trying to put together a Web site in Webgen. However, I can''t figure out how to get the site to use Textile. When I try adding a ''sourcehandler.default_meta_options'' option to the config file, it keeps throwing stupid errors about hash merging and method calls and the like, and since I''m not a Ruby programmer, I have no idea how to track them all down. When I use the ''blocks'' meta option on every page, not only does the Textile not process, but my CSS file doesn''t show up. How do I get the entire site to use Textile while still having everything else work like the default? A configuration file snippet (that actually works) would be appreciated. -- LeafStorm
Am Mon, 21 Sep 2009 06:56:53 -0700 (PDT) schrieb Leaf <leafstormrush at gmail.com>:> I''m trying to put together a Web site in Webgen. However, I can''t > figure out how to get the site to use Textile. When I try adding a > ''sourcehandler.default_meta_options'' option to the config file, it > keeps throwing stupid errors about hash merging and method calls and > the like, and since I''m not a Ruby programmer, I have no idea how to > track them all down. When I use the ''blocks'' meta option on every > page, not only does the Textile not process, but my CSS file doesn''t > show up. > > How do I get the entire site to use Textile while still having > everything else work like the default? A configuration file snippet > (that actually works) would be appreciated.Put the following into your config.yaml file: default_processing_pipeline: Page: erb,tags,textile,blocks,fragments This changes only the used markup language from Markdown to Textile. -- Thomas
Thanks. The markup is working fine. The config file documentation gave
me the impression that I needed to use
sourcehandler.default_meta_information to do this.
My stylesheet''s still not getting copied, though. I added:
patterns:
Copy:
add: [''**/*.css'']
but the file still is not copied. It is named ''default.css'' in
the
root directory. Do you know why this could be happening?
-- Leaf
On Sep 22, 3:11?am, Thomas Leitner <t_leit... at gmx.at>
wrote:> Am Mon, 21 Sep 2009 06:56:53 -0700 (PDT)
> schrieb Leaf <leafstormr... at gmail.com>:
>
> > I''m trying to put together a Web site in Webgen. However, I
can''t
> > figure out how to get the site to use Textile. When I try adding a
> > ''sourcehandler.default_meta_options'' option to the
config file, it
> > keeps throwing stupid errors about hash merging and method calls and
> > the like, and since I''m not a Ruby programmer, I have no idea
how to
> > track them all down. When I use the ''blocks'' meta
option on every
> > page, not only does the Textile not process, but my CSS file
doesn''t
> > show up.
>
> > How do I get the entire site to use Textile while still having
> > everything else work like the default? A configuration file snippet
> > (that actually works) would be appreciated.
>
> Put the following into your config.yaml file:
>
> default_processing_pipeline:
> ? Page: erb,tags,textile,blocks,fragments
>
> This changes only the used markup language from Markdown to Textile.
>
> -- Thomas
> _______________________________________________
> webgen-users mailing list
> webgen-us... at
rubyforge.orghttp://rubyforge.org/mailman/listinfo/webgen-users
> My stylesheet''s still not getting copied, though. I added: > > patterns: > Copy: > add: [''**/*.css''] > > but the file still is not copied. It is named ''default.css'' in the > root directory. Do you know why this could be happening?The above is not necessary since css files are handled by copy sourcehandler by default. It''s odd that the file does not get copied... What happens if you run webgen in verbose mode (webgen -v -l 0)? Can you post the output? -- Thomas