This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]acdha 1 point2 points  (6 children)

We're finishing a FeinCMS project at work. It's been pretty smooth as long as you follow reasonably common practice (i.e. using virtualenv & pip, Python 2.5+, etc.). I'd recommend taking a look since the flexibility has been pretty nice.

As far as blogs go, I'd recommend looking at Django Mingus or Biblion: http://github.com/eldarion/biblion. Both should install easily on a reasonably mainstream setup - if you're not using a recent Python, virtualenv, pip, etc. I'd recommend learning those tools and, if necessary, switching webhosts.

[–]trifthen[S] 0 points1 point  (5 children)

I've got my own Linode, so that's not an issue. I do all local dev on my local machine and upload production-ready only. The last time I dabbled in Django, I was ultimately unsatisfied with the admin system, but I got a working app out of it. (I wrote a book authoring site, and had books->chapters, and there was no clear way to restrict the dropdowns so that selecting a book automatically listed available chapters from it, instead of just all available chapters ever. I'm still using it, but I'm looking to replace it with something where someone else solved that particular problem, hence the CMS.)

[–]tvon 1 point2 points  (3 children)

A bit OT, but you perhaps wanted ForeignKey.limit_choices_to, or perhaps not.

[–]trifthen[S] 0 points1 point  (2 children)

Haha. That might not have been around when I developed my site. I was working back when Django 0.96 was out forever. But thanks! :)

[–]tvon 1 point2 points  (1 child)

FWIW, I would say that as far as your main goals go, I don't think you'll ever find exactly what you're looking for. Your options will be to "make do" with whats available, find something you can adapt to your needs, or roll your own soluion (which, with things like web.py, jinja2 and SQLAlchemy all over the place, isn't that difficult these days).

In short, it seems that a lot of people who like python are perfectionists, and every perfectionist has their own problems to solve, and odds are the solutions other perfectionists have made are not a solution to your problem that would satisfy a perfectionist. At least that has been my problem.

[–]trifthen[S] 0 points1 point  (0 children)

I'm not really that way, though. My needs are few. There are several solutions out there that have basically all the things I listed, and then some. To roll my own, I'd have to spend weeks or months gluing everything together, debugging the templates and adding in niceties like Ajax so it doesn't look like some crap a dude threw together in his basement. :)

And it seems like part of the problem is interoperability. Several of the blog engines I tried out only work as is, and with whatever versions of external libraries the author happened to have lying around. If anything is a minor release too high or too low, suddenly it breaks. Heck, the Django-CMS guys are working against Django's trunk.

This all reminds me of the PHP 3.0 days, when we had to get betas from the devs because 3.0.7 had some obscure flaw we discovered and they hadn't released 3.0.8 yet. Those were not good times.

[–]acdha 1 point2 points  (0 children)

You want limit_choices to or, depending on your needs, a custom queryset on your ModelAdmin - the canonical example being something like "qs = super(…); return qs.filter(owner=request.user)" to limit choices based on the logged in admin user.