Common Merengue errors

Media errors

Some front-end UI are not working (multimedia slide, inline trans, etc.)

Cause: the media for plugins/application are not copied/linked into your media root.

Solution: execute either sync_apps_media or sync_plugins_media command. For example:

$ python manage.py sync_apps_media --link
$ python manage.py sync_plugins_media --link --all

Note

The latest sync_plugins_media is not needed during development, but you have to execute it when deploy your website. See deploying Merengue.

Javascript console raises a non defined or not a function error

Example javascript error:

$("#inlinetrans-toolbar").inlinetranstoolbar is not a function

Possible cause: the media for plugins/application are not copied/linked into your media root.

Solution: execute either sync_apps_media or sync_plugins_media command. See previous error.

JS/CSS compression error

Error traceback:

Traceback (most recent call last):
...
Exception Type: TemplateSyntaxError at /
Exception Value: Caught UncompressableFileError while rendering: "/path/to/js/foofile.js" does not exist

Cause: you have enabled compression and the files to compress are not linked into media root.

Solution: one of these:

  • Disable JS/CSS compression, setting COMPRESS to False. See deploying Merengue.
  • Execute either sync_apps_media or sync_plugins_media to copy/link the media asset to media root.

Plugins errors

You cannot see all in admin the plugins installed in plugins directory

Possible cause: the plugins are not registered.

Solution: one of these:

  • Click on Detect new plugins button in the admin plugins view.
  • Define the DETECT_NEW_PLUGINS setting to True and go again admin plugins view.
  • Execute the register_new_plugins command with python manage.py register_new_plugins.

Database errors

Use a non GIS database with a GIS project

Error traceback:

Traceback (most recent call last):
...
    version_tuple = postgis_version_tuple()
File "/home/user/django_src_1.3.X/django/contrib/gis/db/backend/postgis/management.py", line 46, in postgis_version_tuple
    version = postgis_lib_version()
File "/home/user/django_src_1.3.X/django/contrib/gis/db/backend/postgis/management.py", line 26, in postgis_lib_version
    return _get_postgis_func('postgis_lib_version')
File "/home/user/django_src_1.3.X/django/contrib/gis/db/backend/postgis/management.py", line 13, in _get_postgis_func
    cursor.execute('SELECT %s()' % func)
File "/home/user/django_src_1.3.X/django/db/backends/util.py", line 19, in execute
    return self.cursor.execute(sql, params)
psycopg2.ProgrammingError: no existe la función postgis_lib_version()
LINE 1: SELECT postgis_lib_version()

Cause: you are using a non GIS database but your project is configured with USE_GIS=True

Solution: one of these:

  • Use a GIS database (it depends of your database engine).
  • Define USE_GIS=False if you don't need geographic features.
up