montylounge / django-mingus Goto Github PK

When following the QuickStartGuide, this step:
pip install -r stable-requirements.txt

fails with error:
"No distributions matching the version for BeautifulSoup==3.0.8"

I just modified requirements.txt line to BeautifulSoup>=3.0.8 and it installed successfully.

In the base.html template on line 31 the path to css/pygment.css should be css/pygments.css

All

and

Well this is an enhancement and I'll do it if i can find it! as of now no matter how you insert a picture the class is &lt div class = "post-img clearfix"> so the css style covers the width of the blog space and text cannot wrap.. I'd like to apply a different class (class="small_left" depending on the tag when the picture is inserted and the apply style with a narrow width, floated left so the text can wrap.. The current post at oswco.com shows the issue.

I may yet find the stuff, but pointers appreciated

I have complet Path in DATABASE_NAME
and i chmod 777 for test

Thu Sep 23 19:40:36 2010] [error] [client ] Traceback (most recent call last):
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/core/handlers/wsgi.py", line 245, in call
[Thu Sep 23 19:40:36 2010] [error] [client ] response = middleware_method(request, response)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/opt/env/django-mingus/django-mingus/mingus/src/django-request/request/middleware.py", line 27, in process_response
[Thu Sep 23 19:40:36 2010] [error] [client ] r.from_http_request(request, response)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/opt/env/django-mingus/django-mingus/mingus/src/django-request/request/models.py", line 65, in from_http_request
[Thu Sep 23 19:40:36 2010] [error] [client ] self.save()
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/base.py", line 411, in save
[Thu Sep 23 19:40:36 2010] [error] [client ] self.save_base(force_insert=force_insert, force_update=force_update)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/base.py", line 496, in save_base
[Thu Sep 23 19:40:36 2010] [error] [client ] result = manager._insert(values, return_id=update_pk)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/manager.py", line 177, in _insert
[Thu Sep 23 19:40:36 2010] [error] [client ] return insert_query(self.model, values, **kwargs)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/query.py", line 1087, in insert_query
[Thu Sep 23 19:40:36 2010] [error] [client ] return query.execute_sql(return_id)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/sql/subqueries.py", line 320, in execute_sql
[Thu Sep 23 19:40:36 2010] [error] [client ] cursor = super(InsertQuery, self).execute_sql(None)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/sql/query.py", line 2369, in execute_sql
[Thu Sep 23 19:40:36 2010] [error] [client ] cursor.execute(sql, params)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/backends/util.py", line 19, in execute
[Thu Sep 23 19:40:36 2010] [error] [client ] return self.cursor.execute(sql, params)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/backends/sqlite3/base.py", line 193, in execute
[Thu Sep 23 19:40:36 2010] [error] [client ] return Database.Cursor.execute(self, query, params)
[Thu Sep 23 19:40:36 2010] [error] [client ] OperationalError: unable to open database file

Hi!

I'm looking for a django-based blog for which I'd be able to remotely post (in reST) from Emacs.

Byteflow (http://byteflow.su/) can do it, so I wonder what do you think about it for Mingus?

Sincerely,
Gour

Another item I've been trying to track down is some errors from the error log
when something hits my site requesting items from too far back I get a Django Debug error page rather than the nice page does not exist that you have in the normal flow, I have all debug set to false.. and this is the only condition that gives me the problem example: http://oswco.org/2009/jul/31/

other errors/ not founds work fine.. Again I'm looking and if I find I'll report back but pointers appreciated.

If the post to Twitter fails when making a blog post you get an error in basic/blog/signals.py the second to last line. The current line is "urllib2 import HttpError" but it should be "urllib2 import HTTPError".

I've tweaked quite a bit with Mingus' default markup, making the demo content valid HTML (besides the oembed output).

There's a couple of commits you can cherry-pick if you want:

http://github.com/mikl/django-mingus/commit/a441a10f5dcb17ce4f40ed6164b6744ece358496
http://github.com/mikl/django-mingus/commit/0e7b3c26f0651531d9f8a43cb727a4633ab8bcd4

I was trying to create a mingus install on my slicehost and I kept getting the following error when running syncdb:
psycopg2.InternalError: current transaction is aborted, commands ignored until end of transaction block

I tracked it down to the commit: 2979ea3
If I reset back to commit 2f7eb8d, syncdb works fine, but the minute I step forward to the commit above, i get the transaction error.

This might help as well, the following query is showing up when I run ./manage.py syncdb in my postgres logs:

ERROR: relation "django_site" does not exist at character 78
STATEMENT: SELECT "django_site"."id", "django_site"."domain", "django_site"."name" FROM "django_site" WHERE "django_site"."id" = 1 ORDER BY "django_site"."domain" ASC

In an effort to get the Google web tools going, I placed the entire meta string <> to </> in the analytics section of admin.. it did not work... I looked to see if anything from that box on admin made it into the HTML before the and could not see anything so I simply place the string in base.html.... Is there something I'm missing? is there something else I should put in the admin box for G Analytics?

When I try to install the stable requirements, I get the following error:

> pip install -r stable-requirements.txt
Downloading/unpacking http://dist.repoze.org/PIL-1.1.6.tar.gz (from -r stable-requirements.txt (line 2))
  Downloading PIL-1.1.6.tar.gz (440Kb): 440Kb downloaded
  Running setup.py egg_info for package from http://dist.repoze.org/PIL-1.1.6.tar.gz
Downloading/unpacking http://www.aeracode.org/releases/south/south-0.6.1.tar.gz (from -r stable-requirements.txt (line 12))
  Downloading south-0.6.1.tar.gz (52Kb): 52Kb downloaded
  Running setup.py egg_info for package from http://www.aeracode.org/releases/south/south-0.6.1.tar.gz
Downloading/unpacking django-tagging==0.3 (from -r stable-requirements.txt (line 6))
  Downloading django-tagging-0.3.tar.gz
  Running setup.py egg_info for package django-tagging
Obtaining django-proxy-tip from hg+https://bitbucket.org/montylounge/django-proxy/@tip#egg=django_proxy-tip (from -r stable-requirements.txt (line 16))
  Cloning hg https://bitbucket.org/montylounge/django-proxy/ (to revision tip) to /home/scelis/sites/myblog/src/django-proxy-tip
  Running setup.py egg_info for package django-proxy-tip
Obtaining django-oembed from git+git://github.com/brosner/django-oembed.git@0b09321a6042c490534e5940083136f712da57b0#egg=django_oembed-0.1.0-py2.5-0b09321a6042c490534e5940083136f712da57b0 (from -r stable-requirements.txt (line 27))
  Cloning git://github.com/brosner/django-oembed.git (to revision 0b09321a6042c490534e5940083136f712da57b0) to /home/scelis/sites/myblog/src/django-oembed
  Running setup.py egg_info for package django-oembed
Obtaining django-contact-form-tip from hg+https://bitbucket.org/ubernostrum/django-contact-form/@tip#egg=django_contact_form-tip (from -r stable-requirements.txt (line 21))
  Cloning hg https://bitbucket.org/ubernostrum/django-contact-form/ (to revision tip) to /home/scelis/sites/myblog/src/django-contact-form-tip
  Running setup.py egg_info for package django-contact-form-tip
Obtaining django-honeypot from git+git://github.com/sunlightlabs/django-honeypot.git@825c1cd0fc99491d5f30b976f511a97b56ca9978#egg=django_honeypot-0.1.2-py2.5-825c1cd0fc99491d5f30b976f511a97b56ca9978 (from -r stable-requirements.txt (line 25))
  Cloning git://github.com/sunlightlabs/django-honeypot.git (to revision 825c1cd0fc99491d5f30b976f511a97b56ca9978) to /home/scelis/sites/myblog/src/django-honeypot
Could not find a tag or branch '825c1cd0fc99491d5f30b976f511a97b56ca9978' in repository /home/scelis/sites/myblog/src/django-honeypot
Storing complete log in ./pip-log.txt

If I run it again, the error changes to:

> pip install -r stable-requirements.txt
Downloading/unpacking http://dist.repoze.org/PIL-1.1.6.tar.gz (from -r stable-requirements.txt (line 2))
  Downloading PIL-1.1.6.tar.gz (440Kb): 440Kb downloaded
  Running setup.py egg_info for package from http://dist.repoze.org/PIL-1.1.6.tar.gz
Downloading/unpacking http://www.aeracode.org/releases/south/south-0.6.1.tar.gz (from -r stable-requirements.txt (line 12))
  Downloading south-0.6.1.tar.gz (52Kb): 52Kb downloaded
  Running setup.py egg_info for package from http://www.aeracode.org/releases/south/south-0.6.1.tar.gz
Downloading/unpacking django-tagging==0.3 (from -r stable-requirements.txt (line 6))
  Running setup.py egg_info for package django-tagging
Obtaining django-proxy-tip from hg+https://bitbucket.org/montylounge/django-proxy/@tip#egg=django_proxy-tip (from -r stable-requirements.txt (line 16))
  Updating /home/scelis/sites/myblog/src/django-proxy-tip clone (to revision tip)
  Running setup.py egg_info for package django-proxy-tip
Obtaining django-oembed from git+git://github.com/brosner/django-oembed.git@0b09321a6042c490534e5940083136f712da57b0#egg=django_oembed-0.1.0-py2.5-0b09321a6042c490534e5940083136f712da57b0 (from -r stable-requirements.txt (line 27))
Command git symbolic-ref -q HEAD failed with error code 1

Any ideas? I am on Ubuntu running Git 1.6.4.4 and Python 2.6.2. I am using the standard virtualenv without the wrapper, and have indeed activated my virtual environment.

Thanks.

Was trying to set up a sub page to a parent page /Test1/testsub/
Test1 shows up fine on parent page(main page) as well as all other pages, testsub never shows up. even when configured to the navbar neither on parent nor on sub page, where I'd like it, I'm looking into it to see if I can find it! Thought I'd go ahead and note here in case some one else sees or knows..

Tagging a blog post with a tag with a space in its name produces the tag correctly and tags the blog post with the given tag, which also shows correctly on the blog's detail view. Clicking that tag, however, produces a 404 (Not Found) page because the regex doesn't match any slug with a space in it.

Replacing with r'^tags/(?P.*)/$' solves this problem on my local instance, and should be safe given there's no other usage of the "tags/" namespace in the public view.

Perhaps this behavior is by design (although if it is I think its misguided), but instead of tag_detail returning proxy objects based on their direct association with the tag name in the URL, it searches the "tags" field, instead of doing a relationship based query.

For instance, you have two tags: django-minugs and mingus. Going to http://[site]/tags/django-mingus results in the correct findset. Going to http://[site]/tags/mingus returns both the objects tagged mingus and the objects tagged django-mingus.

My blog is a technical blog and I often post code snippets. Sadly, django-mingus currently strips all extraneous whitespace from blog posts. I have investigated this issue and have narrowed it down to the render_inlines filter in django-basic-apps.

In src/django-basic-apps/basic/inlines/parser.py, the inlines function makes use of the BeautifulStoneSoup class. This class sets PRESERVE_WHITESPACE_TAGS to an empty list while the BeautifulSoup class sets it to contain both the pre and textarea tags.

Sure enough, if I edit the BeautifulSoup code to set pre as a PRESERVE_WHITESPACE_TAG for BeautifulStoneSoup, everything works perfectly and my whitespace is no longer stripped.

So it appears to me that there are a few possible solutions:

1. Do not use the render_inlines filter in mingus templates.
2. Modify django-basic-apps to use a custom BeautifulSoup parser that extends BeautifulStoneSoup but sets PRESERVE_WHITESPACE_TAGS to something that makes sense for mingus.
3. Patch BeautifulSoup to allow developers to set custom PRESERVE_WHITESPACE_TAGS for each instance of the BeautifulStoneSoup parser.

What are your thoughts on this whole situation? I can very easily do (1) for my personal mingus install, but it would be nice to fix this for all mingus users.

Hiya!

Will McGugan writes in http://www.willmcgugan.com/blog/tech/2009/3/14/the-low-down-on-django-techblog/ post: "I want to blog on a variety of subjects, but because some of the things I post about (namely the geeky stuff) are only of interest to a select few, I risk turning away visitors who aren't interested in those techy posts. Categories and tags are one solution to this, but I prefer to have a number of blogs under an umbrella blog, each with its own posts, templates and tags. In Techblog, there is also a concept of a channel which appears exactly like a blog from the front-end, but aggregates posts & tags from one or more blogs. In this site, the home-page at / is actually a channel consisting of /blog/tech/ and /blog/personal."

I'm curious if something like that can be done in Mingus?

Sincerely,
Gour

So far Django-Slimmer hasn't introduced anything but great results.

ಠ_ಠ

'slimmer.middleware.CompressHtmlMiddleware' removes whitespaces from between tags, effectively removing all whitespaces in pygmentized code blocks.

Everyone knows what a blog looks like. The most interesting thing would be to peruse the admin on a working site.

Mingus seems like a great project. However, it is packaged as a monolithic project, and is not terribly easy to integrate into other projects. Possible to make mingus itself be reusable?

Hello,

I just read http://blog.montylounge.com/2009/sep/24/apps-that-power-django-mingus/ post and under the Django-Markup section it is written "Out of the box Mingus supports (via basic-blog) raw html, markdown, and textile."

Does it mean that there is no reST support in Mingus?

Sincerely,
Gour

p.s. I prefer Mingus over Byteflow hoping xmlrpc will somehow arrive, but reST is 'must'. :-)

The doc refers to version 0.4 of pip (due to a bug in 0.5 that got fixed by the pip-guys). After talking to jezdez (http://github.com/jezdez) pip is now included in virtualenv and it is not needed to install it manually.

Worked fine for me w/o installing pip to the virtualenv. Please double check though ;-)

I've temporarily removed the Related Posts bit from the post detail page because it was returning posts that were not published yet.

Just as a note for anyone trying to install, delete the line in the requirements file and install manually. from git hub. Just working on upgrading my install from.7 to the upgrade to .97

(myblog)hzg@debian:~/work/myblog/django-mingus/mingus$ ./manage.py runserver
Validating models...
0 errors found

Django version 1.1.1, using settings 'mingus.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
/home/hzg/.virtualenvs/myblog/lib/python2.5/site-packages/pygments/plugin.py:39: UserWarning: Module simplejson was already imported from /home/hzg/.virtualenvs/myblog/src/python-twitter/simplejson/init.pyc, but /home/hzg/.virtualenvs/myblog/lib/python2.5/site-packages is being added to sys.path
import pkg_resources

When I visited http://localhost:8000/,
It can not continue to run the following step. Why?

but visiting http://localhost:8000/admin/, it works, and it is very nice.

error: package directory 'mingus/templatetags' does not exist

Looks like this was moved into core but the setup.py was not updated. Just wanted to let you know of the error I got.

Love Mingus!

I'm sure this has everything to do with me and nothing to do with mingus but here's my current trouble.

when I hit the "pip install -r stable-requirements.tx" step I'm getting a failure that ends with

_imaging.c: In function ‘DL_EXPORT’:

_imaging.c:3250: error: expected declaration specifiers before ‘init_imaging’

_imaging.c:3281: error: expected ‘{’ at end of input

error: command 'gcc' failed with exit status 1

Command /home/pshields/.virtualenvs/mingus/bin/python -c "import setuptools; file='/home/pshields/.virtualenvs/mingus/build/PIL/setup.py'; execfile('/home/pshields/.virtualenvs/mingus/build/PIL/setup.py')" install --single-version-externally-managed --record /tmp/pip-o6QuZ8-record/install-record.txt --install-headers /home/pshields/.virtualenvs/mingus/lib/include failed with error code 1
Storing complete log in ./pip-log.txt

Sorry to keep bombarding your issue queue, but basic-apps doesn't have an issue queue, so here goes:

On line 16 of basic.blog.views:

    page_size = getattr(settings,'BLOG_PAGESIZE', paginate_by),

The trailing comma here causes Python to return a one-item tuple (yes, that confused me at first), which then causes a TypeError in django/core/paginator.py in _get_num_pages (line 64).

So a quick fix would be to remove the comma, then everything seems to work as expected :)

Hi,

I am trying to install mingus on my windows box and am facing the same issue as the poster who created issue 36. Here are the steps I have followed:

cd virtualenvs

virtualenv myblog --no-site-packages

myblog\Scripts\activate.bat

cd myblog

git clone git://github.com/montylounge/django-mingus.git

cd django-mingus/mingus

pip install -r stable-requirements.txt

At this point, I got a number of exceptions which I solved by performing the following changes:

(1) Open stable-requirements.txt and change BeautifulSoup>=3.0.8 into BeautifulSoup>=3.0.8.1
(2) Open myblog\src\django-flatblocks\MANIFEST.in and remove the last / in the recursive line
(3) Open myblog\src\django-navbar\MANIFEST.in and remove the last / in the recursive lines

mv local_settings.py.template local_settings.py

manage.py syncdb

which throws the "ImportError: No module named django_proxy.signals" error

I am copying the trace for both the 'pip' and the 'manage.py syncdb' commands

Thanks for your help.

Fargaud

Trace of 'pip' command

(mingus-blog) C:\virtualenvs\mingus-blog\django-mingus\mingus>pip install -r stable-requirements.txt
warning: Not importing directory 'C:\virtualenvs\mingus-blog\django-mingus\mingus\locale': missing init.py
Obtaining django-slimmer from git+git://github.com/hbussell/django-slimmer.git@61deecdbc7650664c2a23f36ed806c043c70d65e#egg=django_slimmer-0.0.1-py2.5-dev (from -r stable-requirements.txt (line 29))
Updating c:\virtualenvs\mingus-blog\src\django-slimmer clone (to 61deecdbc7650664c2a23f36ed806c043c70d65e)
Running setup.py egg_info for package django-slimmer
Obtaining django-view-cache-utils-tip from hg+https://bitbucket.org/kmike/django-view-cache-utils/@4408ad8f1751ee2fccb441d2a342c4ed710467a0#egg=django_view_cache_utils-tip (from -r stable-requirements.txt (line 34))
Updating c:\virtualenvs\mingus-blog\src\django-view-cache-utils-tip clone (torevision 4408ad8f1751ee2fccb441d2a342c4ed710467a0)
Running setup.py egg_info for package django-view-cache-utils-tip
Downloading/unpacking django-tagging==0.3 (from -r stable-requirements.txt (line 6))
Downloading django-tagging-0.3.zip
Running setup.py egg_info for package django-tagging
Obtaining django-twitter from git+git://github.com/skevy/django-twitter.git@887a017e0436b5e03aab96e5ba650696ab2d9b58#egg=django_twitter-0.1-py2.5-dev (from -r stable-requirements.txt (line 33))
Updating c:\virtualenvs\mingus-blog\src\django-twitter clone (to 887a017e0436b5e03aab96e5ba650696ab2d9b58)
Running setup.py egg_info for package django-twitter
Obtaining django-tinymce-trunk-py2.5 from svn+http://django-tinymce.googlecode.com/svn/trunk@96#egg=django_tinymce-trunk-py2.5-dev_r96 (from -r stable-requirements.txt (line 32))
Updating c:\virtualenvs\mingus-blog\src\django-tinymce-trunk-py2.5 checkout (to revision 96)
At revision 96.
Running setup.py egg_info for package django-tinymce-trunk-py2.5
Obtaining django-oembed from git+git://github.com/brosner/django-oembed.git@0b09321a6042c490534e5940083136f712da57b0#egg=django_oembed-0.1.0-py2.5-dev (from -r stable-requirements.txt (line 26))
Updating c:\virtualenvs\mingus-blog\src\django-oembed clone (to 0b09321a6042c490534e5940083136f712da57b0)
Running setup.py egg_info for package django-oembed
Obtaining django-contact-form-tip from hg+https://bitbucket.org/ubernostrum/django-contact-form/@1d3791fa4dfbb2375ba0d27e62283380c0ec74e6#egg=django_contact_form-tip (from -r stable-requirements.txt (line 20))
Updating c:\virtualenvs\mingus-blog\src\django-contact-form-tip clone (to revision 1d3791fa4dfbb2375ba0d27e62283380c0ec74e6)
Running setup.py egg_info for package django-contact-form-tip
Obtaining django-honeypot from git+git://github.com/sunlightlabs/django-honeypot.git@76f57f487f68825fb302269516bb2b3284b81801#egg=django_honeypot-0.2.1-py2.5-dev (from -r stable-requirements.txt (line 24))
Updating c:\virtualenvs\mingus-blog\src\django-honeypot clone (to 76f57f487f68825fb302269516bb2b3284b81801)
Running setup.py egg_info for package django-honeypot
Requirement already satisfied (use --upgrade to upgrade): django-robots==0.6.1 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt(line 11))
Obtaining django-bitly-tip from hg+http://bitbucket.org/discovery/django-bitly/@6c6b6fe662cbe48325b902775fcf1eaacfd08181#egg=django_bitly-tip (from -r stable-requirements.txt (line 18))
Updating c:\virtualenvs\mingus-blog\src\django-bitly-tip clone (to revision 6c6b6fe662cbe48325b902775fcf1eaacfd08181)
Running setup.py egg_info for package django-bitly-tip
Requirement already satisfied (use --upgrade to upgrade): textile==2.1.3 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 10))
Requirement already satisfied (use --upgrade to upgrade): PIL in c:\python25\lib\site-packages\pil (from -r stable-requirements.txt (line 2))
Obtaining django-proxy from git+git://github.com/montylounge/django-proxy.git@37f5e24c4426aeec6fc20473d1213fafb6e5c489#egg=django_proxy-0.1.0-py2.5-dev (from -r stable-requirements.txt (line 27))
Updating c:\virtualenvs\mingus-blog\src\django-proxy clone (to 37f5e24c4426aeec6fc20473d1213fafb6e5c489)
Running setup.py egg_info for package django-proxy
Requirement already satisfied (use --upgrade to upgrade): django-dbtemplates==0.6.1 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 12))
Downloading/unpacking BeautifulSoup==3.0.8.1 (from -r stable-requirements.txt (line 1))
Downloading BeautifulSoup-3.0.8.1.tar.gz
Running setup.py egg_info for package BeautifulSoup
Obtaining django-disqus from git+git://github.com/montylounge/django-disqus.git@35a022f28c50b9f7cdfcdd5deb4ae6f9150f4358#egg=django_disqus-0.1-py2.5-dev (from -r stable-requirements.txt (line 22))
Updating c:\virtualenvs\mingus-blog\src\django-disqus clone (to 35a022f28c50b9f7cdfcdd5deb4ae6f9150f4358)
Running setup.py egg_info for package django-disqus
Obtaining django-cropper from git+git://github.com/montylounge/django_cropper.git@194e3c94b0abcb5ec2a9788ff1fe474779b3f67d#egg=django-cropper-0.1.5a-py2.5-dev (from -r stable-requirements.txt (line 40))
Updating c:\virtualenvs\mingus-blog\src\django-cropper clone (to 194e3c94b0abcb5ec2a9788ff1fe474779b3f67d)
Running setup.py egg_info for package django-cropper
Obtaining django-db-log from svn+http://django-db-log.googlecode.com/svn/trunk@13#egg=django_db_log-1.0.1-py2.5-dev_r13 (from -r stable-requirements.txt (line 21))
Updating c:\virtualenvs\mingus-blog\src\django-db-log checkout (to revision 13)
At revision 13.
Running setup.py egg_info for package django-db-log
Requirement already satisfied (use --upgrade to upgrade): FeedParser==4.1 in c:\python25\lib\site-packages\feedparser-4.1-py2.5.egg (from -r stable-requirements.txt (line 8))
Requirement already satisfied (use --upgrade to upgrade): django-markup==0.3 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 13))
Obtaining django-request from git+git://github.com/kylef/django-request.git@84cfef56f6eea281a9c382859fb29ef570c7295d#egg=django_request-0.21-py2.5-dev (from -r stable-requirements.txt (line 41))
Updating c:\virtualenvs\mingus-blog\src\django-request clone (to 84cfef56f6eea281a9c382859fb29ef570c7295d)
Running setup.py egg_info for package django-request
Requirement already satisfied (use --upgrade to upgrade): django-memcache-status==1.0.1 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 14))
Obtaining django-staticfiles-tip from hg+http://bitbucket.org/jezdez/django-staticfiles/@25e2c314aa665e855c4f242c374b2a27bd895542#egg=django_staticfiles-tip (from -r stable-requirements.txt (line 30))
Updating c:\virtualenvs\mingus-blog\src\django-staticfiles-tip clone (to revision 25e2c314aa665e855c4f242c374b2a27bd895542)
Running setup.py egg_info for package django-staticfiles-tip
Obtaining django-wysiwyg from git+git://github.com/pydanny/django-wysiwyg.git@b280e1b75326363dfe746d8c36425cfbed53b4ec#egg=django_wysiwyg-0.1.0-py2.5-dev (from -r stable-requirements.txt (line 35))
Updating c:\virtualenvs\mingus-blog\src\django-wysiwyg clone (to b280e1b75326363dfe746d8c36425cfbed53b4ec)
Running setup.py egg_info for package django-wysiwyg
Obtaining django-extensions from git+git://github.com/django-extensions/django-extensions.git@459276ded0edf1d1cf6d94b4865891a281445b95#egg=django_extensions-0.4.2_pre-py2.5-dev (from -r stable-requirements.txt (line 16))
Updating c:\virtualenvs\mingus-blog\src\django-extensions clone (to 459276ded0edf1d1cf6d94b4865891a281445b95)
Running setup.py egg_info for package django-extensions
Obtaining template-utils from svn+http://django-template-utils.googlecode.com/svn/trunk@109#egg=template_utils-0.4p2-py2.5-dev_r109 (from -r stable-requirements.txt (line 39))
Updating c:\virtualenvs\mingus-blog\src\template-utils checkout (to revision 109)
At revision 109.
Running setup.py egg_info for package template-utils
Requirement already satisfied (use --upgrade to upgrade): python-dateutil==1.4.1 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 3))
Obtaining sorl-thumbnail-tip from hg+https://sorl-thumbnail.googlecode.com/hg/@caf69b5206329d89282b4b8246a72e5aa77cb578#egg=sorl_thumbnail-tip (from -r stable-requirements.txt (line 38))
Updating c:\virtualenvs\mingus-blog\src\sorl-thumbnail-tip clone (to revision caf69b5206329d89282b4b8246a72e5aa77cb578)
Running setup.py egg_info for package sorl-thumbnail-tip
Obtaining django-quoteme from git+git://github.com/montylounge/django-quoteme.git@d067a0da1756867250af9d836b8e0d47ff6c7c44#egg=django_quoteme-0.2-py2.5-dev (from -r stable-requirements.txt (line 28))
Updating c:\virtualenvs\mingus-blog\src\django-quoteme clone (to d067a0da1756867250af9d836b8e0d47ff6c7c44)
Running setup.py egg_info for package django-quoteme
warning: no files found matching 'README.textile'
warning: no files found matching 'quoteme\fixtures\initial_data.json'
warning: no files found matching '*.txt' under directory 'quoteme\templates'

Downloading/unpacking Markdown==2.0.1 (from -r stable-requirements.txt (line 9))

Downloading Markdown-2.0.1.tar.gz (71Kb): 71Kb downloaded
Running setup.py egg_info for package Markdown
Obtaining django-sugar from git+git://github.com/montylounge/django-sugar.git@fad43351d848da815159837d0a5f548b1fd2ef0f#egg=django_sugar-0.2-py2.5-dev (from -r stable-requirements.txt (line 31))
Updating c:\virtualenvs\mingus-blog\src\django-sugar clone (to fad43351d848da815159837d0a5f548b1fd2ef0f)
Running setup.py egg_info for package django-sugar
Requirement already satisfied (use --upgrade to upgrade): django-debug-toolbar==0.8.1 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 5))
Obtaining django-basic-apps from git+git://github.com/montylounge/django-basic-apps.git@72ad0a50a464d3dd296a566f749e86b1f9080bac#egg=django_basic_apps-0.6-py2.5-dev (from -r stable-requirements.txt (line 17))
Updating c:\virtualenvs\mingus-blog\src\django-basic-apps clone (to 72ad0a50a464d3dd296a566f749e86b1f9080bac)
Running setup.py egg_info for package django-basic-apps
Requirement already satisfied (use --upgrade to upgrade): django==1.1.1 in c:\python25\lib\site-packages (from -r stable-requirements.txt (line 4))
Obtaining django-flatblocks from git+git://github.com/zerok/django-flatblocks.git@77c310727d5ec5a0f69cdeda2b71bea8613503f0#egg=django_flatblocks-0.3.3-py2.5-dev
(from -r stable-requirements.txt (line 23))
Updating c:\virtualenvs\mingus-blog\src\django-flatblocks clone (to 77c310727d5ec5a0f69cdeda2b71bea8613503f0)
Running setup.py egg_info for package django-flatblocks
warning: no previously-included files found matching '.gitignore'
Obtaining django-navbar from svn+http://django-navbar.googlecode.com/svn/trunk@20#egg=django_navbar-0.1.1rc1-py2.5-dev_r20 (from -r stable-requirements.txt (line 25))
Updating c:\virtualenvs\mingus-blog\src\django-navbar checkout (to revision 20)
At revision 20.
Running setup.py egg_info for package django-navbar
Obtaining python-twitter from hg+https://python-twitter.googlecode.com/hg/@7e5cb2db67352ac1fd7b40a3ec54fdef352f802f#egg=python_twitter-0.7_devel-py2.5-default (from -r stable-requirements.txt (line 37))
Updating c:\virtualenvs\mingus-blog\src\python-twitter clone (to revision 7e5cb2db67352ac1fd7b40a3ec54fdef352f802f)
Running setup.py egg_info for package python-twitter
Requirement already satisfied (use --upgrade to upgrade): Pygments==1.1.1 in c:\virtualenvs\mingus-blog\lib\site-packages (from -r stable-requirements.txt (line 7))
Obtaining django-compressor from git+git://github.com/mintchaos/django_compressor.git@7f314c513410a5be6379edf1abfc4f1730a36d09#egg=django_compressor-0.5.1-py2.5
-dev (from -r stable-requirements.txt (line 19))
Updating c:\virtualenvs\mingus-blog\src\django-compressor clone (to 7f314c513410a5be6379edf1abfc4f1730a36d09)
Running setup.py egg_info for package django-compressor
Obtaining google-analytics from git+git://github.com/montylounge/django-google-analytics.git@6b7aa6dba851dd59dca0a20bc7eefe70754384e4#egg=google_analytics-0.1-py2.5-dev (from -r stable-requirements.txt (line 36))
Updating c:\virtualenvs\mingus-blog\src\google-analytics clone (to 6b7aa6dba851dd59dca0a20bc7eefe70754384e4)
Running setup.py egg_info for package google-analytics
Requirement already satisfied (use --upgrade to upgrade): setuptools in c:\python25\lib\site-packages\setuptools-0.6c11-py2.5.egg (from django-slimmer->-r stable-requirements.txt (line 29))
Requirement already satisfied (use --upgrade to upgrade): simplejson in c:\python25\lib\site-packages\simplejson-2.0.9-py2.5.egg (from python-twitter->-r stable-requirements.txt (line 37))
Installing collected packages: BeautifulSoup, django-basic-apps, django-bitly-tip, django-compressor, django-contact-form-tip, django-cropper, django-db-log, django-disqus, django-extensions, django-flatblocks, django-honeypot, django-navbar, django-oembed, django-proxy, django-quoteme, django-request, django-slimmer,django-staticfiles-tip, django-sugar, django-tagging, django-tinymce-trunk-py2.5, django-twitter, django-view-cache-utils-tip, django-wysiwyg, google-analytics,
Markdown, python-twitter, sorl-thumbnail-tip, template-utils
Found existing installation: beautifulsoup 3.1.0.1
Not uninstalling beautifulsoup at c:\python25\lib\site-packages\beautifulsoup-3.1.0.1-py2.5.egg, outside environment C:\virtualenvs\mingus-blog
Running setup.py install for BeautifulSoup
Running setup.py develop for django-basic-apps
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-basic-apps.egg-link (link to .)
django-basic-apps 0.6 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-basic-apps

Running setup.py develop for django-bitly-tip
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-bitly.egg-link (link to .)
django-bitly 0.4 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-bitly-tip

Running setup.py develop for django-compressor
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-compressor.egg-link (link to .)
django-compressor 0.5.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-compressor

Running setup.py develop for django-contact-form-tip
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-contact-form.egg-link (link to .)
django-contact-form 0.3 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-contact-form-tip

Running setup.py develop for django-cropper
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-cropper.egg-link (link to .)
django-cropper 0.1.5a is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-cropper

Running setup.py develop for django-db-log
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-db-log.egg-link (link to .)
django-db-log 1.0.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-db-log

Running setup.py develop for django-disqus
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-disqus.egg-link (link to .)
django-disqus 0.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-disqus

Running setup.py develop for django-extensions
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-extensions.egg-link (link to .)
django-extensions 0.4.2-pre is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-extensions

Running setup.py develop for django-flatblocks
warning: no previously-included files found matching '.gitignore'
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-flatblocks.egg-link (link to .)
django-flatblocks 0.3.3 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-flatblocks

Running setup.py develop for django-honeypot
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-honeypot.egg-link (link to .)
django-honeypot 0.2.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-honeypot

Running setup.py develop for django-navbar
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-navbar.egg-link (link to .)
django-navbar 0.1.1rc1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-navbar

Running setup.py develop for django-oembed
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-oembed.egg-link (link to .)
django-oembed 0.1.0 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-oembed

Running setup.py develop for django-proxy
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-proxy.egg-link (link to .)
django-proxy 0.1.0 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-proxy

Running setup.py develop for django-quoteme
warning: no files found matching 'README.textile'
warning: no files found matching 'quoteme\fixtures\initial_data.json'
warning: no files found matching '*.txt' under directory 'quoteme\templates'

Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-quoteme.egg-link (link to .)
django-quoteme 0.2 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-quoteme

Running setup.py develop for django-request
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-request.egg-link (link to .)
django-request 0.21 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-request

Running setup.py develop for django-slimmer
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-slimmer.egg-link (link to .)
django-slimmer 0.0.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-slimmer

Running setup.py develop for django-staticfiles-tip
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-staticfiles.egg-link (link to .)
django-staticfiles 0.2.0 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-staticfiles-tip

Running setup.py develop for django-sugar
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-sugar.egg-link (link to .)
django-sugar 0.2 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-sugar

Found existing installation: django-tagging 0.3.1
Not uninstalling django-tagging at c:\python25\lib\site-packages\django_tagging-0.3.1-py2.5.egg, outside environment C:\virtualenvs\mingus-blog
Running setup.py install for django-tagging
Running setup.py develop for django-tinymce-trunk-py2.5
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-tinymce.egg-link (link to .)
django-tinymce trunk is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-tinymce-trunk-py2.5

Running setup.py develop for django-twitter
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-twitter.egg-link (link to .)
django-twitter 0.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-twitter

Running setup.py develop for django-view-cache-utils-tip
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-view-cache-utils.egg-link (link to .)
django-view-cache-utils 0.1.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-view-cache-utils-tip

Running setup.py develop for django-wysiwyg
Creating c:\virtualenvs\mingus-blog\lib\site-packages\django-wysiwyg.egg-link (link to .)
django-wysiwyg 0.1.0 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\django-wysiwyg

Running setup.py develop for google-analytics
Creating c:\virtualenvs\mingus-blog\lib\site-packages\google-analytics.egg-link (link to .)
google-analytics 0.1 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\google-analytics

Found existing installation: markdown 2.0.3
Not uninstalling markdown at c:\python25\lib\site-packages\markdown-2.0.3-py2.5-win32.egg, outside environment C:\virtualenvs\mingus-blog
Running setup.py install for Markdown
Created: C:\virtualenvs\mingus-blog\Scripts\markdown.bat
Running setup.py develop for python-twitter
Creating c:\virtualenvs\mingus-blog\lib\site-packages\python-twitter.egg-link (link to .)
python-twitter 0.7-devel is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\python-twitter

Running setup.py develop for sorl-thumbnail-tip
Creating c:\virtualenvs\mingus-blog\lib\site-packages\sorl-thumbnail.egg-link (link to .)
sorl-thumbnail 3.2.5 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\sorl-thumbnail-tip

Running setup.py develop for template-utils
Creating c:\virtualenvs\mingus-blog\lib\site-packages\template-utils.egg-link (link to .)
template-utils 0.4p2 is already the active version in easy-install.pth

Installed c:\virtualenvs\mingus-blog\src\template-utils

Successfully installed BeautifulSoup django-basic-apps django-bitly-tip django-compressor django-contact-form-tip django-cropper django-db-log django-disqus django-extensions django-flatblocks django-honeypot django-navbar django-oembed django-proxy django-quoteme django-request django-slimmer django-staticfiles-tip django-sugar django-tagging django-tinymce-trunk-py2.5 django-twitter django-view-cache-utils-tip django-wysiwyg google-analytics Markdown python-twitter sorl-thumbnail-tip template-utils
Cleaning up...

Trace of 'manage.py syncdb' command

Traceback (most recent call last):
File "C:\virtualenvs\mingus-blog\django-mingus\mingus\manage.py", line 16, in
execute_manager(settings)
File "C:\Python25\Lib\site-packages\django\core\management__init__.py", line 436, in execute_manager
setup_environ(settings_mod)
File "C:\Python25\Lib\site-packages\django\core\management__init__.py", line 419, in setup_environ
project_module = import_module(project_name)
File "C:\Python25\Lib\site-packages\django\utils\importlib.py", line 35, in import_module
import(name)
File "C:\virtualenvs\mingus-blog\django-mingus\mingus..\mingus__init__.py",line 2, in
from django_proxy.signals import proxy_save, proxy_delete
ImportError: No module named django_proxy.signals

Since manager names (that can easily contain non-ASCII characters) are input into the config file, it would be helpful to have the UTF-8 coding line that Python requires to parse those files.

# -*- coding: utf-8 -*-

I found the following problem while installing the requirements with pip.:

...
Checking out django-view-cache-utils-tip from hg+https://bitbucket.org/kmike/django-view-cache-utils/@4408ad8f1751ee2fccb441d2a342c4ed710467a0#egg=django_view_cache_utils-tip checkout from hg+https://bitbucket.org/kmike/django-view-cache-utils/@4408ad8f1751ee2fccb441d2a342c4ed710467a0#egg=django_view_cache_utils-tip (from -r stable-requirements.txt (line 34))
https://bitbucket.org/kmike/django-view-cache-utils/
Clone in ./src/django-view-cache-utils-tip exists, and has correct URL (https://bitbucket.org/kmike/django-view-cache-utils/)
Updating clone ./src/django-view-cache-utils-tip (to revision 4408ad8f1751ee2fccb441d2a342c4ed710467a0)
hg: unknown command 'fetch'
Mercurial Distributed SCM

I have complet Path in DATABASE_NAME
and i chmod 777 for test

Thu Sep 23 19:40:36 2010] [error] [client ] Traceback (most recent call last):
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/core/handlers/wsgi.py", line 245, in call
[Thu Sep 23 19:40:36 2010] [error] [client ] response = middleware_method(request, response)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/opt/env/django-mingus/django-mingus/mingus/src/django-request/request/middleware.py", line 27, in process_response
[Thu Sep 23 19:40:36 2010] [error] [client ] r.from_http_request(request, response)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/opt/env/django-mingus/django-mingus/mingus/src/django-request/request/models.py", line 65, in from_http_request
[Thu Sep 23 19:40:36 2010] [error] [client ] self.save()
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/base.py", line 411, in save
[Thu Sep 23 19:40:36 2010] [error] [client ] self.save_base(force_insert=force_insert, force_update=force_update)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/base.py", line 496, in save_base
[Thu Sep 23 19:40:36 2010] [error] [client ] result = manager._insert(values, return_id=update_pk)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/manager.py", line 177, in _insert
[Thu Sep 23 19:40:36 2010] [error] [client ] return insert_query(self.model, values, **kwargs)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/query.py", line 1087, in insert_query
[Thu Sep 23 19:40:36 2010] [error] [client ] return query.execute_sql(return_id)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/sql/subqueries.py", line 320, in execute_sql
[Thu Sep 23 19:40:36 2010] [error] [client ] cursor = super(InsertQuery, self).execute_sql(None)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/models/sql/query.py", line 2369, in execute_sql
[Thu Sep 23 19:40:36 2010] [error] [client ] cursor.execute(sql, params)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/backends/util.py", line 19, in execute
[Thu Sep 23 19:40:36 2010] [error] [client ] return self.cursor.execute(sql, params)
[Thu Sep 23 19:40:36 2010] [error] [client ] File "/usr/local/lib/python2.6/site-packages/django/db/backends/sqlite3/base.py", line 193, in execute
[Thu Sep 23 19:40:36 2010] [error] [client ] return Database.Cursor.execute(self, query, params)
[Thu Sep 23 19:40:36 2010] [error] [client ] OperationalError: unable to open database file

The current tag view uses /tags/{{ tag.name }}/ as it's URL. That works fine if all your tags live up to [-\w]+ as defined in urls.py, but does not work for tags like "Drupal 7", "#fail" or "hf&j" and a lot of other similar cases (not to mention Unicode characters), and since Django's backend does nothing to enforce these rules, you will end up with broken links or, in this case, url reversion errors.

I don't see an immediate solution to this issue. Changing django_tagging to include a slug field would be the neat solution, but getting those changes merged upstream may be a bit hard.

On my development blog I had changed my Site settings via to shorten the site name since it was messing up my layout,, could not figure out why my header was not updating when I looked at the database the site name in the blog_settings table was not changed although the site setting was,, the blog setting site name is not avail through the admin.. I am using Mysql if that might make a difference, granted most people don't change their site names often,, but it was a problem for me to figure out, I thought something weird was going on with cashing.

When editing the 'About' setting, the UI provides the following hint:

Accepts RAW html. By default, appears in right rail.

However, when RAW html is entered, this HTML is escaped on display and you can actually see all of the tags in the text of the block.

The BLOG_SETTINGS.about variable needs to be marked as safe in the base.html template. I will submit a patch to this momentarily.

I fixed a small issue with invalid blog URLs causing an internal server error. It's just a one-line change:

http://github.com/mikl/django-basic-apps/commit/e22a7393d06e00263e7d8c20096a7a909e6e8c24

Hi I don't know if I'm missing something here. I run a few Django sites but am not an expert Python developer or anything, and I'm not very familiar with virtualenv.

I followed the setup steps until this one

• ./manage.py syncdb

When I got an error.
ImportError: No module named django.core.management

Generally I look at my PythonPath for that kind of thing, but since the steps to install Mingus are so simple I thought I was missing something, or there was a missing step in the docs.

It looks as though there are two templates for displaying search results:

templates/blog/post_search.html
templates/proxy/proxy_search.html

Currently, templates/proxy/proxy_search.html is being used. However, this template is missing the following pieces of information:

1. The extended title.
2. The "Search results for:" block.
3. The "message" paragraph (not sure what this is used for).

These all exist in the other template.

I'd create a patch for you but I'm not sure which template you want fixed up. :)

I believe this is because a Settings blog instance has not been created but posting it anyway for me to follow up....

From a user:

Now i have error when i an a post

Exception Type: UnboundLocalError at /admin/blog/post/add/
Exception Value: local variable 'active_editor' referenced before assignment

Environment:

Request Method: GET
Request URL: http://domaine.com/admin/blog/post/add/
Django Version: 1.1.1
Python Version: 2.6.4
Installed Applications:
['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.admin', 'django.contrib.sitemaps', 'django.contrib.flatpages', 'django.contrib.redirects', 'django_extensions', 'tagging', 'djangodblog', 'disqus', 'basic.inlines', 'basic.blog', 'basic.bookmarks', 'basic.media', 'oembed', 'flatblocks', 'dbtemplates', 'navbar', 'sorl.thumbnail', 'template_utils', 'django_proxy', 'django_markup', 'google_analytics', 'robots', 'basic.elsewhere', 'compressor', 'contact_form', 'honeypot', 'sugar', 'quoteme', 'mingus.core', 'debug_toolbar', 'django_twitter', 'django_bitly', 'staticfiles', 'tinymce', 'django_wysiwyg', 'cropper', 'memcache_status', 'request'] Installed Middleware:
('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.middleware.doc.XViewMiddleware', 'django.contrib.redirects.middleware.RedirectFallbackMiddleware', 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware', 'slimmer.middleware.CompressHtmlMiddleware', 'sugar.middleware.debugging.UserBasedExceptionMiddleware', 'request.middleware.RequestMiddleware', 'djangodblog.DBLogMiddleware', 'debug_toolbar.middleware.DebugToolbarMiddleware')

Traceback:
File "/usr/local/lib/python2.6/site-packages/django/core/handlers/base.py" in get_response
92. response = callback(request, callback_args, *_callback_kwargs) File "/usr/local/lib/python2.6/site-packages/django/contrib/admin/options.py" in wrapper
226. return self.admin_site.admin_view(view)(args, kwargs) File "/usr/local/lib/python2.6/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
44. response = view_func(request, *args, kwargs) File "/usr/local/lib/python2.6/site-packages/django/contrib/admin/sites.py" in inner
186. return view(request, *args, *_kwargs) File "/opt/env/django-mingus/django-mingus/mingus/src/django-basic-apps/basic/blog/admin.py" in add_view
68. extra_context = { 'active_editor': active_editor }

Exception Type: UnboundLocalError at /admin/blog/post/add/
Exception Value: local variable 'active_editor' referenced before assignmen

hi,

I have fixed an issue in forked repository of django-basic-apps when you haven't an English-based locale, the month is not caught by urls.

For example for august month, the render is "aoû" in French due to an automatic translation made by django.

My fix changes the month format to numeric type.

You also need to update this portion of code in the template base.html of django-mingus:

{% cache 7200 "base.archive" %}
{% get_post_archive as dates %}
<h4>{% trans "Archive" %}</h4>
<ul class="archive">
{% for date in dates %}
<li><a href="{% url blog_archive_month date|date:"Y", date|date:"b" %}" title="{{ date|date:"F Y" }}">{{ date|date:"F Y" }}</a></li>
{% endfor %}
</ul>
{% endcache %}

to

{% cache 7200 "base.archive" %}
{% get_post_archive as dates %}
<h4>{% trans "Archive" %}</h4>
<ul class="archive">
{% for date in dates %}
<li><a href="{% url blog_archive_month date|date:"Y", date|date:"m" %}" title="{{ date|date:"F Y" }}">{{ date|date:"F Y" }}</a></li>
{% endfor %}
</ul>
{% endcache %}

Thanks again for your great work.

confirm issue exists. resolve if so.

This is already implemented in the 'blog' app, just needs to be enabled at urls.py. Patch included.

diff --git a/mingus/urls.py b/mingus/urls.py
index 2a3c82d..124fc1f 100644
--- a/mingus/urls.py
+++ b/mingus/urls.py
@@ -15,6 +15,7 @@ admin.autodiscover()
 feeds = {
     'latest': BlogPostsFeed,
     'all': AllEntries,
+    'categories': BlogPostsByCategory,
 }
 #ex: /feeds/latest/
 #ex: /feeds/categories/django/

Fixed, was local_settings config issue

I just tried setting up django-mingus both locally, and on a WebFaction instance.. when I do a syncdb, I get the following:

When viewing the RSS feed at http://blog.server.com/feeds/latest/ , all posts written in Markdown are not properly evaluated. My RSS reader simply displays all of the Markdown text on a single line.

when pip install -r, django sugar goes wrong,
license='BSD',

SyntaxError: keyword argument repeated

it turns out in django sugar, there is a duplicate license....

I find the following typo in INSTALL.textile document:

diff --git a/docs/INSTALL.textile b/docs/INSTALL.textile
index c5fce75..840c20b 100644
--- a/docs/INSTALL.textile
+++ b/docs/INSTALL.textile
@@ -14,7 +14,7 @@ It also assumes you have both subversion, mecurial, and git clients locally.

• ... wait a bit
• mv local_settings.py.template local_settings.py
• ./manage.py syncdb
  -* .manage.py loaddata test_data.json
  +* ./manage.py loaddata test_data.json
• ./manage.py runserver

I'm not sure if this bug belongs here, but since the Proxy-object for a blog post is created immediately, regardless of the blog post's state, effectively defeating the purpose of the draft-state, since all Proxy-objects are displayed on the front page.

Clicking through to the post, however, generates a 301 (permanent redirect), so while the post is not displayed, this does not seem to be the correct behavior. Either a 404 or 403 would be fine, or if you want to keep the redirect, a 302 or 307 should be used, indicating that this URL may still be used in the future :)

I follow the exact directions provided on the website provided verbatim. I have no idea what the hell is going on here.

right after I try and run ./manage.py syncdb:

Traceback (most recent call last):
File "./manage.py", line 16, in
execute_manager(settings)
File "/home/grahamg/myblog/lib/python2.5/site-packages/Django-1.1.1-py2.5.egg/django/core/management/init.py", line 360, in execute_manager
setup_environ(settings_mod)
File "/home/grahamg/myblog/lib/python2.5/site-packages/Django-1.1.1-py2.5.egg/django/core/management/init.py", line 343, in setup_environ
project_module = import_module(project_name)
File "/home/grahamg/myblog/lib/python2.5/site-packages/Django-1.1.1-py2.5.egg/django/utils/importlib.py", line 35, in import_module
import(name)
File "/home/grahamg/myblog/django-mingus/mingus/../mingus/init.py", line 2, in
from django_proxy.signals import proxy_save, proxy_delete
ImportError: No module named django_proxy.signals

I'm still on .7 but had found that certain URL's would cough up debug even though debug was set to false.. made two changes to fix, removed ##'sugar.middleware.debugging.UserBasedExceptionMiddleware', from Middleware classes which says it should only be called for a super user but in my deploy on Webfaction seemed to be causing the debug instead of nice user page to display. And moved 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware', to last item in middleware,, now 500's get the nice user error page... as to why they are not regular 404's that is a topic for more investigation.. Also removed all reference to Django debug toolbar.