FAQs Omeka Classic plugin

Troubleshooting

I do not see Theme Files under Appearance

Only Super Users can use the editor; Admins cannot, unless a plugin adds their role (see Security Model). Check the user's role under Users, and that the plugin is active under Settings > Plugins.

Every theme is read-only

That is by design: installing a new version of a theme replaces its files and any edits made to them, so installed themes open read-only. Click Copy This Theme… to make a copy of your own and edit that, then choose the copy under Appearance > Themes. If you manage a theme's files yourself and will not update it, tick it under Settings > Editable themes instead. See Copying a Theme.

The theme I copied before reinstalling the plugin is read-only

Uninstalling deletes the plugin's list of your copies. Tick the theme under Settings > Editable themes to edit it again.

A template opens read-only with "a link to … outside the theme"

Theme Engine themes (Vitrine, Plinth, Confetti, Overprint), on sites where they are installed for development, link most of their templates to the shared Theme Engine. Saving one would change it for every theme, so it opens read-only. Copy the theme: the copy gets real files of its own. Themes installed from the hosting dashboard have real files and are not affected.

"The web server cannot write to…"

The web server user cannot write to the theme's folder or the file. Ask your host, or on your own server make the theme's folder writable by the web server user (for example chmod -R u+w themes/my-theme with the right owner). Copy Theme needs the themes folder itself to be writable. The plugin never changes permissions.

The save is refused with a syntax error I cannot see

The message gives PHP's error and the line, counted in the whole file. A parse error is often caused a few lines earlier (a missing ;, ) or endif;). If you are sure the code is right, tick Save anyway, despite the error and save. When PHP's parser accepts the code but php -l reports a compile error (such as a function declared twice), the message says Fatal error.

The public site shows an error after a save

A template with an error breaks the pages that use it, and an error in custom.php or functions.php breaks every public page. The admin still works: open the file's Revision History and roll back to the revision before the change.

A change does not show on the site

  • Check that you edited the theme the site uses (Appearance > Themes), or the theme of the exhibit you are looking at.
  • Check that the file is the one Omeka uses: on a plugin's own pages, themes/<theme>/<plugin-folder>/… wins over the theme folder; elsewhere the theme folder wins over core and plugin views. See Overriding Plugin and Core Views.
  • A stylesheet or script may be cached by the browser: reload the page without the cache.

"You can save at most 10 files a minute"

You saved more than Saves a minute in the last minute. Wait a moment, or raise the limit under Settings.

"This file is too large to open in the editor"

The file is larger than Largest file. Raise the limit under Settings (up to 10240 KB). Large minified stylesheets and scripts are best edited from their sources.

Copy to Theme is greyed out

The theme is read-only (copy it first), or every place the view could go is a link out of the theme or a folder the web server cannot write to; the box says which.

I clicked Copy to Theme and the file opened

That is the theme's new copy of the view, ready to edit. To see the original again, choose it in Show, or use Compare in the This file overrides box.

Copy Theme fails

  • There is already a theme named …: choose another folder name (theme names are compared without case).
  • A theme folder name has up to 30 letters…: use only letters, numbers, - and _.
  • The web server cannot write to the themes folder: see above.
  • The copy would be larger than 256 MB or hold more than 20000 files: the theme is too large to copy here.

When links were left out of a copy, a message lists them: they pointed outside the theme and the Omeka installation, to nothing, or to a folder holding the theme.

I cannot delete a theme copy

Delete This Copy is shown only for themes made with Copy Theme that neither the site nor an exhibit uses. Choose another public theme under Appearance > Themes, or change the exhibits' theme, first. Installed themes are never deleted here.

Where are backups, and how do I remove them?

Next to the file, as <file>.<YYYYMMDDHHMMSS>.bak, shown in italics in the tree. Open one and click Delete Backup. The revision history keeps every version anyway, so backups are rarely needed.

The revisions table is getting large

Lower Revisions per file under Settings; a file's old revisions are pruned when it is next saved. Deleting a theme copy deletes its revisions. Rows can also be deleted from theme_file_editor_revisions directly; nothing else refers to them.

Can I edit theme.ini, config.ini or images?

No. theme.ini and config.ini open read-only, since a mistake there breaks the Themes page and the theme's configuration form; Copy Theme sets a copy's title itself, and the theme's settings are changed under Configure Theme. Images and fonts cannot be opened.

Log in for Support