A. Pritschet's profile - activity

Have the exact same problem and took the liberty of taking a look at the HTML code of the page and the settings.py of the recaptcha module. I think I found the source of the error:

_RECAPTCHA_HTML = u'''
%(options)s
<script type="text/javascript"
   src="%(proto)s://www.google.com/recaptcha/api/challenge?k=%(public_key)s">
</script>
<noscript>
   <iframe src="%(proto)s://www.google.com/recaptcha/api/noscript?k=%(public_key)s"
       height="300" width="500" frameborder="0"></iframe><br>
   <textarea name="recaptcha_challenge_field" rows="3" cols="40">
   </textarea>
<input type="hidden" name="recaptcha_response_field" value="manual_challenge">
</noscript>
'''

As you can see, there are three variables options, proto and public_key supposed to be rendered into the string, but nothing is defined!

A quick and dirty solution is to replace %(public_key)s with your actual public key...

I have tried the code from the repo, but the error remains. There definitely appears to be a problem with the templates I edited in my custom_skin. As pointed out earlier I have created a new custom_skin and used unchanged templates from the default skin. Using this unmodified skin I still get the error -- with the deselected skin; there seems to be still some erroneous data in my test system's cache. Most curiously everything was working fine on my Django dev. server...

Out of curiosity, I simply copied the default theme from /usr/local/lib/python-2.x/dist-utils/bot/templates to a new folder in custom_skins, and now my system is additionally complaining about the "title_search" name...

Hi, I just made a clean new installation:

• Apache 2.2.22 on Ubuntu 12.04 64bit
• Django 1.4.5 from project page
• askbot and other dependencies via pip

I configured the site and everything was working great with the default skin. Switching to a custom skin (copy&paste of default skin and editing of templates) almost everything is working, except for the question's detail pages, e.g. /question/1/...

I get an error message saying

NoReverseMatch at /question/2/where-can-i-find-the-model-or-serial-number-of-my-device/ 
Reverse for 'AskBot.vote' with arguments '(2L,)' and keyword arguments '{}' not found.`

Commenting out the {% url %} tags I can obtain a running system again, but the following URL-names cannot be reversed using my custom skin:

• vote
• answer_to_comment

I just fiddled around with the MULTILINGUAL support. The possibility of filtering threads by language is very nice, except for the fact that I found no possibility to limit the list of possible languages. Is there an easy way to limit the number of languages in LANGUAGES_DICT? In another thread you mentioned the possibility of translating strings in jinja templates to the chosen language. Is this feature part of the github askbot-devel repo? --Thanks

Thanks for the tip. I will give it a try. Could it be a problem related to different versions of django?

The most interesting part is, that on another machine (Ubuntu 10.04, at home) installation even with an InnoDB engine is working quite well. Would you suggest to look for the error in Askbot or to have a serious talk with the network administrators at my company?

Hi there, running "./manage.py migrate" does not complete when MySQL database is used (independent of InnoDB/MyISAM) and yields the error below. Using SQLite everything is working fine.

---

Running migrations for django_authopenid: - Migrating forwards to 0005_auto__del_externallogindata.

django_authopenid:0001_initial django_authopenid:0002_make_multiple_openids_possible ! Error found during real run of migration! Aborting.

! Since you have a database that does not support running ! schema-altering statements in transactions, we have had ! to leave it in an interim state between migrations.

! You might be able to recover with: = ALTER TABLE django_authopenid_userassociation DROP COLUMN provider_name CASCADE; [] = ALTER TABLE django_authopenid_userassociation ADD CONSTRAINT django_authopenid_userassociation_user_id_uniq UNIQUE (user_id) []

! The South developers regret this has happened, and would ! like to gently persuade you to consider a slightly ! easier-to-deal-with DBMS. ! NOTE: The error which caused the migration to fail is further up. Traceback (most recent call last): File "./manage.py", line 14, in <module> execute_manager(settings) File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 438, in execute_manager utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 379, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 191, in run_from_argv self.execute(args, *options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 220, in execute output = self.handle(args, *options) File "/usr/lib/python2.7/dist-packages/south/management/commands/migrate.py", line 105, in handle ignore_ghosts = ignore_ghosts, File "/usr/lib/python2.7/dist-packages/south/migration/__init__.py", line 191, in migrate_app success = migrator.migrate_many(target, workplan, database) File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 221, in migrate_many result = migrator.__class__.migrate_many(migrator, target, migrations, database) File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 292, in migrate_many result = self.migrate(migration, database) File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 125, in migrate result = self.run(migration) File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 99, in run return self.run_migration(migration) File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 81, in run_migration migration_function() File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 57, in <lambda> return (lambda: direction(orm)) File "/home/andi/MyAskbot/askbot/deps/django_authopenid/migrations/0002_make_multiple_openids_possible.py", line 22, in forwards db.delete_unique('django_authopenid_userassociation', ['user_id']) File "/usr/lib/python2.7/dist-packages/south/db/generic.py", line 479, in delete_unique raise ValueError("Cannot find a UNIQUE constraint on table %s, columns %r" % (table_name, columns)) ValueError: Cannot find a UNIQUE constraint on table django_authopenid_userassociation, columns ['user_id']

Installed Askbot in a virtual machine. Using django's internal development server everything was working fine. Then I switched to Apache/WSGI and I end up with the exact same error.