I traped in some problems while update ubuntu 10.04TLS to 12.04TLS.
Generally: You must allways recreate the PyLucid virtual environment, if python version changed. In this case python v2.6 to v2.7. This is needed, because many symlinks doesn't work after a version change.
# get PyLucid boot script:# First make a "backup":
/home/FooBar$ mv PyLucid_env PyLucid_env_OLD
# Get the newest boot script:
/home/FooBar$ wget --timestamp https://raw.github.com/jedie/PyLucid/master/bootstrap/pylucid-boot.py
# Create the PyLucid virtual environment:
/home/FooBar$ python pylucid-boot.py PyLucid_env
Some problems:
You must relink all external plugins.
You must install all additional dependencies.
Delete old cache entries, e.g.: $ rm /tmp/PyLucid* -rf
If you use DjangoBB you should recreate the search index, e.g.:
Also a strage error: Error importing authentication backend pylucid.system.auth_backends.SiteSHALoginAuthBackend: "No module named auth_backends"
In settings is:
If you use MySQL and hase set default-character-set and/or default-collation in /etc/mysql/my.cnf, than you will have the next problem. These settings was deprecated and doesn't be accepted with newer MySQL v5.5.x
You can leave your old CACHES settings untouched. But it's a good idea to use the new "smooth cache backends", because:
The default PyLucid settings used the SmoothLocMemCache backend. But this isn't very memory-efficient.
You can use the normal django cache backends. But PyLucid clears the cache with cache.clear() completely after e.g. a page was edited. This isn't effective with the normal backends.
It's not really backward incompatible, because no admin action is needed for update. The only backward incompatible changes are the PyLucid search API and that is only interesting for developers ;)
there exist no comment for 'blog'
loading...
Leave a comment