Extension of modUserMessage

Hi there,

I'm currently planning to extend the internal MODX messaging system to use in a frontend context.

In the RFTM I found the article regarding the extension of modUser, which includes core changes. I want to avoid core changes for obvious reasons of udpate processes.

Is anybody out there having experience with this stuff?
Would it be easier to create a new component from scratch?

Thanks for any suggestions, help, guidance.

I'm going to vote for creating what you need from scratch, though that may be cause I never used the message system within MODX at all

It really depends on what you want to do. For example:

When do you want to send messages to the user (on login or when the message is created)?

Would you rather use the Manager message system or email to send the message?

Do you need to store the user message, or just send it?

Will you need to store multiple messages for each user?

How do you want the user to respond to the message?


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODX info for everyone: http://bobsguides.com/modx.html

Hi,

I'm all with Mark here : tailor what you need.
For me (and after talking with Jason -- opengeek), extending modUser should be done when you need to change your login/identification process (like using Jainrain or a LADP).

If you need some more table fields, i would create another table tailored to your needs, without touching modUser/any core table... but as Bob wrote, it all depends on your needs

Hope my 2 cents will be helpful