[pmwiki-users] Planning for 2.2.0
aalbuquerque at lanowar.sytes.net
Fri Sep 22 12:04:35 CDT 2006
On Fri, 22 Sep 2006 08:30:44 -0500, Patrick R. Michaud wrote:
> On Fri, Sep 22, 2006 at 12:04:33PM +0000, Karl Loncarek wrote:
> > "Patrick R. Michaud" wrote in
> > > news:20060922033021.GA1458 at host.pmichaud.com:
> > Sounds great.
> > (:comment:) sounds good for boxes and/or an ?action=comment for
> > commentpages? (using a action would allow to set different rigths)
> > But please add some features of commentboxplus:
> > * possiblilty to add comments even without edit rights (maybe
> Yes, commenting and editing will be able to have separate authorizations.
> Commenting will be the ability to add content to a page (but not change
> what is there), while editing includes the ability to modify existing
Comment is not the same as editing, even in a restrict form. Comment is
more in the line of an attribute. It's something that is added to a page
but without changing the page text contents. When editing a page I
expect to edit it's text without the comments. A comment could be added
or deleted but not modified.
> > * optional activation of entering a code number before an entry is
> > (see $EnableAccessCode from commentboxplus). This could greatly help
> > with spammers (together with blocklist2)
> I see commenting as just a restricted form of editing, so whatever
> blocking mechanisms are available for editing will also be available
> for commenting.
The blocking mechanisms should be available for commenting but
commenting should not be related to editing. There should be the
possibility to receive a notice when a page is edited (text contents
modified) and not when a new comment is added (text contents remains the
same) and vice-versa, receiving a notice just when a page has a new comment.
If the text md5 is implemented I expect it's value be related to the
page text contents and not to the page comments
More information about the pmwiki-users