MODX Staff
MODX Staff
MODX Staff
I’m not understanding the new event question; at what point in the core would this event be executed? I think we have all the events we need. You’ll just get the service in your snippet or plugin registered to the event of your choice, or even in an external script that is instantiating the modX class, and call the appropriate function( s ).
It might be nice to have a plugin as a wrapper for it, since every client will want pretty much the same thing. What do you think about a new System Event for it?
I can see it being used in a lot of places for logins and content evaluation. With the plugin, the client would just invoke the event with some optional parameters and get a yes/no result with the plugin handling the communication and user interaction (hypothetically, of course). That would make it easy to integrate into other components.
MODX Staff
<?php
/* add the package */
$modx->addPackage('mollum', MODX_ASSETS_PATH . 'components/mollum/model/');
/* get the service using the run-time properties from the snippet/plugin */
if ($modx->getService('mollum', 'mollum.modMollum', '', $scriptProperties)) {
/* evaluate your chosen contentVariable for spam */
if (!$modx->mollum->evaluate($contentVariable)) {
/* it's spam, take some action */
} else {
/* it's not spam, do something else */
}
}
?>
Further, in 0.9.6 it can be loaded as an "extension" like DBAPI, and in Revolution as a "service" class, like modRegistry and modSmarty (see modX::getService()).
It seems to me the primary use of this service class would already be in a plugin triggered on the form events, at least on the backend, and for the front-end adding it to the form processing will be as simple as using it in a plugin. Here’s a Revo code example that might be used in a plugin or snippet.
<?php /* add the package */ $modx->addPackage('mollum', MODX_ASSETS_PATH . 'components/mollum/model/'); /* get the service using the run-time properties from the snippet/plugin */ if ($modx->getService('mollum', 'mollum.modMollum', '', $scriptProperties)) { /* evaluate your chosen contentVariable for spam */ if (!$modx->mollum->evaluate($contentVariable)) { /* it's spam, take some action */ } else { /* it's not spam, do something else */ } } ?>
$eventInfo= $modx->invokeEvent('OnEvaluateContent');
And anyway, the real point IMO is why create an event to execute within an existing system event which is triggering a plugin that uses the Mollum web service? I don’t see any purpose in invoking events in code that may itself be invoked by an event itself.
In the front end, though, there’s really no common event that occurs before saving or emailing user content, but it would be easy for developers to invoke one when processing user input if it existed.
The front end does not save anything and does not email anything and when in the core does it process front-end user input? So where would you have that event triggered? Isn’t it the snippets or plugins that do most of the processing, saving and emailing?