Event Filter: Add to storage

[designermonkey]

How awesome would that be?

[nilshoerrmann]

Would be kind of nice – but I have no idea how to create an event filter. Personally I think, that Symphony's event system is quite complicated and only half-backed.

How should the event data be added to the storage? Under an events namespace, like storage[events][my-event-name]?

[michael-e]

Maybe you are thinking too complicated.

You don't need the actual event data, do you? Why not create en event filter to simply add POST data (if available) to the storage?

[michael-e]

And why a filter? Coundn't that be an event? (Don't we already have this? I admit that I haven't tested it…)

[nilshoerrmann]

The good thing about using an event filter is that you'd know the data context (your event).
Of course you could recreate that from the POST data, but that seems to overcomplicate things.

But I see use cases for both, an event filter and a general POST to storage event.

[designermonkey]

Yeah, it would definitely need to be a filter, it would have to be added to another event as that is what we're after; Posting data from an event into the session.

I've done event filters before (stopforumspam) so could tackle this at some point soon.

How should the event data be added to the storage?

Yes, like:

storage[events][my-event-name]
storage[events][my-event-name][message]
storage[events][my-event-name][post-values]
storage[events][my-event-name][post-values][value-1]

etc

[designermonkey]

The more we can provide for this extension, the more it will be loved IMO. You two have already got the core of it working really well.

[nilshoerrmann]

Well, the most important thing is to keep this extension focussed.
One reason why it hasn't been announced or released publicly so far.

But I'm with you that a simple event filter would be a useful addition.

[nilshoerrmann]

Adding event data to the storage would be rather simple. Are there any information online how to create an event filter?

[michael-e]

Not that I am aware of. But you might use the ETM's event filter logic as a blueprint. It resides in the extension driver.

[nilshoerrmann]

I just created a filter branch that adds a filter that saves the event's field data in the storage, like so:

        <group id="events">
            <item id="contact">
                <item id="name">John Doe</item>
                <item id="mail">john.doe@example.com</item>
            </item>
        </group>

The first item id matches the event name, the nested ones are the fields.
What do you think?

[michael-e]

Sorry, I am in a hurry. I can think about it tomorrow.

[designermonkey]

Aww, I really wanted to do that one! lol

You got it all done before I even got home!

When I discussed this on the Symphony tracker, I was aiming more at having the xml intact in the session and just reloaded into the page but with an attribute of redirected="true" or similar, but for the purposes of this extension, this is perfectly fine.

[nilshoerrmann]

I just pushed a few updates to the branch fixing bugs and adding a drop filter:
https://github.com/hananils/storage/blob/filter/extension.driver.php