Webgen News webgen - static website generation made easy Thomas Leitner http://webgen.rubyforge.org webgen - Webgen::SourceHandler::Feed 2010-08-09T09:11:12+02:00 http://webgen.rubyforge.org/news/ webgen 0.5.14 released http://webgen.rubyforge.org/news/release_0_5_14.html 2010-08-09T08:50:00+02:00 2010-08-09T08:50:00+02:00 <p>This release changes the version of the kramdown library to 0.10.0 and contains one small bug fix.</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Minor changes:</p> <ul> <li>kramdown version equal to 0.10.0 is now needed</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>Fixed bug RF#28392: problem with rdoc test (reported by Hans de Graaff)</li> </ul> </li> </ul> webgen 0.5.13 released http://webgen.rubyforge.org/news/release_0_5_13.html 2010-07-16T08:30:00+02:00 2010-07-16T08:30:00+02:00 <p>This just a minor maintainance release which fixes some bugs and adds support for Sassy CSS.</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Minor changes:</p> <ul> <li>Specifying a prefix for kramdown generated header IDs is now possible</li> <li>Added support for <a href="../documentation/contentprocessor/scss.html">Sassy CSS</a></li> <li>A haml version greater than 3.0.0 is now needed</li> <li>A kramdown version greater or equal to 0.9.0 is now needed</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>Fixed problem in ContentProcessor::Less where a non-useful error message was shown</li> </ul> </li> </ul> webgen 0.5.12 released http://webgen.rubyforge.org/news/release_0_5_12.html 2010-04-14T20:30:00+02:00 2010-04-14T20:30:00+02:00 <p>This release includes two minor changes and some bug fixes: The output of the <a href="../documentation/tag/metainfo.html">meta information tag</a> is now escaped by default. This can be changed by setting the <code>tag.metainfo.escape_html</code> option in the configuration file. And a rake task for showing outdated translations has been added.</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Minor changes:</p> <ul> <li>Added a rake task to show outdated translations</li> <li>Added a <a href="../documentation/reference_configuration.html#tagmetainfoescapehtml">configuration option</a> for specifying whether a meta info value should be escaped</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>All error messages now display useful path names (reported by Eric Sunshine)</li> <li>Fixed another CSS bug with sub directories in style bundle ‘andreas07’ (reported by Thomas Deselaers)</li> <li>Fixed problem with unintentionally modified <code>link</code> meta information that lead to errors</li> <li>Commands are now correctly shown when running <code>webgen --help</code></li> <li>Fixed a problem where an incorrect path was shown in error messages</li> </ul> </li> </ul> webgen 0.5.11 released http://webgen.rubyforge.org/news/release_0_5_11.html 2010-02-15T09:30:00+01:00 2010-02-15T09:30:00+01:00 <p>In this release there are two big changes regarding the internals of webgen:</p> <ol> <li> <p>The dependency on facets has been removed since it was only used in two or three places and since the facets project is not very stable regarding its API.</p> </li> <li> <p>The default markup language used by the webgen is Markdown and the default processor for converting Markdown to HTML has been Maruku for a long time. However, Maruku has some bugs that need to be fixed and although it runs under Ruby 1.9 there are some issues. Therefore the new default processor for Markdown will be <a href="../documentation/contentprocessor/kramdown.html">kramdown</a> from now on. Aside from being actively maintained, it is about 5x faster than Maruku and runs on Ruby 1.9 without problems.</p> <p>This means that if you used the default configuration, you will automatically use kramdown from now on. If you still want to use Maruku, just change the default processing pipeline for page files:</p> <pre><code>default_processing_pipeline: Page: erb,tags,maruku,blocks,fragments </code></pre> <p>The short name <code>markdown</code> now also refers to kramdown instead of Maruku.</p> </li> </ol> <p>Aside from the new content processor <a href="../documentation/contentprocessor/kramdown.html">kramdown</a>, another content processor for <a href="../documentation/contentprocessor/less.html">LESS</a> has been added and the content processor <a href="../documentation/contentprocessor/head.html">head</a> has been updated to handle arbitrary <code>link</code> tags. Many bugs have been fixed in this release as well.</p> <p><em>Note</em>: All deprecated methods have been removed in this release!</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Major changes:</p> <ul> <li>Added content processor <a href="../documentation/contentprocessor/kramdown.html">kramdown</a> (faster Markdown parser)</li> <li>Added content processor <a href="../documentation/contentprocessor/less.html">less</a> (extends CSS with variables, mixins, operations, …)</li> <li>Updated content processor <a href="../documentation/contentprocessor/head.html">head</a> to allow the specification of arbitrary <code>link</code> tags and links to javascript and CSS files by the user</li> </ul> </li> <li> <p>Minor changes:</p> <ul> <li>Added a CSS class to the HTML tag of the currently selected language of <a href="../documentation/tag/langbar.html">Tag::Langbar</a> (requested by Damien Robert)</li> <li>Removed dependency on facets</li> <li>All deprecated methods have been removed</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>Fixed atom feed template to produce completely valid feeds</li> <li>Fixed order of feed entries (now sorted from most recent to oldest) (reported by Tuomo Valkonen)</li> <li>Fixed error in <code>SourceHandler::Virtual</code> when creating virtual directories (reported by Tuomo Valkonen)</li> <li>Fixed bug in <code>ContentProcessor::Blocks</code>: <code>context.dest_node</code> was not correctly set when <code>#render_block</code> was called via the context object</li> <li>Fixed bug in <code>Sourcehandler::Main</code>: an error was raised when the configuration option <code>output.do_deletion</code> was set to <code>true</code> (reported by Thomas Deselaers)</li> <li>Fixed RF#27075: Typo in webgen documentation (reported by Luis Parravicini)</li> <li>Fixed bug which occured when archive-tar-minitar was not installed</li> <li>Fixed CSS bug with sub directories in style bundle ‘andreas07’ (reported by Thomas Deselaers)</li> <li>Fixed a bug with path patterns not matching correctly (reported by Damien Robert)</li> <li>Fixed bug in <code>ContentProcessor::Tags</code> with regard to parsing strings/files with a multi-byte encoding under Ruby 1.9 (reported by Stefano Crocco)</li> <li>Fixed bug in terminal size detection (webgen CLI now works in Emacs shell buffer) (reported by Bob Dobbs)</li> </ul> </li> </ul> webgen 0.5.10 released http://webgen.rubyforge.org/news/release_0_5_10.html 2009-08-10T08:45:00+02:00 2009-08-10T08:45:00+02:00 <p>This is just a small bug fix release. The only change feature wise was the addition of a content processor for checking XML (XHTML) files for validness.</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Minor enhancements:</p> <ul> <li>Added content processor <a href="../documentation/contentprocessor/xmllint.html"><code>xmllint</code></a> for checking an XML (XHTML) file for well-formedness and validness</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li><code>Tag::TikZ</code>: the generated image tags now always have an <code>alt</code> attribute</li> <li>Fixed problem with the webgui when creating a new website</li> <li>Fixed problem with matching directory nodes (reported by Hermann Schichl)</li> <li>Fixed bug RF#26885: paths with dots in the extension and without a language part were handled incorrectly (reported by John Lockman)</li> <li>Fixed bug RF#26890: detecting unused paths did not always work correctly (reported by John Lockman)</li> <li>Fixed problem with handling paths of the form <code>NUMBER.REST</code> (e.g. <code>1340.png</code>): the number part is now considered the basename and the rest is the extension</li> </ul> </li> </ul> webgen 0.5.9 released http://webgen.rubyforge.org/news/release_0_5_9.html 2009-07-25T08:10:00+02:00 2009-07-25T08:10:00+02:00 <p>This release does not bring many new and cool features (some naturally made it into this release ;-) but it is another step to bringing more advanced functionality like image gallery and blog support to webgen. Since gallery and blog template files will rely heavily on embedded Ruby scripts via erb, haml and thelike, the functionality of the <code>context</code> object has been expanded to allow the programmatic inclusion of tags and the rendering of blocks.</p> <p>Another important change in this release is that the naming convention for paths has been made stricter sothat it is easier to derive the (a)(l)cn from a source path.</p> <p>Also note that there have been some incompatible API changes!</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Major enhancements:</p> <ul> <li> <p>webgen tags can now be accessed and used via the <code>context</code> object provided by some content processors (<a href="../documentation/contentprocessor/builder.html">builder</a>, <a href="../documentation/contentprocessor/erb.html">erb</a>, <a href="../documentation/contentprocessor/erubis.html">erubis</a>, and <a href="../documentation/contentprocessor/haml.html">haml</a>).</p> <blockquote class="information"> <p>Tag handlers that do not use the <code>Webgen::Tag::Base</code> module now need to provide one more method - see the <a href="../documentation/rdoc/Webgen/Tag/Base.html">API documentation</a>!</p> </blockquote> </li> <li> <p>Likewise, blocks can now be rendered via the <code>context</code> object in the same way as can be done via the <a href="../documentation/contentprocessor/blocks.html"><code>blocks</code> content processor</a>.</p> </li> <li> <p>Change in source path naming convention: only files have different parts now (sort information, basename, extension), directories and fragments not - see <a href="../documentation/manual.html#source-naming">Source Paths Naming Convention</a>! Also note that directories now always have a trailing slash (source paths and canonical names)!</p> <blockquote class="warning"> <p>This change may lead to unexpected behaviour if you used the sort information part or an extension in your directory names! Check this before upgrading to this version!</p> </blockquote> </li> <li> <p>There is the new notion of <em>passive sources</em> which do not actively create nodes from paths but only on-demand when a to-be-resolved path is not found. This is, for example, very useful for shipping default files that can easily be overridden with custom files by putting the custom files under the to-be-resolve path in a normal source directory.</p> </li> <li> <p>There is now a better system for error reporting which allows for more detailed and more specific (with path name and approximate line number) error reports.</p> </li> </ul> </li> <li> <p>Minor enhancements:</p> <ul> <li>Added new content processor <a href="../documentation/contentprocessor/head.html"><code>head</code></a> for inserting CSS/JS fragments and links into the head section of an HTML file. Arbitrary <code>meta</code> tags can also be inserted.</li> <li>Added new content processor <a href="../documentation/contentprocessor/tidy.html"><code>tidy</code></a> for running tidy over a (most often generated) HTML file (requested by Michael Franzl).</li> <li>Special characters like German umlauts and spaces are now allowed in paths (suggested by Michael Franzl). However, note that using paths with such characters may lead to problems when accessing them later on the server!</li> <li>Added new configuration option <a href="../documentation/reference_configuration.html#outputdodeletion"><code>output.do_deletion</code></a> for specifying if generated files should be deleted if their respective source is deleted (suggested by Matthias Kirschner).</li> <li>Added new configuration option <a href="../documentation/reference_configuration.html#tagcoderaycss"><code>tag.coderay.css</code></a> which allows the inclusion of external stylesheets.</li> <li>Added new meta information <a href="../documentation/reference_metainfo.html#usednodes"><code>used_nodes</code></a> for specifying dependencies for a node (suggested by Hermann Schichl).</li> <li>The feed source handler now uses the passive sources system for finding its templates and does not rely on the <code>feedtools</code> library anymore (which gives a huge speedup).</li> <li>The sitemap source handler now uses the passive sources system for finding its templates and dos not rely on the <code>builder</code> library anymore. And the format of a <code>*.sitemap</code> file is now similar to that of a <code>*.feed</code> file for consistency.</li> <li>The <code>ERB::Util</code> module is now available when using the <code>erb</code> content processor.</li> <li>Directories are not created anymore if they do not contain any files.</li> <li>There is now the distinction between textual and binary content processors.</li> <li>The leading and trailing whitespace of content blocks in Webgen Page Format is not removed anymore.</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>Fixed bug RF#25943: apply command did not work without explicitly specifying a directory</li> <li><code>Tag::Relocatable</code>: the resolved node is now additionally used as dependency for detecting a change</li> <li>Switching on <code>host_os</code> instead of <code>arch</code> for specifying Windows specific behaviour (in preparation for the change of the Windows Ruby Installer).</li> <li>Using <code>$?.exitstatus</code> instead of bit shifting to fix a JRuby issue</li> <li>webgen tag handlers are now called only if all mandatory parameters are set</li> <li>Fixed <code>Website#render</code> to work when called multiple times</li> <li>Fixed <code>Node#is_directory?</code> to also work when called on a fragment with a trailing slash</li> </ul> </li> <li> <p>Incompatible API changes:</p> <ul> <li> <p>Since one can now get at the parent node of a to-be-created node directly via the Path object, the interface for creating nodes has been simplified. The method <code>SourceHandler::Base#create_node</code> now only takes a path parameter and optionally an options hash for special cases (fragment nodes and virtual nodes), <code>SourceHandler::Base#node_exists</code> has seen a similar change.</p> <p>The <code>create_nodes</code> service signature also changed. Also note that the <code>before_node_created</code> message now only sends the path instead of parent and path.</p> <blockquote class="warning"> <p>These changes will in most cases render custom source handlers nonfunctional! Read the API documentation and have a look at the shipped source handlers!</p> </blockquote> </li> <li> <p><code>Node.absolute_name</code> has been removed since it has no purpose anymore!</p> </li> </ul> </li> <li> <p>Deprecation notes:</p> <ul> <li><code>Path#cnbase</code> and <code>Path#cnbase=</code> are now deprecated, use <code>Path#basename</code> and <code>Path#basename=</code> instead!</li> <li><code>Common.absolute_path(path, base)</code> is deprecated, use <code>Path.make_absolute(base, path)</code> instead! Note the different parameter order!</li> <li><code>Node#absolute_cn</code> and <code>Node#absolute_lcn</code> are now deprecated, use <code>Node#acn</code> and <code>Node#alcn</code> instead!</li> </ul> </li> </ul> webgen 0.5.8 released http://webgen.rubyforge.org/news/release_0_5_8.html 2009-05-07T09:40:00+02:00 2009-05-07T09:40:00+02:00 <p>This release brings some very useful new features and paves the way for more new features in the next versions!</p> <p>The most notable change is that there is no distinction between website styles and templates anymore - both are called bundles now or more specifically, for example, style bundles. Since both were basically the same but provided different kinds of content I thought that it would be useful to drop the distinction.</p> <p>This also lead to changes in the CLI command <code>create</code> which can now take any number of website bundles from which the new website will be created. Also, the <code>create</code> command got a new companion, the <code>apply</code> command which can be used to apply website bundles to an already existing website.</p> <p>But that’s not all regarding website bundles: after the addition of a new source class for handling local or remote, possibily gzipped, tar archives, it is now very easy to provide style bundles or even complete websites on websites. For example, if a user develops a new website style bundle and puts it on his website, anyone can use it by just using</p> <pre><code>webgen create -b default -b http://www.example.com/webgen/ubercool-style.tar.gz new_site </code></pre> <p>As usual, some minor enhancements, many bug fixes and many documentation updates made it into this release! See the changes section for a complete list of changes and also note that some parts of the API got deprecated!</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Major enhancements:</p> <ul> <li>Everything except feed handling (due to the dependency <code>feedtools</code> not working) is now Ruby 1.9 compatible! However, be aware that some used libraries may not work correctly under Ruby 1.9 - this is, for example, sometimes the case with Maruku!</li> <li>The distinction between website styles and website templates is no more - say welcome to website bundles!</li> <li>Added new source class which can handle local or remote (gzipped) tar archives - see <a href="../documentation/source/tararchive.html">Source::TarArchive</a></li> <li>Added new CLI command for applying a style bundle to a webgen website - see <a href="../documentation/manual.html#cli">The <code>webgen</code> command</a></li> </ul> </li> <li> <p>Minor enhancements:</p> <ul> <li>Added new value <code>current</code> for attribute <code>node</code> for webgen block content processor - see <a href="../documentation/contentprocessor/blocks.html">ContentProcessor::Blocks</a></li> <li>The CLI commands <code>apply</code> and <code>create</code> can now make use of remote website bundles due to <a href="../documentation/source/tararchive.html">Source::TarArchive</a></li> <li>Added new option <a href="../documentation/reference_configuration.html#contentprocessorredclothhardbreaks"><code>contentprocessor.redcloth.hard_breaks</code></a> for specifying if single newlines should become HTML line break tags</li> <li>The use of the environment variable <code>WEBGEN_WEBSITE</code> moved from the CLI to the main Webgen::Website class sothat it is also available when programmatically using webgen.</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li><code>Tag::Link</code>: the linked-to node is now correctly specified for partial site regeneration</li> <li>Fixed <code>Node#changed?</code> and <code>Node#meta\_info\_changed?</code>: dependent meta information nodes are now checked in <code>Node#changed?</code></li> <li><code>SourceHandler::Virtual</code>: changes in the meta information for virtual nodes are now correctly detected</li> <li><code>SourceHandler::Metainfo</code>: empty meta information files don’t throw errors anymore</li> <li><code>SourceHandler::Metainfo</code>: deleting a path/alcn from a meta information file now correctly updates the affected nodes</li> <li><code>SourceHandler::Virtual</code>/<code>SourceHandler::Page</code>: detection of deleted paths between webgen runs now works correctly and doesn’t throw error anymore (bug reported by Tim Hunter)</li> <li><code>SourceHandler::Fragment</code>: fixed bug with header tag attribute parsing</li> <li>Fixed a small CSS bug in the website bundle style-andres06</li> <li>Fixed bug in CLI: commands specified in <code>ext/init.rb</code> are now correctly recognized</li> <li><code>Webgen::Website</code>: <code>#execute_in_env</code> now correctly sets back prior website object</li> <li>Updated used versions of dependencies, rake is now a development dependency, all development dependencies now use <code>&gt;=</code> instead of just <code>=</code>. This fixes a bug with rake (reported by Chad Wooley)</li> </ul> </li> <li> <p>Documentation:</p> <ul> <li>The documentation now includes <a href="../documentation/reference_website_styles.html">previews</a> of all website style bundles</li> <li>The <a href="../documentation/reference_configuration.html">configuration option reference</a> now shows the default values for each option</li> <li>Updated installation instructions and added platform specific notes</li> <li>Added documentation for <a href="../documentation/source/filesystem.html">Source::FileSystem</a> and <a href="../documentation/source/tararchive.html">Source::TarArchive</a></li> <li>Other general user documentation updates</li> <li>Went through the whole API documentation and fixed documentation bugs and added some new documentation</li> <li>Online API documentation now uses the new RDoc template <em>darkfish</em></li> </ul> </li> <li> <p>Deprecation notes:</p> <ul> <li>The objects <code>node</code>, <code>ref_node</code>, <code>dest_node</code> and <code>website</code> are deprecated and will be removed in one of the next versions, use <code>context.node</code>, <code>context.ref_node</code>, <code>context.dest_node</code> and <code>context.website</code> instead!</li> <li><code>Node#flagged</code> is now called <code>Node#flagged?</code> - the old name will be removed in one of the next releases.</li> <li><code>Webgen::Block</code> is now named <code>Webgen::Page::Block</code> and <code>Webgen::WebgenPageFormatError</code> is now called <code>Webgen::Page::FormatError</code> - the old names will be removed in one of the next releases.</li> <li><code>Webgen::ContentProcessor::Context</code> is now named <code>Webgen::Context</code> - the old name will be removed in one of the next releases.</li> <li>All website templates have been removed, there is just one <code>default</code> website bundle instead for a default website.</li> <li>The class <code>Webgen::WebsiteManager</code> now handles bundles instead of styles and templates.</li> </ul> </li> </ul> webgen 0.5.7 released http://webgen.rubyforge.org/news/release_0_5_7.html 2009-02-27T14:56:23+01:00 2009-02-27T14:56:23+01:00 <p>Although this is a just a minor interim release, the 0.5.x series is declared stable with this release and should be used instead of the old stable 0.4.x series! The one exception is when you rely on features of the 0.4.x series that have not been ported to 0.5.x yet.</p> <p>Aside from this this release brings some new features, various issues were fixed and the homepage was updated sothat the current version and release date are visible from the start page.</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Major enhancements:</p> <ul> <li>0.5.x series declared the new stable webgen series</li> </ul> </li> <li> <p>Minor enhancements:</p> <ul> <li>Added two very useful options to <a href="../documentation/contentprocessor/blocks.html">ContentProcessor::Blocks</a></li> <li>Added one new option to <a href="../documentation/tag/langbar.html">Tag::LangBar</a></li> <li>Added <code>.ico</code> as extension that is handled by <a href="../documentation/sourcehandler/copy.html">SourceHandler::Copy</a> (suggested by Matthias Kirschner)</li> <li>Added detection of non webgen website</li> <li>Updated API and user documentation</li> <li>Current webgen version and release date visible on start date (tip from Sebastian Gassner)</li> <li>The webgen CLI now uses the environment variable <code>WEBGEN_WEBSITE</code> instead of the current directory as the location of the webgen website if the switch <code>-d</code> is not specified</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>Fixed a small bug in Common::Sitemap: directories with just an index file did not appear in the sitemap (reported by Damien Robert)</li> <li>Removed causes of Ruby code warnings</li> </ul> </li> </ul> webgen 0.5.6 released http://webgen.rubyforge.org/news/release_0_5_6.html 2008-10-20T16:16:00+02:00 2008-10-20T16:16:00+02:00 <p>The main emphasis on this release lies on a new implementation of the update tree/write tree cycle which now also allows the creation of nodes not only in the update tree phase but also in the write phase. A user visible change of this is, for example, that nodes for page fragment are now not created at page node creation time but through a content processor when the page node is written. Since menus would not be correctly generated in this situation, the update/write cycle is now executed as often as needed (which amounts to two times in nearly all situations).</p> <blockquote class="warning"> <p>Since the internal code changed a lot from the last release, you may need to update your extensions to comply with the new internal API! Have a look at the ChangeLog or the <code>git log</code> to see all changes.</p> </blockquote> <p>Building on the above changes a new webgen tag for generating high quality graphics using the LaTeX library PGF/TikZ is now available.</p> <p>The next release of webgen will concentrate on the blog support. For example, a source handler for automatically generating tag pages is in the works. Stay tuned!</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Major enhancements:</p> <ul> <li>Updated internals to allow for node creation during the write phase</li> <li>Fragment nodes are now generated by the content processor <a href="../documentation/contentprocessor/fragments.html">fragments</a></li> <li>Added new webgen tag <a href="../documentation/tag/link.html"><code>link</code></a> for generating links</li> <li>Added new webgen tag <a href="../documentation/tag/tikz.html"><code>tikz</code></a> for generating high quality graphics</li> </ul> </li> <li> <p>Minor enhancements:</p> <ul> <li>Added new option to SourceHandler::Feed for specifying the name of the block that should be rendered for the feed entry content</li> <li>Added new option to SourceHandler::Feed for specifying the RSS version that should be used</li> <li>The feed entries for SourceHandler::Feed are now ordered from newest to oldest instead of the other way around</li> <li>Added new configuration option <a href="../documentation/reference_configuration.html#taglangbarlangnames"><code>tag.langbar.lang_names</code></a></li> <li>Many documentation fixes, especially in the configuration reference</li> </ul> </li> <li> <p>Bug fixes:</p> <ul> <li>Fixed a small bug in Webgen::Page: empty block options work again now</li> <li>Fixed all bugs that occured when running the test suite with Ruby 1.9</li> </ul> </li> </ul> webgen 0.5.5 released http://webgen.rubyforge.org/news/release_0_5_5.html 2008-10-01T18:25:12+02:00 2008-10-01T18:25:12+02:00 <p>This is just a small release which fixes a bug with absolute virtual URLs. The only change feature wise was the addition of the configuration option <code>tag.menu.nested</code> which allows to generate either a nested or a sequential menu (like the horizontal menu style in webgen 0.4.x).</p> <p>If you want to live on the edge, a beta gem is now provided via Github’s gem server. To use the beta gem you need to run</p> <pre><code>gem sources -a http://gems.github.com gem install gettalong-webgen </code></pre> <p>Be aware that these beta gems are not officially supported but are normally in quite a useable state and are updated more often than the official gem for testing purposes.</p> <h3 id="changes">Changes</h3> <ul> <li> <p>Minor enhancements:</p> <ul> <li>New configuration option <a href="../documentation/reference_configuration.html#tagmenunested"><code>tag.menu.nested</code></a></li> <li>Depending on fixed gem version (using <code>=</code> instead of <code>&gt;=</code>)</li> </ul> </li> </ul> <ul> <li> <p>Bug fixes:</p> <ul> <li>RF#21349: absolute virtual URLs didn’t work correctly</li> <li>small docu fixes</li> </ul> </li> </ul>