omeka / omeka/plugin-ExhibitBuilder
theme_options filter isn't always triggered for exhibit themes
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 25
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Once I've saved an exhibit's theme configuration, I can no longer access the values via the theme_options filter. Omeka_Form_ThemeConfiguration::init() does call this filter via Theme::getOptions() if nothing has been saved, but Exhibit Builder never calls the filter if theme options have been loaded from the exhibits table.
Steps to reproduce
- Implement the theme_options filter in a plugin class like so:
protected $_filters = ['theme_options'];
public function filterThemeOptions($serializedOptions, $args)
{
echo 'asdf';
return $serializedOptions;
}
- Edit an exhibit, switch to another theme, and configure it.
- Notice the 'asdf' at the bottom of the page.
- Save the theme configuration form.
- Press Configure again.
Expected behavior
'asdf' should still be at the bottom of the page.
Actual behavior
'asdf' is not present.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Omeka_Form_ThemeConfiguration::init() and Theme::getOptions(), then trace how Exhibit Builder loads saved theme options from the exhibits table. Reproduce the configuration flow described in the issue and verify that theme_options is invoked both before and after saving configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100