PyLucid CMS Logo

blog

outdated

Currently we work on a migration to Django-CMS.
So, the most parts of this page is invalid ;)
More information: github.com/jedie/PyLucid/tree/django-cms.

tag cloud ajax | Amazon | Apache | Aptana | backward incompatible | blog | browser | bugfix | ColorMirror | creole | database | dbtemplates | development | django | django-reversion | django-sync | django-sync-server | django-tagging | django-tools | django-weave | DjangoBB | djangocms | documentation | dokumentation | Eclipse | editor | encoding | fastcgi | firefox | firefox sync | formset | generic | git | gunicorn | honypot | html | HTML dump | include | IRC | javascript | JS-SHA-Login | linux | login | mysql | nginx | pip | plugin | politik | pydev | pygments | pylucid | pypy | python | release | screencast | screencasts | security | server | sicherheit | software | sqlite | standalone | suchmaschine | svn | test | textile | unittest | v0.10 | v0.11 | virtualenv | visible changes | web | webspace

↑ Aug. 11, 2015 - PyLucid v1.6.1 **released**  #

Before 3 weeks published by jens.

Release v1.6.1 is out.

Changes:

Don't use it for a new page! Better try the v2 django-cms Branch !

Pages that used v2:

If you would like to update:

  1. create a second, fresh virtualenv
  2. change path in index.fcgi

pip freeze:

unknown type
Django==1.6.11
django-appconf==1.0.1
django-compressor==1.3
django-dbpreferences==0.5.0
django-dbtemplates==1.3
django-processinfo==0.7.1
django-reversion==1.8.7
django-reversion-compare==0.5.5
django-tagging==0.3.4
django-tools==0.29.5
feedparser==5.1.3
flup==1.0.2
mysqlclient==1.3.6
Pygments==1.6
-e git+https://github.com/jedie/PyLucid.git@0d13c35b55e6028c35486c307867f160e5336a01#egg=PyLucid-old_v1
python-creole==1.3.0
six==1.9.0
South==1.0.2
wheel==0.24.0

(Last update: Aug. 11, 2015, 1:08 p.m. by jens.)

tags development | pylucid
0 comments...

↑ Feb. 22, 2015 - setup a enhanced djangocms-blog page  #

Before 6 months, 1 week published by jens.

Destination is a blog page with one or more of the existing plugins:

  • BlogArchivePlugin
  • BlogAuthorPostsPlugin
  • BlogCategoryPlugin
  • BlogTagsPlugin

In this case you have to create a own Template, to overwrite the existing templates/djangocms_blog/base.html

In this template, add a static placeholder so you can add plugins to this.

e.g. (here a example using bootstrap):

{% extends "base.html" %}
{% load cms_tags %}

{% block meta %}
	{%  if meta %}
		{% include "meta_mixin/meta.html" %}
	{% endif %}
{% endblock meta %}

{% block content %}
<div class="row">
    <div class="col-md-3">
        {% static_placeholder "static_placeholder_blog" %}
    </div>
    <div class="col-md-9">
        {% block content_blog %}{% endblock %}
    </div>
</div>
{% endblock content %}

Then you have to:

  • create a blog AppHook-Page
  • edit the structure of this page
  • add you plugins to the Static_Placeholder_Blog

EDIT:

Since djangocms-blog pull #97 you can just select a other template (with normal place holder) in page settings !

(Last update: Feb. 23, 2015, 11:01 a.m. by jens.)

tags blog | djangocms
0 comments...

↑ Feb. 12, 2015 - PyLucid v1.6.0 **released**  #

Before 6 months, 3 weeks published by jens.

The last v1 release is out: PyLucid v1.6.0

  • Update to Django v1.6

The current package versions are:

unknown type
Django==1.6.10
django-appconf==0.6
django-compressor==1.3
django-dbpreferences==0.5.0
django-dbtemplates==1.3
django-processinfo==0.7.0
django-registration==0.8
django-reversion==1.7.1
django-reversion-compare==0.4.0
django-tagging==0.3.4
django-tools==0.28.0
feedparser==5.1.3
flup==1.0.3.dev20110405
mysqlclient==1.3.5
postmarkup==1.2.1
Pygments==1.6
-e git+https://github.com/jedie/PyLucid.git@574958d50605c3289e3f115835254b7c4f0ba9fd#egg=PyLucid-master
python-creole==1.2.1
six==1.9.0
South==0.8.4

↑ Upgrade instruction  #

Best way is to create a fresh, new virtualenv with the current bootstrap file!

You must also update your local_settingy.py and insert:

Python
1
2
3
4
5
ALLOWED_HOSTS = [
    "*", # insert you domain and remove: "*"
    # '.example.com', # Allow domain and subdomains
    # '.example.com.', # Also allow FQDN and subdomains
]

Please insert your domains there.
See also: https://docs.djangoproject.com/en/1.6/ref/settings/#allowed-hosts

↑ development  #

This will be the last v1 release. The next v2 will be use django-cms as a new base.
Current development is on django-cms branch

(Last update: Feb. 12, 2015, 2:59 p.m. by jens.)

tags backward incompatible | development | pylucid | visible changes
0 comments...

↑ March 1, 2014 - Switch the PyLucid base to a other CMS?  #

Before 1 year, 6 months published by jens.

Time is money... PyLucid CMS need more man power, more time and there is only a small contribution in the past. So everything always takes forever. Currently the django 1.6 migration...

That's why I ask me to change the base system of PyLucid with a other django based CMS? But if so, then what project?

At least the list at https://www.djangopackages.com/grids/g/cms/ looks a little long.

As a limiting criterion: The CMS should have content versioning. Would be fine if django-reversion would be used (So i can use my https://github.com/jedie/django-reversion-compare )

Seems that django-reversion used only this (big enough and under active development):

django-cms https://github.com/divio/django-cms
Feincms https://github.com/feincms/feincms

django-page-cms should also be able to versioning. But it's unclear how this is done. see: https://github.com/batiste/django-page-cms/issues/94

Discuss in our forum, here: http://www.pylucid.org/de/forum/topic/366/ (en)

(Last update: March 1, 2014, 5:15 p.m. by jens.)

tags development | pylucid
0 comments...

↑ Sept. 30, 2013 - v1.5.1: https login  #

Before 1 year, 11 months published by jens.

v1.5.1 changes:

  • Update bootstrap script
  • protect normal users via JavaScript to submit login data into honeypot
  • Add "https" option in auth db-preferences

↑ https option  #

If your side is also available via https, then you can force the usage of secure http JS-SHA-Login by changing auth db preferences:

  • Django Admin Site / Dbpreferences / Preferences / AuthPreferencesForm
  • activate the 'Https urls' checkbox

If https urls is activate, the use will be redirected if the clicked on the login link.

diff view: https://github.com/jedie/PyLucid/compare/v1.5.0...v1.5.1

(Last update: Sept. 30, 2013, 2:49 p.m. by jens.)

tags development | pylucid | visible changes
0 comments...

↑ Aug. 7, 2013 - PyLucid env mit PyPy erstellen...  #

Before 2 years published by jens.

Hier mal die Zeilen, um ein PyLucid mit PyPy zu erstellen:

Bash
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
# In diesem beispiel ist es die 32Bit Version von PyPy:
~$ wget https://bitbucket.org/pypy/pypy/downloads/pypy-2.1-linux.tar.bz2
~$ tar xfv pypy-2.1-linux.tar.bz2

# Mal testen, ob PyPy läuft:
~$ ./pypy-2.1/bin/pypy --version
Python 2.7.3 (480845e6b1dd, Jul 31 2013, 11:05:31)
[PyPy 2.1.0 with GCC 4.4.3]

# PyLucid bootstrap:
~$ wget --timestamp https://raw.github.com/jedie/PyLucid/master/bootstrap/pylucid-boot.py

# env mit PyPy erzeugen:
~$ ./pypy-2.1/bin/pypy pylucid-boot.py PyLucid_pypy_env

Dann erzeugt man eine sog. page instance, wie in der PyLucid Doku beschrieben.

Damit manage.py, index.fcgi funktionieren und den PyPy interpreter nehmen, muß man die shebang Zeile anpassen, z.B.:

Diff
1
2
-#!/usr/bin/env python
#!/home/FooBar/PyLucid_pypy_env/bin/pypy
tags pylucid | pypy | python | virtualenv
0 comments...

↑ July 25, 2013 - django 1.5 support in PyLucid  #

Before 2 years, 1 month published by jens.

We started the update process to switch from Django 1.4.x to Django 1.5.x

For the development phase we done everything in a separate branch: django1.5
github compare view:

All PyLucid own projects would also have a django1.5 branch in development phase.

We use the step to change a few things in PyLucid:

  • PluginPage urls would be inserted into the global urls.py (So plugin urls.py are usable everywhere)
  • Plugin API change a little bit: The way how request.PYLUCID would be created:
    • New @pylucid_objects decorator for plugin views the get request.PYLUCID

(Last update: July 25, 2013, 11:01 a.m. by jens.)

tags development | django | pylucid | visible changes
0 comments...

↑ July 18, 2013 - PyLucid auf Uberspace.de installieren...  #

Before 2 years, 1 month published by jens.

Es gibt nun eine Übersicht, wie man PyLucid bei Uberspace.de installieren kann:

Im Groben ist es sehr ähnlich wie in der normalen PyLucid installations Anleitung. Aber lest selber ;)

(Last update: July 18, 2013, 8:21 a.m. by jens.)

tags documentation | pylucid | webspace
0 comments...
Syndication feed format:
0 comments for 'blog':
    there exist no comment for 'blog'
Leave a comment
tag navi developing

django-processinfo: 6.4 ms of 118.5 ms (5.4%)