WackoWiki: 6.0 Change Log

https://wackowiki.org/doc     Version: 29.11.2021 18:53


(25.11.2021) f7ed6cc[link1] -> M26 (Release Notes[link2])

1. Configuration

1.1. primary config

  1. changed
    1. 'db_charset' => 'utf8mb4',
    2. 'db_collation' => 'utf8mb4_unicode_520_ci',
  2. renamed
    1. database_driver -> db_driver
    2. database_host -> db_host
    3. database_port -> db_port
    4. database_databasename -> db_name
    5. database_user -> db_user
    6. database_password -> db_password
    7. database_collation -> db_collation
    8. database_charset -> db_charset
    9. database_engine -> db_engine

1.2. secondary config

  1. new 
    • upload_translit
    • source_handler
    • export_handler
    • canonical
    • base_path
    • opensearch
    • enable_counters
    • permissions_policy
    • news_structure
    • xml_sitemap_gz
  2. renamed
    • owners_can_change_categories -> categories_handler
  3. removed
    • antidupe
    • disable_tikilinks
    • outlook_workaround

1.3. constants

  1. new 
  2. removed

1.4. conf files

  1. new 
    1. permissions_policy.conf[link3]
  2. changed
    1. autoload.conf[link4]
    2. router.conf[link5]
    3. csp_custom.conf[link6]
    4. csp.conf[link7]

2. Core

2.1. Methods

This is only a random selection.

3. Database

4. Installer

5. Formatters

5.1. Wrapper

new arguments:
  1. wrapper_type="default | error | example | important | note | question | quote | success | warning"
  2. wrapper_title="Title"
  3. col=1 | 0

box  shade page text
type + +
title + +
alignment + 1 2 +
clear + +
width + 1 + 3
column + +
frame + +
automatic line feed + + +
1 This option does not make sense, because the width of the block is always equal to the width of the page.
2 Only to the left.
3 If you don't put the line feeds yourself, the block width is fixed by the engine at approximately 90% of the page width.

%%(wacko wrapper="shade" wrapper_type="note" wrapper_title="Columns" col=4) content... %%


Unicode has the explicit aim of transcending the limitations of traditional character encodings, such as those defined by the ISO 8859 standard, which find wide usage in various countries of the world but remain largely incompatible with each other. Many traditional character encodings share a common problem in that they allow bilingual computer processing (usually using Latin characters and the local script), but not multilingual computer processing (computer processing of arbitrary scripts mixed with each other).

Unicode, in intent, encodes the underlying characters—graphemes and grapheme-like units—rather than the variant glyphs (renderings) for such characters. In the case of Chinese characters, this sometimes leads to controversies over distinguishing the underlying character from its variant glyphs (see Han unification).

In text processing, Unicode takes the role of providing a unique code point—a number, not a glyph—for each character. In other words, Unicode represents a character in an abstract way and leaves the visual rendering (size, shape, font, or style) to other software, such as a web browser or word processor. This simple aim becomes complicated, however, because of concessions made by Unicode's designers in the hope of encouraging a more rapid adoption of Unicode.

A tiny part of the Unicode table

The first 256 code points were made identical to the content of ISO-8859-1 so as to make it trivial to convert existing western text. Many essentially identical characters were encoded multiple times at different code points to preserve distinctions used by legacy encodings and therefore, allow conversion from those encodings to Unicode (and back) without losing any information. For example, the "fullwidth forms" section of code points encompasses a full Latin alphabet that is separate from the main Latin alphabet section because in Chinese, Japanese, and Korean (CJK) fonts, these Latin characters are rendered at the same width as CJK characters, rather than at half the width. For other examples, see duplicate characters in Unicode.

6. Actions

7. Handlers

8. Themes

9. WikiEdit

10. Admin panel

  1. added option to create user without setting email confirm token
  2. removed transliterate module
  3. stores admin panel menu in session
  4. data synchronization: added option to reparse all pages
  5. resync: fixed broken setting of resync_limit
  6. the panel now uses the language of the user account
  7. users: added option to resend email confirmation code
  8. backup: added missing column collation to backup script

11. Translations

12. Packages


Note that the changelog is usually incomplete, for a complete list of changes that went into R6.0, you can browse the Commit log[link32], the Bug Tracker Log[link33] and ToDo[link34] list.