Re: [Tiki-devel] A default for the list of plugins, whose bodies should be indexed
Adrien Maloba <[email protected]>
| Newsgroups | gmane.comp.cms.tiki.devel |
|---|---|
| Message-ID | <CAA83xJBf_B1NKfng96JhXwk0CoLp9wmGNjM-XFTKnHCShe=m_A@mail.gmail.com> |
Hello all, I have read all the thread of the discussions. I will give here the different proposals of everybody in synthesis and give my opinion. - The first proposal is from Volker, you proposed to include a list of default plugins in the preference "Except included plugins" (unified_included_plugins); - Then there is another proposal from Rick Sapir, you proposed to add an option (searchable="y|n") in each plugin to allow flexibility (hit management system); - Volker, you proposed to add the settings "Include plugins" and "Exclude plugins" and also add a "Show defaults" button in the search panel to show activated and deactivated plugins. In the last message you sent, you went back to the idea proposed by Rick Sapir and pointed out that the "Include plugins" and "Exclude plugins" already exist in Tiki, but they are just named differently. Here is my thought: - Add an option to each plugin (searchable="y|n"). Give the value searchable="y" to all the plugins that we want to index by default. - Add another preference that we could call "Included plugins" different from "Except included plugins" (unified_included_plugins). This new preference will allow to include plugins with searchable="n" value that we want to make indexable without depending on "Exclude all plugins" preference. - Disable the preference "Exclude all plugins" by default, today this preference is enabled by default. With these three proposals, we will have : - At the beginning, a list of indexed and non-indexed plugins by default thanks to the option (searchable="y|n"). - A preference that allows to include plugins that we want to make indexable (The new preference) - A preference that allows to exclude some plugins even if they are searchable="y". This preference already exists "Excluded plugins" (unified_excluded_plugins) - A preference that allows all plugins "Exclude all plugins", if you activate it with the possibility to include some plugins with the preference "Except included plugins". Thank you! On Sat, 14 Jan 2023 at 20:39, Volker Wysk <post-hhF2Jplw28UoZk/[email protected]> wrote: > Am Freitag, dem 13.01.2023 um 13:51 -0500 schrieb Benoit Grégoire: > > On vendredi 13 janvier 2023 07 h 33 min 10 s EST Jonny Bradley via > > TikiWiki-devel wrote: > > > Hi Benoit, Volker and all > > > > > > That's some pretty impressive feature creep, i was going to just add > > > that list: > > > > Well, that's a good reason to talk about it ;) To me at least: > > > > - Even having a global "Include plugins" and "Exclude plugins" in > > preferences is kind of feature creep, because I can't see a case where > > it's the clear and logical answer to any user's need (To illustrate: when > > is the answer to "Should this be indexed" be "because it's been affected > > in some unknowable way by PluginDiv"). It's not even a list of defaults, > > it's an all-or-nothing thing! > > I've thought of that, because we already have global settings for indexing > or not indexing plugin bodies - in the "Exclude plugins" or "Except > included > plugins" search settings. > > Maybe you're right, and those settings should be abandoned altogether, in > favor of global per-plugin settings, specified in the > "wikiplugin_..._info()" functions. And in favor of an optional "searchable" > argument for all plugins. > > I don't see a good reason either, why someone would want to override those > settings, when the per-plugin defaults are reasonable. > > Volker > > _______________________________________________ > TikiWiki-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > _______________________________________________ TikiWiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel