FAQs

Troubleshooting

Jobs sit at "starting" and never progress

The background job process is not launching. Check Admin > Jobs for the job's log. Common causes are a PHP CLI path that Omeka cannot execute, or a phpcli_path containing spaces, which Omeka's PhpCli strategy does not quote. On macOS with Laravel Herd, point cli.phpcli_path at a wrapper script with no spaces in its path that execs the real binary, and set cli.execute_strategy to exec.

Video cannot be queued

ffmpeg was not found. Install it and either let the module auto-detect it or set the ffmpeg path and ffprobe path in settings. Audio still works without ffmpeg as long as the file is within the provider's upload limit.

Queueing is refused

The monthly budget would be exceeded, or the daily auto-queue cap has been reached. Raise the cap under settings, or wait for the next period. A budget of 0 is unlimited.

A stage failed with a provider error

The error is shown on the interview in the review queue. Fix the cause (an invalid API key, a model that no longer exists, a network problem) and click Retry. Processing resumes at the failed stage; earlier stages are not re-billed.

Whole passages are flagged, not single words

Expected. Whisper reports confidence for a segment of speech rather than per word, so the module flags the words of a segment together. Review the passage with play snippet and mark it reviewed.

The model list is empty

Click Refresh model list after entering the API key. The list is fetched from the provider, so it needs a valid key and network access from the server.

The player does not appear on the public page

Check, in order: the interview is published, not just saved; the site setting for media or item pages is on; the item is assigned to the site you are viewing. Themes that place the player themselves need the site setting off to avoid a second player.

Two players show on the page

The theme renders its own audio embed and JavaScript is disabled, or the theme's embed markup does not carry the media URL the module looks for. With JavaScript enabled the module hides the theme's embed for the same file.

Site search does not find the transcript

The text is written on publish to the ExtractText property. Confirm ExtractText is active and that the interview is published. If the site uses a custom search index, it must include extracttext:extracted_text.

Publishing changed other modules' records

Approving performs a partial API update on the media to set the ExtractText property, and on the item when a summary property is configured. Modules that listen for updates, such as ResourceVersioning, will record a version. This is expected.

Can I edit the summary property by hand?

Yes, but the value is replaced the next time the interview is published and removed when it is unpublished. Edit the summary on the review screen instead so it survives republishing.

Log in for Support