Tanguy Ortolo | 9 Feb 11:45
Picon

PHP 4.5 compatibility

Hello,

Debian has begun a transition to PHP 5.4, so I shall have to check that
the package for DokuWiki still works with that version.

By chance, did anyone already try DokuWiki with PHP 4.5?

-- 
 ,--.
: /` )   Tanguy Ortolo <xmpp:tanguy <at> ortolo.eu> <irc://irc.oftc.net/Tanguy>
| `-'    Debian Developer
 \_

--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Don Shesnicky | 8 Feb 15:52
Picon
Picon

forums catpcha


The captcha presented when registering for the forums occasionally has 
more characters in it then the text input field will accept.

Don
--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Chris Green | 8 Feb 15:08

Data from handle() to render() in plugins, how persistent/global is it?

I have two plugins which both pass data to their render() function in
the array returned by the handle() function, the normal/only way to do
it. 

One of the items in the array is an array itself, called $rows.

It seems that that data in $rows is common to both plugins, i.e. I am
seeing the data that one plugin has put into the array when I use it in
the other plugin.  This causes a problem when the data is used for
insertion into a database using PDO and an INSERT query like:-

    INSERT INTO zzr1200 (seqno, blogdate, Mileage, Description) VALUES
    (:seqno, :Date, :Mileage, :Description)

The insert fails because there is too much data in the $rows array as it
has values from the 'other' plugin as well as the expected values keyed
with seqno, blogdate, Mileage and Description.

Is this a bug or is it just the way that DokuWiki works?

What's the best way around the problem?

    Use different names for the $rows array in the two plugins?

    Is there a way to guarantee all values are removed from the array?

    Any other ideas?

It probably only affects odd cases like this as normally the handle()
function will have explicitly set all the values expected by the render()
(Continue reading)

git changes 2012-02-08


Good Morning!

This are the git changes for DokuWiki committed
yesterday. Please test them and report bugs.

---------------------------------------------------------------------

http://github.com/splitbrain/dokuwiki/commit/b2a1a44c2b1170a6fdbec637fa077c1469631511
Author: Marius Olar <olarmariusalex[at]yahoo.com>
Date:   Tue Feb 7 19:46:28 2012 +0100

    Romanian language update

---------------------------------------------------------------------

You can download individual diffs or patches by appending .diff or
.patch to the given commit URLs above.

Bye,
your git changelog mailer

--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Chris Green | 8 Feb 00:04

Is it possible to get data between states in plugins?

A typical syntax plugin with a format like:-

    <plugin:param1=abc&param2=xyz>Some text here</plugin>

Will handle states DOKU_LEXER_ENTER, DOKU_LEXER_UNMATCHED and
DOKU_LEXER_EXIT in its handle() function, is there any way to communicate
between them?

E.g. will class variables be available between calls or is each call
of handle() in a different instance of the syntax plugin class?

-- 
Chris Green
--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

git changes 2012-02-07


Good Morning!

This are the git changes for DokuWiki committed
yesterday. Please test them and report bugs.

---------------------------------------------------------------------

http://github.com/splitbrain/dokuwiki/commit/5c0c6845e9d948437a54eb986c9f339dfc4b2c62
Author: PCPA <pcpa[at]cyberpunk.su>
Date:   Mon Feb 6 23:39:40 2012 +0100

    Russian language update

---------------------------------------------------------------------

You can download individual diffs or patches by appending .diff or
.patch to the given commit URLs above.

Bye,
your git changelog mailer

--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Chris Green | 6 Feb 19:52

Error reporting, or not - I'm not seeing PHP errors anywhere

I have a big new problem with developing plugins in DokuWiki, PHP syntax
errors don't seem to be reported anywhere.

I've recently updated my Dokuwiki installation to Angua, I'm not sure if
it's related or not, I certainly *used* to see errors reported on the
web page and/or in the apache error log.  

So, has anything changed in Angua which might affect error reporting?  
Errors outside of DokuWiki are reported OK, both to screen and to the
apache error log.

As things are now when there's any sort of error in my plugin code all I
get is a completely blank screen and no sort of error message anywhere. 
This makes diagnosis rather difficult!

-- 
Chris Green
--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Chris Green | 6 Feb 17:45

Mixture of syntax and action plugin wanted - how to do this?

I'm trying to do something that seems to be a mixture of a syntax plugin
and an action plugin.

It's a syntax plugin in that I need to extract some information from the
wiki text using the syntax plugin connectTo() function, but then it's an
action plugin because I only want to do something with the extracted
text when the page it's on has been edited (or created).

Is there any mechanism for handing data between them?  I need to extract
the text and put it somewhere so that an action plugin triggered by
(say) IO_WIKIPAGE_WRITE can handle it.

Alternatively do I simply put it all in the IO_WIKIPAGE_WRITE action
plugin and search for the relevant text strings there?

-- 
Chris Green
--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Chris Green | 6 Feb 15:48

Is there any 'recommended' formatting/layout/syntax for plugins?

I seem to remember asking something like this a long time ago but I
don't think I got a very conclusive answer then and a lot of things have
changed since (Dokuwiki has developed and so has my knowledge, a bit).

So are there any good reasons for using particular Dokuwiki syntax for
calling plugins?  I have two basic questions I think:-

1. Is there any particular reason to prefer, say "<pluginName......>"
over "~~pluginName......~~" or any other character or characters?  If
not then should we not recommend one particular format just for the sake
of consistency (unless there are *very* specific reasons for using
something different)?

2. Are there any reasons for putting parameters/text in one place rather
than another?

E.g. is there any major difference between:-

    <pluginName:A load of text of some sort>

... and:-

    <pluginName>A load of text of some sort</pluginName>

I know that the plugin code will get called with DOKU_LEXER_ENTER,
DOKU_LEXER_UNMATCHED, DOKU_LEXER_EXIT with the text from the various
places.  What I'm asking is whether there is any good reason for putting
things in particular places.  

--

-- 
(Continue reading)

Anika Henke | 5 Feb 19:42
Gravatar

Embrace the new default template

Hi all,

Finally, our new default template is finished! \o/

Logged-in users can see it from today on on dokuwiki.org (users who are 
not logged in will still see the old one). Please report any issues to 
http://bugs.dokuwiki.org/index.php?do=newtask&project=1&product_category=16
It's not in the core repository yet, but will be soon.

I'd like to tell you a bit about the history of this template to make 
clear how much of an effort it actually was:

We've been unhappy with the current default template for a very long 
time now and had plans to write a new one ever since. I don't remember 
exactly when was the first time we talked about it, but I remember at 
least when Andi added tpl_include_page() (which was on 05 June 2009) 
that that was already meant for the new template and by that time the 
idea was already "old". Andi remembered that he did the 
tpl_actiondropdown() also for the idea of making the new default 
template more mobile friendly and that was even further back (17 August 
2008).

I actually started to prepare the template back in 2009 (not quite sure 
when exactly, might even have been 2008?). But as we were lacking 
designers and professional design ideas, I went ahead and released it 
"without a design" as the starter template 
[http://www.dokuwiki.org/template:starter] in November 2010, planning to 
use it as the base for the default template whenever we'd have a design. 
And that plan succeeded, the new template is indeed based on the starter 
template.
(Continue reading)

Chris Green | 5 Feb 17:13

data and sqlite plugins - sqlite 2 only? - broken on newer Linux distros

I just tried to have a play with the data plugin and hence needed the
sqlite plugin as well.

It would appear that they fail on new[er] Linux distributions because
they depend on the [no longer] built in sqlite interface in PHP5.  

What happens is that one gets errors reported by sqlite which are caused
by:- 

[Sun Feb 05 15:51:48 2012] [error] [client 192.168.1.4] PHP Fatal error:
 Call to undefined function sqlite_open() in
 /home/www-data/src/dokuwiki-plugins/sqlite/helper.php on line 63,
 referer: http://wiki/blog:2012:02:05?do=admin

I'm running ubuntu 11.10 and have everything PHP5/sqlite related
installed, if you search with Google you find that it's generally
recommended that one uses PDO for database access with sqlite3 and it
would seem that sqlite2 support is disappearing.

-- 
Chris Green
--

-- 
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist


Gmane