If Omeka Classic doesn't seem to be behaving correctly, for whatever reason, there are steps you can take to get more descriptive error messages. These are turned off by default, but can be used during the production of an Omeka site for troubleshooting.
Display Error Messages
You can change some configuration settings in Omeka to display error messages directly on the screen.
After enabling error messages, return to the page in Omeka that is causing the error. Do your best to repeat whatever originally caused the error, then send us the error message that is displayed on your screen. Be sure to disable these settings again once the problem is resolved.
The error display settings are different between Omeka 2.0 and older versions of Omeka:
Omeka 2.0 and newer
To turn on robust error messages, take the following steps:
- Open the
.htaccessfile in the root of your Omeka installation. If you are unable to edit in your file manager, you may need to download the file.
- Find the following line, and uncomment it (that is, remove the
#SetEnv APPLICATION_ENV development. When you are done, it should read
SetEnv APPLICATION_ENV development. If you had to download the file to edit it, be sure to upload it and replace the older version.
Note: if you cannot see the
.htaccess file, make sure that you can view hidden (dot) files in your ftp or ssh client.
If you're trying to debug a 404 ("Not Found") or 403 ("Forbidden") error, open
application/config/config.ini, and change the value of
Omeka 1.5 and older
- Open the .htaccess file in the root of your Omeka installation, and change the value of
- Open 'application/config/config.ini', and change the value of
Activate Error Logging
If you'd prefer to not have your error messages publicly displayed on your site, you can instead activate error logging. Activating error logging will log any errors encountered by Omeka to a file in
application/log directory of Omeka. You can then post to the forum or email directly to us.
- Change permissions on your installation so that the following file is writable by your server:
- Edit your
application/config/config.inifile and change the value of
- Do your best to repeat whatever originally caused the error, then send us the relevant contents of the