call for additional issues

will guaraldi <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
I'm getting ready to release PyBlosxom 1.3.1 that fixes a bunch of issues, 
specifically:

Changes between 1.3 and 1.3.1
=============================

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 ]]>


Pertinent to developers:
------------------------

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.


I've also done a lot of work on the manual pulling in information from 
other places and adding some additional markup to make it easier to find 
what you're looking for (depending on whether what you're looking for is 
something I was thinking of when making things easier to find).

If there's anything else that should be mentioned--bugs, issues, other 
ideas...--let me know as soon as possible in the next 48 hours.  Pending 
issues, I'll release PyBlosxom 1.3.1 which is primarily a bug-fix release 
on Sunday.

w00t!

/will


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.