django-blocks current state
NicoEchániz
I'm working on a project that consists of migrating a bunch of
websites from a proprietary PHP CMS to a Python/Django based solution.
I'm evaluating django-blocks as a candidate but I'm having some
trouble testing it, as the documentation is incomplete.
Looking at the websites listed as "using django blocks" I can see it's
mature enough for what I need, but some things seem to be lacking
instructions, incomplete or buggy.
Stuff I've run into so far (while using the demo project):
1) inserting an image in a textarea opens a pop-up with a filebrowser
link that points at:
http://127.0.0.1:8000/admin/filebrowser/?_popup=1&pop=1
but this URL seems invalid to the filebrowser app (it's installed and
it's urls added to the project's urls.py)
2) inserting an image in a news article works but deletion is not
working. Changing it's mode (center, topleft, etc.) has no effect
either.
3) I could find no instructions on using the blog, cart and search
apps. I've fiddled with them a bit but had only partial progress in
enabling and using them.
4) The method employed for the site structure is a bit confusing
(powerful, but confusing) :
- It let's you assign a Static page to the Root (/) URL, but the Home
overides it.
- There's no way or hint to block some menu items from "holding"
child pages. For example: feeds should be one such item, as it's URL
patterns do not allow for arbitrary descendant URLs. Root would be
another example as well as blog/ cart/ etc.
I find your method for handling translations very interesting.
My work involves replicating the very minimalistic interface of the
PHP CMS I'm migrating from, and the project will have it's own name,
but I'd like to base it on django-blocks and commit back everything
that might be useful to you while maintaining our project as a layer
on top. I hope this is ok with you.
Thanks for your work. I look forward to your replies.
--
NicoEchániz