Rephrased this to make it a bit shorter, more suitable for the NEWS-file IMO.
More details could better be added to the Wiki at some place/point for proper documentation (duh).
This commit is contained in:
17
docs/NEWS
17
docs/NEWS
@ -4,17 +4,14 @@
|
||||
Version 2.0-beta3 ()
|
||||
------------------------------------------------------------------------
|
||||
|
||||
* Alle frontend themes that use the pre set jquery library
|
||||
will have the jquery.noConflict-mode activated for compat reasons.
|
||||
This mode is now set deprecated and will be removed in future.
|
||||
If you (have already) set
|
||||
$serendipity['capabilities']['jquery'] = false;
|
||||
there is no need to do anything further. For the ones wanting to
|
||||
use the core set jquery lib, but do not want to rely on the
|
||||
noConflict-mode, please use (the now recommended)
|
||||
* All frontend themes that rely on the bundled Core jQuery library
|
||||
are currently using the jquery.noConflict-mode for compatibility
|
||||
to older plugins.
|
||||
This mode is now considered deprecated and will be removed in
|
||||
future releases. A new variable:
|
||||
$serendipity['capabilities']['jquery-noconflict'] = false;
|
||||
in your serendipity_config_local.inc.php or your templates
|
||||
config.inc.php file.
|
||||
in your theme's config.inc.php file can now turn of that
|
||||
noConflict-mode.
|
||||
|
||||
* Due to distinction of backend and frontend themes, each theme
|
||||
that provides a custom jquery.js now only does so for the
|
||||
|
Reference in New Issue
Block a user