Bug 8067 - HTML blocks in sysprefs should be definable for multiple languages
Summary: HTML blocks in sysprefs should be definable for multiple languages
Status: RESOLVED DUPLICATE of bug 22318
Alias: None
Product: Koha
Classification: Unclassified
Component: I18N/L10N (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-10 10:57 UTC by D Ruth Holloway
Modified: 2022-08-22 03:26 UTC (History)
8 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description D Ruth Holloway 2012-05-10 10:57:36 UTC
Blocks of HTML are used many places in the system preferences, and are injected directly onto pages at runtime.  The problem is that there is only one instance of these, which is used for all languages defined on the system. 

It would be useful to have multiple context-sensitive values for this.

See http://wiki.koha-community.org/wiki/Contextual_Preferences_RFC

This would be easily extensible to be used for languages, as well.
Comment 1 D Ruth Holloway 2013-10-20 22:31:03 UTC
In talking with Owen and Kyle about this, the best bet is probably to yank the relevant System Prefs out of the systempreferences table, and creating their own table with the identifier (same as in systempreferences), branch, language, and value, and use a cascading scheme like with circ prefs.

Then, hack getsystempreference into a new function to use the new table.

Also, we'll need an editor.  And the updatedatabase for this will need to copy existing ones into the new table, with contexts Branch * and Language *

The prefs we'll need to do this with are:
IntranetmainUserblock
IntranetNav
LibraryName
opaccredits
opacheader
OpacMainUserBlock
OpacMainUserBlockMobile
OpacNav
OpacNavBottom
OpacNavRight
OPACNoResultsFound
OPACResultsSidebar
OPACSearchForTitleIn
PatronSelfRegistrationAdditionalInstructions
Comment 2 Owen Leonard 2013-10-21 00:46:31 UTC
I think the CSS and JS ones should be included as well. For example: Use OPACUserCSS to load an alternate image which contains translated text.
Comment 3 Mark Tompsett 2016-11-23 19:17:40 UTC
Forgive me for adding you, if you didn't want to be added, folks. Just thought this notion of multilingal system preferences might be a good idea.
Comment 4 Owen Leonard 2019-04-11 13:40:11 UTC
This bug could be fixed if we build upon Bug 22318.
Comment 5 Katrin Fischer 2019-04-28 12:48:56 UTC
I am inclined to mark this duplicate of bug 2318 now. Or should we recylce for fixing the prefs listed using the new feature?
Comment 6 David Cook 2022-08-22 03:26:54 UTC

*** This bug has been marked as a duplicate of bug 22318 ***