| Summary: | Split opac_news.lang into two distinct fields for location and language | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Josef Moravec <josef.moravec> |
| Component: | Database | Assignee: | Josef Moravec <josef.moravec> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | jonathan.druart, martin.renvoize |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 22544 | ||
| Bug Blocks: | 9081, 24346, 22663, 24220, 24221, 24223, 24224, 24766, 26801 | ||
|
Description
Josef Moravec
2021-01-16 16:32:02 UTC
Why? Can you explain a bit please? The 'lang' field now holds information about language and display location. These two string are concatenated by '_'. So data in lang field are not atomic. This leads to not very flexible design... I think Josef is right about the cleaner design and it will also make it a little nicer to add an 'all languages' like I think we really should have for the logo and such. It also makes reporting and querying on the data nicer. Shouldn't we actually implement the same behaviour and UI than for the notice templates? https://snipboard.io/Ol8fZY.jpg We would have a short list of the different block/content/news to edit, then a form with a list of the languages (vs the long ugly dropdown list we have now). It will also add the ability to have a default value. 100% agree with that approach Jonathan :) |
