See http://peter.deweeses.net/doku.php?id=programming:wp_most_recent. : transfer more information here.

Wordpress Most Recent Entries allows you to show the most recent entries from wordpress blogs in any Dokuwiki page. The display and many properties are completely customizable, and polish can be added. For example, dates can be displayed as “1 day 7 hours ago”, and summeries are ended with “[…]”. This is my first PHP project, so please give me tips! For bugs and tips (not gripes), email mailto:peterdeweese@earthlink.net. Please include the exact versions of dokuwiki and wordpress that you are using with a full description of any issue. (add a compatibility chart)

• custom template for blog entry display
• connection aliases
• summary or full article view
• category constraint
• max settings for entries, categories, and summary length

1. Under your wiki installation, create the directory ‘lib/plugins/wp_most_recent’.
2. Place ‘syntax.php’ into this directory.
3. Configure using the instructions below.

Configure wp_most_recent in your dokwiki installation under conf/local.php.

Since WordPress blogs are databased as dynamic, the semi-static nature of Dokuwiki rendering can get in the way.

• Set the maximum cache length to a reasonable value. For many sites, a half hour to a one day period will be reasonable.
• Time-ago strings are generated on the client side, so they should not be considered when configuring cache settings.
• If real-time posts are required, the cache must be turned off. Performance test your site without caching. If the performance is an issue, question why you require a static style collaborative website to be so dynamic. If performance is not acceptable, consider hybrids such as Confluence or Blog:CMS.

At least one alias is required, but you can also configure the plugin to work with multiple WordPress databases. By default, the default alias should be named “default”. For each alias of name <aliasname>, include the following properties:

/These settings should mirror the configuration for a wordpress configuration.
$conf['wp_most_recent']['db_alias']['<aliasname>']['host']         = "localhost";
$conf['wp_most_recent']['db_alias']['<aliasname>']['user']         = "db_user";
$conf['wp_most_recent']['db_alias']['<aliasname>']['pass']         = "db_password";
$conf['wp_most_recent']['db_alias']['<aliasname>']['sid']          = "wordpress";
$conf['wp_most_recent']['db_alias']['<aliasname>']['table_prefix'] = "wp_";
$conf['wp_most_recent']['db_alias']['<aliasname>']['baseurl']      = "http://<host>/blog";

Although any attribute can be defined by editing the wiki tags, a default attribute can be overridden using the following line:

$conf['wp_most_recent']['defaults']['<attribute>']='<value>';

<wp_most_recent [attribute1="value1" attribute2="value2" (...)]>[entry_template]</wp_most_recent>

Entry templates can include tokens, html (, and wiki syntax):

<p>@categories@ <b>@title@</b><br/>@time_ago@ - @author@<br/>@content@</p>

Tokens are surrounded with ‘@’. Ex: @title@

• category template aliases
• dokuwiki syntax
• add user full name, first name, and last name as tokens

[…] I think that there are definite limits to generating an absolute time reference in HTML which are fixed and rapidly become out of date. A better idea would be to make the PHP generate some JavaScript code. The JavaScript code would include a reference to the base time/date the WordPress page was updated. The JavaScript code could then process that code on the fly to produce the finished page that the end user sees. This would ensure that the time/date stamp is always current. […] — ta' lajzar 2005-08-23 00:13

And it would therefore not require as many cache updates. This is the way to go. - Peter DeWeese

Implemented. - Peter DeWeese

it's possible for dotclear 2 to do the same ?

this is offline, can someone upload the file to somewhere else?