Muut Archive Legend
@Muut · Joined 9 years ago · 18337 posts · 3878 topics · 137 reputation
Badges
Recent posts
-
Activate/Deactivate Plugins Per Page?
· 11 years ago
The plugin can offer the option to read the page header and depending on a setting, enable its functionality or not. This can be done on the onPageInitialized event, but it's a plugin decision to impl
-
Activate/Deactivate Plugins Per Page?
· 11 years ago
@zack-s To be honest it has to be implemented in the plugin. Usually out-of-the-box the enabled option is designed to disable or enable the plugin completely. In a later version it got enhanced to dis
-
Activate/Deactivate Plugins Per Page?
· 11 years ago
Regarding your last point, this can also not be the desired behaviour. Lets take for example the highlight plugin. Now on every page which does not have any code highlighted, I have to put in the head
-
Activate/Deactivate Plugins Per Page?
· 12 years ago
Well that looks correct. After this event you should have your default configuration merged with your page header configuration so for example on your page you can override the defaults with something
-
Activate/Deactivate Plugins Per Page?
· 12 years ago
I tried this: public function onPluginsInitialized() { if ($this->isAdmin()) { $this->active = false; return; } $defaults = (array) $this->config->get('plugins
-
Activate/Deactivate Plugins Per Page?
· 12 years ago
Bob, you just need to provide the logic to merge the plugin defaults that are available via the plugin .yaml and the page headers. You can see plenty of examples of this in the various plugins we h
-
Activate/Deactivate Plugins Per Page?
· 12 years ago
I've gotten a simple little plug-in working called Getter. In getter.yaml I can put enabled: true or enabled: false and the get expected behavior. But using either true or false in the page front matt
-
Language Fallback and other Issues
· 11 years ago
BTW if you think that the docs can be improved or added to, please feel free to click the link in the top right of any doc page, and submit your changes. Sometimes its hard to write docs when you dev
-
Language Fallback and other Issues
· 11 years ago
Okay, everything is very clear now. Thank you for your quick and extensive replies. Hopefully it will be useful for somebody else as well.
-
Language Fallback and other Issues
· 11 years ago
translations_fallback is only intended for translation of text strings. So that is mostly going to be used by themes with language files, or plugins. More in the docs For a page, you should follow @f