Plugin is compatible only with Bootstrap3

[ctgraham]

Because we override frontend/components templates, this plugin is really only compatible with Bootstrap3 subthemes.

The frontend/components templates are not core to this plugin and might be considered spurrious. These should be migrated upstream to bootstrap3 as PRs or subthemes if possible.

Until such is done, we need to check in the register method to ensure Bootstrap3 is the enabled theme, and skip any practical effect if not:

inlineHtmlGalley/InlineHtmlGalleyPlugin.inc.php

Lines 24 to 26 in d10cc31

	$success = parent::register($category, $path, $mainContextId);
	if (!$success) return false;
	if ($success && $this->getEnabled()) {

Specifically, it is critical not to hook TemplateResource::getFilename if our template overrides are not going to be compatible with the selected theme.

inlineHtmlGalley/InlineHtmlGalleyPlugin.inc.php

Line 81 in d10cc31

HookRegistry::register('TemplateResource::getFilename', array($this, '_overridePluginTemplates'), HOOK_SEQUENCE_CORE);

The documentation should be clarified here:

inlineHtmlGalley/README.md

Line 10 in d10cc31

* The plugin will function with other themes, but the structure of the blocks conforms to bootstrap3 expectations

[felixhelix]

Hi @ctgraham

We had two broken journals running the default theme because this plugin was automatically enabled and does not work with this theme. It took me some time to figure out what had caused this problems.
It would be extremely helpful to at least change the plugin descriptions and the README.md to make clear that this only works with botstrap themes. Also the plugin (and folder) name suggests that it is applicable for all themes.
And the plugin should definitely not be automatically enabled.
I could offer to make a pull request for the locale files. I am not sure if and how the plugin name could or should be changed?

Yours,
Felix

[ctgraham]

Hi, @felixhelix , the filesystem name for the plugin and folder are intended for identification only, not for information, so I don't anticipate any changes there.

Please feel free to open a PR against this issue to clarify the locale files and README.

I've tagged @wopsononock here regarding the coding changes described above.