[pmwiki-users] Using AllRecentChanges as a shared page between fields

[Patrick R. Michaud]

On Sat, Jul 23, 2005 at 04:00:50PM +0200, chr at home.se wrote:
> Would it be possible to have Site.AllRecentChanges be shared page between
> fields?

Maybe, if we implement PITS 00459 somehow.  Although, instead of
repurposing Site.AllRecentChanges I think I'd just configure a new
Site.FarmRecentChanges page instead.

> The problem right now (I think) is that if Group.Page exists in two
> fields, you would get conflicting chages in Site.AllRecentChanges. 

Yes, this would be an issue.  But the entry for Site.FarmRecentChanges
could possibly help to make that clearer.

> However, we could still have two instances of pmwiki.php trying to write
> to the same file at the same time. Can the locking mechanism handle this,
> i.e. where is the lock stored?

By default the locking mechanism doesn't handle this, as the lock
is managed on a per-field basis.  However, a farm administrator can
set a farm-wide value for $LockFile, so that all fields share the same
lock, and then there's no problem.

Pm