OPACdidyoumean has an entry in sysprefs.sql: ('OPACdidyoumean','',NULL,'Did you mean? configuration for the OPAC. Do not change, as this is controlled by /cgi-bin/koha/admin/didyoumean.pl.','Free'), You can also find it in the systempreference table: select * from systempreferences where varibale = 'OPACdidyoumean'; However, it can be be found when you search for it as a system preference. If you go to `admin/didyoumean.pl` and make changes they are logged as a change to a system preference. This is confusing.
Sorry I'm not sure I fully understand. Do you mean "admin/didyoumean.pl" does control the data saved to that system preference, but it's weird? One of those things that would probably be better off in that "configuration" table that Tomas has suggested before?
OPACdidyoumean is in the systempreferences table but it can only be accessed via the "Local use" tab. I understand that it's weird to have a Koha-standard preference in local use, but if it's hidden from searches and clearly labeled I think it's not a big deal. There's not just one: ElasticsearchIndexStatus_authorities ElasticsearchIndexStatus_biblios OPACdidyoumean UsageStatsID UsageStatsLastUpdateTime UsageStatsPublicID Version If we don't want OPACdidyoumean in system preferences we'd have to find a solution for all of these.
(In reply to Owen Leonard from comment #2) > If we don't want OPACdidyoumean in system preferences we'd have to find a > solution for all of these. Actually that gives me a thought... There are times where I'd love for sysprefs to be visible to end users but not editable by end users. Maybe we add a column to the syspref table like "read_only" or "system_only". We could show them in a named tab, but make them non-editable by end users? My original use case was setting sysprefs at a vendor level, but this use case makes sense too, no?
I think a system_only to not make them show up in the editor would make sense. They show in local use now, which is not ideal and noone will/should be ever be able to edit them. Version could be read-only... although on dev instances it's handy to be able to reset the version :)