Back to Overview - Next protocol Software/Meeting/20181221
Summary of developer meeting at 2018-12-07
Discussions and Outcomes
- Concerting bug-1305: We'll add another line with SHA1 fingerprints. Other changes will only be done if easy to implement.
Bugtracker case#1452 is not considered critical
Some discussion about UTF-8 migration. Currently the database seems to store text in iso-8859-1 (or windows-1252). Characters not part of iso-8859-1 are stored as HTML entities ("Wałęsa" for "Wałęsa"), but displaying such characters afterwards is (sometimes?) not correct.
- Proposal: for migration all non ASCII characters should be HTML encoded. After this is done the database codepage setting can be safely changed to UTF-8. If preferred, the HTML encoding can later be reversed to UTF-8 encoding.
Irritation how includes/general.php gets included in the code. Brian solves the mystery, it a line php_value auto_prepend_file /www/includes/general.php in the www/www/.htaccess file
General agreement that this line, as well as an additional "RedirectPermanent" directive should be removed from the .htaccess file to be directly included in the code files. But there was a bit of confusion how to do it right. Topic is postponed till Brian has his configuration/startup class ready.
- Karl-Heinz will document the current status of this .htaccess magic.
Logfile of the meeting
The next meeting was proposed to be held on December 21, and then on Jan 04.
This paragraph may be modified after the meeting to document progress
- YYYY-MM-DD: Someone fixed some problem