Re: [Tiki-devel] A default for the list of plugins, whose bodies should be indexed

Volker Wysk <post-hhF2Jplw28UoZk/[email protected]>
Newsgroups gmane.comp.cms.tiki.devel
Message-ID <[email protected]>
Am Montag, dem 03.04.2023 um 18:16 -0400 schrieb Benoit Grégoire:
> > 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.
> 
> Please don't call it searchable, that was the name of the future
> "searchable" 
> parameter in plugin syntax params, which is NOT the same thing.  

I don't find it confusing. Anyway, what about "searchable_by_default"?

> What you seem to be talking about is a defaultindexable key in the plugin
> info 
> function, with 2 values (I suggest true and false, this is code, not
> prefs).  
> 
> If the key is not present you'd treat it as false (to avoid having to
> update 
> every single plugin).  It would also replace the need for the  
> unified_exclude_all_plugins='y'.
> 
> > - 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.
> 
> Reading the code, the current behaviour is already confusing even for 
> developers.
> 
> We have
> unified_exclude_all_plugins , with default 'y'.  It doesn't do what it's
> name 
> says.  It's essentially a unified_exclude_all_plugins_by_default.  I
> propose we 
> remove it (because it has a value on currently running servers), unless
> Victor 
> objects.
> 
> unified_included_plugins , which currently does nothing, unless 
> unified_exclude_all_plugins is true.  On people's server it likely has the
> list 
> of plugins they want indexed, so we can't really change it.  But it should
> really be renamed to unified_additional_default_indexable_plugins. It's
> only 
> used one place in the code in WikiText.php, so we can use 
> additional_default_plugins as the value name in the code)
> 
> unified_excluded_plugins, This option does what it says, it
> unconditionally 
> excludes those plugins from search.  We need this, to disable buggy
> plugins 
> whose value crashes the index.
> 
> Now, unless we go overboard with defaults, I don't think we need a 
> "unified_additional_default_not_indexable_plugins" to override the
> default.

This sure is confusing. But we don't need all this, when we introduce the
"searchable" (or "searchable_by_default") setting for the plugin info
functions. We only need two settings which override the defaults. Perhaps
call them "include_plugins" and "exclude_plugins". Or "include_in_search"
and "exclude_from_search". Or whatever.

Volker

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE6QXGh82Ov3+2nrxp+K4ydFOsHoUFAmQxc8UACgkQ+K4ydFOs
HoV+DRAAtGgTu3MR/LWKmihteem/n4gkBZMDTBAFZ/VzxiJVSDnkKQ6GqbSakqF/
r3CRQQriZtKbdc9GYmfgja8egxmXFr5olC1cwZ2rrQx5BWKDtCZiy1N7s1Y6vap0
QVcJehNEUjZqO48JcBytBBHEKJy/smugjsA5lGRpivrDysjRUWsfUje1lvm2Mk2n
xDxqyr7wqQnvHG9B7wjlGcB68P1Rv5iflNgAH4KvNLcS666UG3HmDHhBbWJznEj+
Q1e7NBruBQtaOoYxxDU+KA251d/XJI5zyiyELKLZ+jxvbzv/59a0Z1+nk/42Zi0j
hNC6Lq9OnB+d1pb7G2HWs2m5qQ+4H1sRYdn95F5M8W0tosYF8dusnrSHJ019BZcU
0EqChhv0um5ItZfBqzZIxfLoQlgwttgaprzcbocLCt4MQcoyfwXKuiA8x5T0FEk+
k1W2pcUSBad73I1IDfZ4M5mpw1D6WPRuRe8xaXuqqdazBetgi6ltUCVIz38naVnT
eJpXM5KUgOAd9HL5VBsed+mfcoHvkzYF3rLrQQf4kv/xpL+IDwZCL+Um03QMqVj/
2N023/TRPFlHlngf+lmE38JEOCUoy5BDFSTkyKfRYd3bCtAyXyUt+1Nvodq4hxYv
EGy2Bs2EpRuRAyJB377mp17rVvF6cLndVay4CKlX95D0c4GfBn8=
=o7n6
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.