I have create a new, seperated django project for implementing a firefox weave server in django, see:

http://code.google.com/p/django-weave/

I found the new Firefox 'weave' Addon. It would be nice if a PyLucid Plugin can be a server for "weave".

I started a plugin here: http://trac.pylucid.net/browser/PyLucidPlugins/weave/
But this is a very early developmental status :)

More information in our forum: http://forum.pylucid.org/viewtopic.php?t=313

Today i worked on some PyLucid things. Some of these:

• add a list of existing template tags from the context: http://trac.pylucid.net/changeset/2517
• I update the initial data and fix some things in the initial pages: http://trac.pylucid.net/changeset/2514
• Add a Bugfix in http://trac.pylucid.net/changeset/2516 for: PyLucid CSS doesn't load in every django admin views. work-a-round: use extrastyle instead of extrastyle, see also: http://code.djangoproject.com/ticket/12726

EDIT: I add a "tag list" link to the Django admin views, if you change a DBtemplate entry or a PageContent entry: http://trac.pylucid.net/changeset/2518

I found the IRC Webchat client from freenode and create the page IRC-Webchat. You can connect the #pylucid IRC channel direct in your Browser. Try it out...

In the past i had problem with a strange error in django-reversion middleware.

But this error does only happens if the app runs via fastCGI. And i only see it in the apache log and that's IMHO boring.

So I worked on a better error handling. I commit a new version of index.fcgi with Changeset 2504.

With Changeset 2500 i add the old HeadlineAnchorMiddleware and implement the new TOC plugin.

more information: TOC plugin documentation.

Easy insert a OpenStreetMap into the CMS page!

more information: PyLucid OpenStreetMap Plugin

With changeset:2469 the page cache would be cleaned after a model has been edited or created. (e.g. after PageTree, PageMeta or PageContent changed.)

This fixed http://trac.pylucid.net/ticket/317 and http://trac.pylucid.net/ticket/335

The Problem in ticket 335: Cleaning the cache is not only necessary so that the client sees the updates also. If a page is no longer accessable for anonymous, they should no longer be delivered from the cache.

We clean the complete page cache for one site, because we can't known witch part of the cache has been really changed. e.g. the update journal is somewhere or if the PageTree hierarchy change...

You will get some information about the cleaning if settings.DEBUG is on or you are a superuser.

You must update your environment, read: update existing PyLucid environment

You can easy setup the menu page order since changeset:2465.

Do this:

• Update PyLucid with: svn up PyLucid09/PyLucid_env/src/pylucid/pylucid_project/
• If you run fastCGI than do a reload with: touch index.fcgi

Then you have a new point "change page order" in the menu under "edit page".

It's similar to the form from v0.8

EDIT:
Here a screenshot how it works:
http://www.flickr.com/photos/jensdiemer/4152920434/

I worked today on the multiple site migration. With this you can merge existing PyLucid v0.8 installations into one v0.9 instance! The Data would be splitted by the django “sites” framework.

With Changeset 2356 you can try it. How it works explain this two pages:

• start multiple developer server
• migrate multiple sites via SQL dumps

There are some limits: Multiple user accounts can't merged :( So some of the update meta data with ForeignKey to the user object can be wrong, after migration.