# Summary

The Message module is the core of the message stack. It enables logging and displaying system events in a number of different use cases. Events that are recorded over time are sometimes call activity streams. Exportable messages subtypes can be created for different use cases with custom fields and display (view) modes.

# Project URL

https://www.drupal.org/project/message

# Where is the code?

https://github.com/Gizra/message/tree/8.x-1.x

# Estimated completion date

# Dependencies

# Who's doing the port?

# What help do they need?

# D8 roadmap

https://www.drupal.org/node/2216877

# Background and reference information

Comments

jhedstrom created an issue. See original summary.

jhedstrom’s picture

jhedstrom’s picture

Status: Active » Needs work
giorgio79’s picture

Also keep in mind https://www.drupal.org/project/courier where message could integrate.

giorgio79’s picture

And another important aspect is whether it should be based on Symfony bundles now such as https://github.com/FriendsOfSymfony/FOSMessage

mccrodp’s picture

Not sure how useful this would be for Message module as FOSMessage is a:

...library providing a data structure and common features to set up user-to-user messaging systems.

Whereas, Message module is currently geared towards "logging and displaying system events". However, it may be useful for Message Private as you pointed out on #2613152-4: [message_private] Message Private

andypost’s picture

There's history core module that could incorporate the storage and extended when some model polished in contrib

jhedstrom’s picture

Status: Needs work » Needs review

Alpha 1 released.

a.romantsov’s picture

I've checked out a module. I also created another custom message template - user cancel logging (using hook_user_predelete() ) and everything worked fine! Great job!

jhedstrom’s picture

Status: Needs review » Reviewed & tested by the community

An rc has been released.

jhedstrom’s picture

Status: Reviewed & tested by the community » Fixed
apaderno’s picture

I am giving credits to the users who participated in this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.