redact exception traces and abstract getTrace
[lhc/web/wiklou.git] / RELEASE-NOTES-1.23
1 Security reminder: MediaWiki does not require PHP's register_globals. If you
2 have it on, turn it '''off''' if you can.
3
4 == MediaWiki 1.23 ==
5
6 THIS IS NOT A RELEASE YET
7
8 MediaWiki 1.23 is an alpha-quality branch and is not recommended for use in
9 production.
10
11 === Configuration changes in 1.23 ===
12
13 === New features in 1.23 ===
14 * ResourceLoader can utilize the Web Storage API to cache modules client-side.
15 Compared to the browser cache, caching in Web Storage allows ResourceLoader
16 to be more granular about evicting stale modules from the cache while
17 retaining the ability to retrieve multiple modules in a single HTTP request.
18 This capability can be enabled by setting $wgResourceLoaderStorageEnabled to
19 true. This feature is currently considered experimental and should only be
20 enabled with care.
21
22 === Bug fixes in 1.23 ===
23 * (bug 41759) The "updated since last visit" markers (on history pages, recent
24 changes and watchlist) and the talk page message indicator are now correctly
25 updated when the user is viewing old revisions of pages, instead of always
26 acting as if the latest revision was being viewed.
27
28 === API changes in 1.23 ===
29
30 === Languages updated in 1.23===
31
32 MediaWiki supports over 350 languages. Many localisations are updated
33 regularly. Below only new and removed languages are listed, as well as
34 changes to languages because of Bugzilla reports.
35
36 === Other changes in 1.23 ===
37
38 == Compatibility ==
39
40 MediaWiki 1.23 requires PHP 5.3.2 or later.
41
42 MySQL is the recommended DBMS. PostgreSQL or SQLite can also be used, but
43 support for them is somewhat less mature. There is experimental support for
44 Oracle.
45
46 The supported versions are:
47
48 * MySQL 5.0.2 or later
49 * PostgreSQL 8.3 or later
50 * SQLite 3.3.7 or later
51 * Oracle 9.0.1 or later
52
53 == Upgrading ==
54
55 1.23 has several database changes since 1.22, and will not work without schema
56 updates. Note that due to changes to some very large tables like the revision
57 table, the schema update may take quite long (minutes on a medium sized site,
58 many hours on a large site).
59
60 If upgrading from before 1.11, and you are using a wiki as a commons
61 repository, make sure that it is updated as well. Otherwise, errors may arise
62 due to database schema changes.
63
64 If upgrading from before 1.7, you may want to run refreshLinks.php to ensure
65 new database fields are filled with data.
66
67 If you are upgrading from MediaWiki 1.4.x or earlier, you should upgrade to
68 1.5 first. The upgrade script maintenance/upgrade1_5.php has been removed
69 with MediaWiki 1.21.
70
71 Don't forget to always back up your database before upgrading!
72
73 See the file UPGRADE for more detailed upgrade instructions.
74
75 For notes on 1.21.x and older releases, see HISTORY.
76
77 == Online documentation ==
78
79 Documentation for both end-users and site administrators is available on
80 MediaWiki.org, and is covered under the GNU Free Documentation License (except
81 for pages that explicitly state that their contents are in the public domain):
82
83 https://www.mediawiki.org/wiki/Documentation
84
85 == Mailing list ==
86
87 A mailing list is available for MediaWiki user support and discussion:
88
89 https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
90
91 A low-traffic announcements-only list is also available:
92
93 https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
94
95 It's highly recommended that you sign up for one of these lists if you're
96 going to run a public MediaWiki, so you can be notified of security fixes.
97
98 == IRC help ==
99
100 There's usually someone online in #mediawiki on irc.freenode.net.