First time here? Check out the FAQ!
0

Error at /api/title_search/ after the update to 0.7.45

It seems that I get these errors every time someone uses the New search bar

(EXTERNAL IP): Internal Server Error: /api/title_search/

... File "/srv/themegasupersite.com/node1/env/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute return self.cursor.execute(query, args)

DatabaseError: column askbot_thread.title_search_vector does not exist
LINE 1: SELECT DISTINCT (ts_rank(askbot_thread.title_search_vector, ...
                                 ^
<WSGIRequest
GET:<QueryDict: {u'query_text': [u'question'], u'_': [u'1355356141482']}>,
POST:<QueryDict: {}>,
COOKIES:{'__utma': '268136331.1476228459.1353848276.1355350963.1355353120.122',
 '__utmb': '268136331.16.10.1355353120',

Bug?

EDIT:

I get the following by using the command: python manage.py migrate But I don't really know what that means

No fixtures found.
Running migrations for django_authopenid:
- Nothing to migrate.
 - Loading initial data for django_authopenid.
No fixtures found.
Running migrations for askbot:
 ! Migration askbot:0157_auto__del_field_anonymousquestion_summary__del_field_an
onymousanswer_s should not have been applied before askbot:0157_add_title_search
_indices_for_postgresql_and_mysql but was.
Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_manager(settings)
  File "/srv/themegasupersite.come/node1/env/local/lib/python2.7/site-packages/Django-1.3
.1-py2.7.egg/django/core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/srv/themegasupersite.come/node1/env/local/lib/python2.7/site-packages/Django-1.3
.1-py2.7.egg/django/core/management/__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/srv/themegasupersite.come/node1/env/local/lib/python2.7/site-packages/Django-1.3
.1-py2.7.egg/django/core/management/base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/srv/themegasupersite.come/node1/env/local/lib/python2.7/site-packages/Django-1.3
.1-py2.7.egg/django/core/management/base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "/srv/themegasupersite.come/node1/env/local/lib/python2.7/site-packages/South-0.7.
6-py2.7.egg/south/management/commands/migrate.py", line 108, in handle
    ignore_ghosts = ignore_ghosts,
  File "/srv/themegasupersite.come/node1/env/local/lib/python2.7/site-packages/South-0.7.
6-py2.7.egg/south/migration/__init__.py", line 207, in migrate_app
    raise exceptions.InconsistentMigrationHistory(problems)
south.exceptions.InconsistentMigrationHistory: Inconsistent migration history
The following options are available:
    --merge: will just attempt the migration ignoring any potential dependency c
onflicts.

Edit 2 (After Update to 0.7.46):

I still get Error emails everytime a user searches on my askbot

I get the following by using the command: python manage.py migrate

Running migrations for longerusername:
- Nothing to migrate.
 - Loading initial data for longerusername.
No fixtures found.
Running migrations for django_authopenid:
- Nothing to migrate.
 - Loading initial data for django_authopenid.
No fixtures found.
Running migrations for askbot:
 - Migrating forwards to 0158_add_title_search_indices_for_postgresql_and_mysql.
 > askbot:0158_add_title_search_indices_for_postgresql_and_mysql
Error in migration: askbot:0158_add_title_search_indices_for_postgresql_and_mysq
l
Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_manager(settings)
  File "/srv/themegasupersite.com/node1/env/local/lib/python2.7/site-packages/Django-1.3
.1-py2.7.egg/django/core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/srv/themegasupersite.com/node1/env/local/lib/python2.7/site-packages/Django-1.3
.1-py2.7.egg/django/core ...
(more)
Toms's avatar
767
Toms
asked 2012-12-12 18:02:02 -0500, updated 2012-12-13 02:19:51 -0500
edit flag offensive 0 remove flag close merge delete

Comments

Maybe you did not run database migrations?

Evgeny's avatar Evgeny (2012-12-12 18:03:24 -0500) edit

Edited the question

Toms's avatar Toms (2012-12-12 18:13:29 -0500) edit

Yep, thanks I made a mistake there.

Evgeny's avatar Evgeny (2012-12-12 18:16:13 -0500) edit
add a comment see more comments

1 Answer

0

Thanks for reporting the issue. I've made a new release with the fix - 0.7.46.

Evgeny's avatar
13.2k
Evgeny
answered 2012-12-12 18:39:58 -0500
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments