This release fixes some minor issues with WSGI and Paste support. It also supports template variables in the form of $(foo) which prevents variable name ambiguity. Additionally there are some bug fixes and more unit tests.

Download here:

http://sourceforge.net/project/showfiles.php?group_id=67445&package_id=65802&release_id=567698

If you have any problems, please toss a bug in the bug tracker, say hi on IRC (#pyblosxom on irc.freenode.net), or send an email to the pyblosxom-users mailing list.

/will (willhelm at users dot sourceforge dot net)

PyBlosxom 1.4.1 still had issues with WSGI, Paste and running on Python 2.5. This release fixes those issues, fixes some issues with running on Windows, and has better documentation for installation.

If you're having problems getting 1.4.1 running on Windows or Python 2.5/WSGI/Paste, I highly recommend you upgrade to 1.4.2.

Download here:

http://sourceforge.net/project/showfiles.php?group_id=67445&package_id=65802&release_id=532722

If you have any problems, please toss a bug in the bug tracker.

/will (willhelm at users dot sourceforge dot net)

p.s. I did the release on 8/16/2007, but forgot to mention it on the front page. Whoops!

PyBlosxom 1.4 had some issues with WSGI, Paste and running on Python 2.5. This release fixes those issues, has a minor optimization in Walk (Ryan removed a silly call to os.listdir), and has some updated documentation regarding installing with Paste.

If you're running 1.4, I highly recommend you upgrade to 1.4.1.

Download here:

http://sourceforge.net/project/showfiles.php?group_id=67445&package_id=65802

If you have any problems, toss a bug in the bug tracker.

/will (willhelm at users dot sourceforge dot net)

Pertinent to users:

1. Added a pyblcmd command line program for PyBlosxom command line things. This now handles static rendering, rendering a single url to stdout, testing your blog setup, ...
2. The Atom story template now has a $default_flavour bit in the link. Bug 1667937. (Thanks Michael!)
3. PyBlosxom is now locale aware in respects to dates, months, days of the week and such. Users should set the locale config property to a valid locale if they don't want English.
4. Added a ``blog_icbm`` config variable for use in the ICBM meta tag. See config_variables.txt for more information.
5. Changed the ``num_entries`` property in config.py from 40 to a much more conservative 5. Also changed the default value from 0 to 5 if you happened not to set ``num_entries`` at all. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373658 (Thanks Jon!)
6. Changed the self link in the atom feed to be of type application/atom+xml. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403008 (Thanks Brian!)
7. Added DOCUMENT_ROOT to the python path per Martin's suggestion. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367127 (Thanks Martin!)
8. Translated all documentation from Docbook to reST. reST documentation is easier to read in "source-form" and a lot easier to convert to HTML and other formats using the Python docutils tools. (Thanks John!)
9. Added support for Paste and brought the WSGI support into the codebase. (Thanks Steven and Yury!)

Pertinent to developers:

1. Lots of code clean-up, documentation, test-code, and some refactoring.
2. cb_filestat will only do an os.stat if no plugin handles the filestat. Previously, cb_filestat did an os.stat and ran through all the plugins allowing them to over-ride it.
3. Added some testing framework pieces. This requires nose. To run the tests, do::

         nosetests --verbose --include unit
         nosetests --verbose --include functional
   

Many thanks to all the people who've helped out over the last 17 months or so and the patience of our users.

/will (willhelm at users dot sourceforge dot net)

We've released version 1.3.3 of the contributed plugins pack! There are a number of additions and bug fixes since 1.3. Most focus on the comments plugins, including anti-spam plugins (Akismet and JavaScript) and AJAX support. The full list of changes is below.

You can download the new contrib pack here. If you find problems with contributed plugins, visit this page on how to contact us. "Problems" could be bugs, feature-requests, or setup issues.

-Ryan <ryanbarrett at users dot sourceforge dot net>

General

• reorganized directory structure.

pycalendar

• fixed to be locale aware and also added a config property for specifying which day to use as the first day of the week. (Thanks Martin!)

weblogsping

• fixed the plugin to handle error conditions.

comments

• handle UTF-8 encoded text correctly. (Thanks makoshark!)
• add $cmt_optionally_linked_author template variable.
• add support for sending comment email notifications via a local MTA, using the comment_mta_cmd config variable, instead of SMTP.
• add a simple new JavaScript-based anti-spam plugin, check_javascript.py.
• add the Akismet anti-spam filter, akismetcomments.py. (Thanks Mako and Blake Winton!)
• add support for AJAX comments.
• added nofollow support to $cmt_optionally_linked_author. (Thanks, Todd Warner, for the ping!)
• updated RSS template and code to support RSS feeds for comments on individual posts. An RSS feed for all comments, site-wide, is yet to come.

trackback and xmlrpc_pingback

• these are no longer subjected to comment_reject filtering plugins. a new callback, trackback_reject, has been added for filtering trackbacks. (Thanks Junji Nakanishi!)

moinmoin

• now compatible with MoinMoin 1.5 as well as 1.0. (Thanks Zarick Lau!)

editfile

• fixed to search the environment for editors. (Thanks Mako!)

rst

• fixed two bugs that prevented the plugin from working. (Thanks g2boojum!)

This is the first release of the contributed plugins pack for PyBlosxom 1.3.

Here's a list of changes between contributed plugins pack 1.2.2 and 1.3:

General

• Added release dates to CHANGELOG.txt file.
• Fixed all logging to use the new functions in PyBlosxom 1.3.

comments

• Adjusted the behavior so that comments are shown if "showcomments=yes" is in the querystring or if the pyblosxom request is for a specific blog entry (as opposed to a category with only one blog entry in it). In doing this, I moved the code from cb_pathinfo to cb_prepare. (Thanks to Matt Weber for the idea!)
• Removed the "showcomments=yes" from the comment-form html code.
• Fixes to allow the comments plugin work with Python 2.2. (Thanks Nathan!)
• Adjusted the documentation text to make it clearer that the bit about what properties each entry needs to have applies only to developers. Added __description__ and __url__ information.
• Fixed issues with rendering. Also removed the "if this is rss, then don't do stuff".
• Fixed an issue where if the config.py file doesn't have blog_encoding set, the comments plugin would die.
• Fixed a security problem where the url and author fields were not getting sanitized. (Thanks Tung Wai Yip!)
• Unfixed the url not getting sanitized--we already remove html from it and sanitize unnecessarily adds an <a href...> </a> to it.
• Re-added the logging code that the comments plugin uses when things go sour.
• Added SMTP-sanitization to the email field. (Thanks David!)
• Changed the comment reject callback so that rejection plugins can return 0 (the comment is fine), 1 (the comment is rejected) or a tuple of 1 and the error message as a string.
  
  For example:
  
  • return 0
  • return 1
  • return (1, "This comment contains a blacklisted address.")
  (Thanks Steven!)
• Changed the format of the body of the email that the comments plugin sends the blog owner to be more informational and readable. (Thanks Alec!)

pycategories

• Fixed a cosmetic issue where an extra / was getting added to the root url
• Fixed a problem where the finish template was incorrectly pulling from the category_finish config property. (Thanks Rob!)
• Fixed a problem where the totals weren't being counted correctly. (Thanks Rob!)
• Added "_urlencoded" versions of the category variables. (Thanks Petteri!)

rst entryparser

• Added two configurable options to the rst entryparser. The first sets the starting level for rendered heading elements. The second enables and disables the promotion of a lone top-level section title to the document title. (Thanks Jan-Wijbrand!)
• Fixed the rst entryparser to handle metadata. (Thanks to spanezz!)

xmlrpc_metaweblog

• Fixed _getCategories so that it returns a list of dicts rather than a list of strings. This conforms to the metaWeblogApi (http://www.xmlrpc.com/metaWeblogApi) and fixes the getCategories request. (Thanks Rob!)

If you find problems with contributed plugins, visit this page on how to contact us. "Problems" could be bugs, feature-requests, or setup issues.

Find the contributed plugin pack here (contrib.1.2.2.tar.gz).

/will (willhelm at users dot sourceforge dot net)

Pertinent to users:

1. Fixes a security issue where PATH_INFO can have multiple / at the beginning. It happens on some/many web-servers. I highly encourage you to upgrade to PyBlosxom 1.3.2 if you're using PyBlosxom 1.3 or 1.3.1. (Thanks FX!)

/will (willhelm at users dot sourceforge dot net)

Pertinent to users:

1. The "num_entries" property now affects the home page and category index pages. It no longer affects archive index pages.

2. Fixed the RSS 0.9.1 feed templates. It has the correct link url and shows the entry bodies. Thanks Norbert!

3. The version string is correct.

4. Added support for $body_escaped .

5. Fixed the blog encoding on the RSS 2.0 feed so that it uses the value provided in the config.py $blog_encoding variable.

6. Fixed the Atom 1.0 story flavour to use $body_escaped instead of <![CDATA[ $body ]]>

7. Fixed a problem with static rendering where we'd render "/index.html" and "//index.html" if the user had entries in their root category.

Pertinent to developers:

1. If you have plugins that use the logger functions in PyBlosxom 1.2, you need to update those plugins to use the new logger functions in PyBlosxom 1.3. Read through the API for details.

2. Moved documentation in ReadMeForPlugins.py over to the manual.

Also, I did a lot more work on the manual. I folded in the documentation from ReadMeForPlugins, added a lot more "markers" for examples, added a static rendering sample configuration, and folded in some material from my blog.

/will (willhelm at users dot sourceforge dot net)

Pertinent to users:

1. We added a "blog_rights" property. This holds a textual description of the rights you give to others who read your blog. Leaving this blank or not filling it in will affect the RSS 2.0 and ATOM 1.0 feeds.

2. If you set "flavourdir" in your config.py file, you have to put your flavour files in that directory tree. If you don't set "flavourdir", then PyBlosxom expects to find your flavour files in your "datadir".

   The flavour overhaul is backwards compatible with previous PyBlosxom versions. So if you want to upgrade your blog, but don't want to move your flavour files to a new directory, DON'T set your "flavourdir" property.

3. Moved the content that was in README to CHANGELOG.

4. You can now organize the directory hierarchy of your blog by date. For example, you could create a category for each year and put posts for that year in that year (2003, 2004, 2005, ...). Previously URLs requesting "2003", "2004", ... would get parsed as dates and would pull blog entries by mtime and not by category.

5. Logging works now. The following configuration properties are useful for determining whether events in PyBlosxom are logged and what will get logged:

   • "log_file" - the file that PyBlosxom events will be logged to--the web-server MUST be able to write to this file.
   • "log_level" - the level of events to write to the log. options are "critical", "error", "warning", "info", and "debug"
   • "log_filter" - the list of channels that should have messages logged. if you set the log_filter and omit "root", then app-level messages are not logged.

   It's likely you'll want to set log_file and log_level and that's it. Omit log_file and logging will fall back to stderr which usually gets logged to your web-server's error log.

Pertinent to developers and plugin developers:

Nothing that I know of. Everything should work pretty much the same.

Also, I've done a lot of work on the manual which can be found here.

Many thanks to all the people who've helped out over the last 8 months or so.

/will (willhelm at users dot sourceforge dot net)

This is the third release of the contributed plugins pack for PyBlosxom 1.2.

Here's the list of changes between contributed pack 1.2.1 and 1.2.2:

General

• New CHANGELOG.txt file which describes the changes between this version and the last as well as compatability and behavior issues.
• New README.txt file which describes what's in the contributed plugins pack, where you can find it, and various other things about the contributed plugins pack.

genericwiki

• Matej updated genericwiki so that it works as an entryparser as well as a preformatter. Will fixed up the documentation. genericwiki was moved from the preformatter directory to the entryparser directory. Thanks Matej!

pycategories

• Now has two new properites "category_start" which gets printed once before printing the category list and "category_finish" which gets printed once after printing the category list. Additionally, the default values for "category_begin" and "category_end" were fixed. This makes the default output for pycategories (x)html compliant. Thanks Joseph!

comments

• comments no longer shows comments by default! In order to view comments for a given entry, you must append "showcomments=yes" to the querystring. THIS IS NOT A BACKWARDS-COMPATIBLE CHANGE! Thanks David!
• comments no longer has documentation for the unused comments-rejected-words property.
• comments no longer requires the email field.
• all the flavour templates for the comments plugin have been updated.
• We cleaned up the comment error messages so they're useful to the user. Thanks Nathaniel!

w3cdate

• w3cdate plugin now provides $w3cdate in head and foot templates. It no longer requires PyXML. Thanks to Steven and Matej!

Thanks to Steven, David, Joseph, Matej, and Nathaniel for their contributions and help.

If you find problems with contributed plugins, visit this page on how to contact us. "Problems" could be bugs, feature-requests, or setup issues.

Find the contributed plugin pack here (contrib.1.2.2.tar.gz).

/will (willhelm at users dot sourceforge dot net)