| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
| |
- better use of Latin terminology for DokuWiki
- ACL is not translated as AAA (Aditus Administrationis Aditus) but
with ICA (Index Custodiae Aditus), which is a more literal translation
- minor corrections of grammar and logic
- The word "namespace" is more literally translated "spatium
nominis", but according to other translations (like the Italian one),
I preferred to use "genus".
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
usage: [[paypal>email@address.com]]
|
| |
|
| |
|
| |
|
|
|
|
| |
first headings)
|
| |
|
|
|
|
|
|
| |
As suggested by Robin Getz locale .txt files can now be duplicated and
changed in the conf/lang/ directory and conf/plugin_lang/$plugin/
directory for plugins.
|
| |
|
| |
|
|
|
|
|
|
| |
This avoids disk writes when not needed and possibly also xhtml
rendering when the metadata needs to be rendered but xhtml doesn't
(unless the metadata file is changed).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The author of MaxgTar (original name of this file) wrote an incorrect
phpdoc license tag mentionning the “GPL” without a version number.
Contacted to clarify the licensing situation of this file, he explained
that he wanted to use the LGPL-2.1:
> I am the author of MaxgTar and I must say I am more than slightly
> surprised to hear about it.
> […]
> I have no doubt that my intention was to use the GNU Lesser General
> Public License, version 2.1.
|
|
|
|
|
| |
as discussed in
http://www.freelists.org/post/dokuwiki/git-changes-20101209,7
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Like ids namespaces are now preg_quoted in the acl check (and therefore
the escaping of "*" has been removed). When plugins call the ACL check
function with strange ids the regex fails otherwise (in the case of the
include plugin errors like "Warning: preg_grep() [function.preg-grep]:
Compilation failed: missing terminating ] for character class at offset
47" have been reported by two users).
I've run the acl tests after this change and everything passes so this
shouldn't break anything but please test this especially with protected
wikis as this change modifies the code that handles namespace
permissions. Furthermore permissions for a namespace foobar are no
longer applied to namespaces with names like foo.ar, I hope nobody has
used that "feature".
When you are using per-user namespaces, user registration is open and
either write or read protection for these namespaces is important to
you this is a security fix for you: When someone wants to get access to
the namespace of a user "foo.bar" he can register as "fooxbar" (where
"x" is an arbitrary character) and will have access to the user
namespace of the user "foo.bar" as when a page in "foo.bar" is checked
it will match the rule for "fooxbar".
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This function abstracts checking a given user and her groups against a
given member list (as used in the superuser and manager options).
It is also used in auth_isManager() and auth_isAdmin(), unlike the
previous function, this one skips the nameencode step as it should be
unnessary here (all input is given decoded).
The test cases where extended by some non-ID user and group names.
People with non-plain auth backends should check that their
administrator and manager setups still work as expected
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to have modes that do accept headers
(baseonly) in the parser.
Related test cases are still running through but I'm not 100% sure
I did not break something here. So it should be tested a bit more.
This patch will allow plugins to wrap multiple sections, however it
also makes it possible to easily break XHTML validity, because
headers also open and close sections, so plugin authors need to be
aware!
In case you wonder: this patch is not about allowing formatting
inside headers.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 4871414204799044c31aa2764c4b4ca020e2331d.
Additionally there is a new fix for FS#2107 that doesn't introduce a lot
of checks but instead ensures that the configuration option can't be set
to negative values when the configuration manager is used.
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
20:51:05 <glen> what is the difference between $INFO['userinfo'] and $USERINFO?
20:52:17 <splitbrain> none really
20:52:33 <glen> yet one works ($USERINFO) and the other doesn't in my setup
20:52:59 <splitbrain> $INFO isn't available everywhere
20:53:27 <splitbrain> or might not have been set yet (if you're fetching an early action hook)
20:53:27 <glen> yeah, mail headers setup failed for me
|