Unspecified error when attempting to view exhibit from dshboard

When attempting to access exhibits from the dashboard by clicking on their title, I'm getting a generic error. In Firefox, the error displays as "Content Encoding Error: The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression." and in IE, I get an internal server error.

These exhibits seem to each use the same theme, though as far as I know, no changes have been made to the exhibits or themes lately. This archive runs on Omeka 1.4.2.

I know these are frustratingly vague error messages, but does anyone have any ideas as to what could be causing the issues?

Thanks,
Adam

Is this only for the exhibits? Can you access your items from the administrative dashboard?

Do you get the same errors viewing exhibits from the front end?

I'm not having any issues with the items.

I'm able to access these exhibits from the front end, though I'm noticing that with the exhibits in question, the link on the front end is going to a specific url www.example.org/exhibits/show/exhibitname/pagename, where the link from the dashboard is simply attempting to go to show/exhibitname/, and that seems to be where the issues lies. Also, I've noticed that the three exhibits that we're having issues with are three of the newest ones, which are not yet public. Perhaps this is part of the issue?

I've recently inherited management of our Omeka sites from a departed coworker, so there may be some easy detail I'm missing here.

Thanks,
Adam

That's the right path from admin to preview an exhibit.

Can you edit the exhibits from the Exhibits admin panel?

Try making them public.

Are you a super or admin user in this Omeka installation?

Sheila,

I'm set up as a super user.

I attempted to make the pages public, but that had no effect on the error. We are able to edit them from the admin panel.

I've realized that the other thing that these problem exhibits share is the theme. It appears that there's something in the theme that's causing the issue, so I'll need to look into that.

Thanks,
Adam