History log of /dokuwiki/ (Results 3601 – 3625 of 10498)
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
5f2aaab219-Nov-2014 james <j.mccann@celcat.com>

translation update

52ec63bf12-Nov-2014 christian studer <christian.studer@meteotest.ch>

Handles CTRL-Enter event to save in the editor

83b7e38d11-Nov-2014 Michael Große <mic.grosse+github@googlemail.com>

Trim unnecessary / at start of windowssharelink

fed2ee9006-Nov-2014 Gerrit Uitslag <klapinklapin@gmail.com>

Make addLogEntry independent of global var INFO

In stead use the type as provided to the function. Fixes #920

0f8f7aaa31-Oct-2014 Danny Lin <danny0838@gmail.com>

Move check after libraries are loaded, so that $conf['compression'] is not turned off in the case that gzopen doesn't exist while gzopen64 does exist, as inc/compatibility.php ought to have fixed.

731669d627-Oct-2014 Pascal Schröder <Pascal1802@gmail.com>

translation update

ae6f2c3127-Oct-2014 lioujheyu <lioujheyu@gmail.com>

translation update

17bc1e4f22-Oct-2014 Jaroslav Lichtblau <jlichtblau@seznam.cz>

translation update

fd18b5f422-Oct-2014 Gerrit Uitslag <klapinklapin@gmail.com>

visibility from private to protected for DokuCssFile

fb15cab621-Oct-2014 Gerrit Uitslag <klapinklapin@gmail.com>

use phpdocs deprecated notation

a1298aea18-Oct-2014 Aleksandr Selivanov <alexgearbox@yandex.ru>

translation update

47914fdf17-Oct-2014 Andreas Gohr <andi@splitbrain.org>

-k requires parameter. fixes #902

8838b30b17-Oct-2014 Rainer Rillke <rillke@wikipedia.de>

Accept some new gTLD e-Mail addresses

by allowing longer TLDs (up to 63 characters, which is the DN maximum: https://tools.ietf.org/html/rfc1034):
"Each node has a label, which is zero to 63 octets

Accept some new gTLD e-Mail addresses

by allowing longer TLDs (up to 63 characters, which is the DN maximum: https://tools.ietf.org/html/rfc1034):
"Each node has a label, which is zero to 63 octets in length."

For an up-to-date-length, see http://stackoverflow.com/a/22038535

show more ...

dfc5e46c15-Oct-2014 Yadav Gowda <yadav.gowda@gmail.com>

translation update

6275d90615-Oct-2014 LarsDW223 <lars_paulsen@web.de>

Ooops...forgot to commit test cases for #897.

5c5b52fd15-Oct-2014 LarsDW223 <lars_paulsen@web.de>

Fixed JavaScript compression. The compressor did not recognize a regular expression after a '&&' ot '||' operator. So it could happen that code had been cut off if the regular expression included '\/

Fixed JavaScript compression. The compressor did not recognize a regular expression after a '&&' ot '||' operator. So it could happen that code had been cut off if the regular expression included '\//' (which was treated as a single line comment because of the regular expression not being recognized). Finally fixes #897.

show more ...

001d05ed14-Oct-2014 Andreas Gohr <andi@splitbrain.org>

new PHP minimum requirement is now 5.3.3

that's the version in Debian old stable

8457f8ce14-Oct-2014 Andreas Gohr <andi@splitbrain.org>

another fix for broken gzlib linking #865

37b21a1b14-Oct-2014 Andreas Gohr <andi@splitbrain.org>

use its own cache file per versions

this ensures there will be never, ever an outdated update message shown
after upgrade.

70daee8614-Oct-2014 LarsDW223 <lars_paulsen@web.de>

Corrected compression for ++ and -- operator. Partially fixes #897.

9c03f73b13-Oct-2014 Michal Koutný <xm.koutny@gmail.com>

AUTH_USER_CHANGE handler can modify passed data

Originally AUTH_USER_CHANGE handler could modify the user data, however,
auth plugin consequently worked with different copy of the array thus
effecti

AUTH_USER_CHANGE handler can modify passed data

Originally AUTH_USER_CHANGE handler could modify the user data, however,
auth plugin consequently worked with different copy of the array thus
effectively preventing any changes by the AUTH_USER_CHANGE implementer.

show more ...

7d247a3c11-Oct-2014 Gerrit Uitslag <klapinklapin@gmail.com>

preserve comments in less if 'compress' config disabled

Otherwise comments are never visible in css.php

86c04d8711-Oct-2014 Angus Gratton <gus@projectgus.com>

Fix for update messages never completely going away

The existing logic for messages.txt requires some valid update
response (ending in %) to the messages update check before it clears
the current me

Fix for update messages never completely going away

The existing logic for messages.txt requires some valid update
response (ending in %) to the messages update check before it clears
the current messages.

However update.dokuwiki.org appears to return an empty string response
if everything is up to date. (ie http://update.dokuwiki.org/check/46.1 )

As a result if there are update messages in messages.txt they don't
automatically go away after updating to the current version. The only
time they change is when a newer release comes out. The upgrade plugin
has logic in it to force a re-download of messages.txt, but currently
this just re-downloads the old update messages.

This change explicitly allows for "" as a valid "no messages"
indicator (distinct from false, which is the HTTP error indicator.)

show more ...

b783602208-Oct-2014 Myeongjin <aranet100@gmail.com>

translation update

7172294d08-Oct-2014 Guy Brand <gb@unistra.fr>

Release preparation

1...<<141142143144145146147148149150>>...420