[geeklog-devtalk] geeklog-devel digest, Vol 1 #492 - 1 msg

[geeklog-devel-request at lists.geeklog.net]

Send geeklog-devel mailing list submissions to
	geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
	geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

   1. Re: PLG_commentPreSave (Vincent Furia)

--__--__--

Message: 1
Date: Thu, 27 Jan 2005 12:26:52 -0500
From: Vincent Furia <vfuria at gmail.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] PLG_commentPreSave
Reply-To: geeklog-devel at lists.geeklog.net

On Thu, 27 Jan 2005 12:00:27 -0500, Blaine Lang <geeklog at langfamily.ca> wrote:

> 

> Dirk, Tom and I talked about this when implementing the new SPAMX API's and

> decided that it was best to still have a Non-Spamx API to allow other

> plugins to add any other comment related filtering or handling that may be

> required.

> 

I'm still confused as to why different APIs are needed since they
appear to do the same thing.  They are even called one after the
other.

I think one plugin call would be enough, something like:

PLG_commentPreSave(title, comment, ...) and have it return HTML to
output if there is an error (this can include a COM_refresh) otherwise
just return 0.  If I can work it into the plugin API to pass the
comment and title by reference, plugins could modify those and still
return a "success" status.

Thoughts?

-Vinny


--__--__--

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel


End of geeklog-devel Digest