Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

You've Got Mail #20162

Merged
merged 4 commits into from
Apr 29, 2018
Merged

You've Got Mail #20162

merged 4 commits into from
Apr 29, 2018

Commits on Apr 13, 2018

  1. You've Got Mail

    Since 2003 the internet has changed. We no longer get a message to say that we have a message. Instead we just give you the message. You probably never use the messages component (especially for private message to a specific user) as they are the equivalent of https://www.youtube.com/watch?v=gFBLiHpkcOk
    
    The Joomla com_messages component is used in two instances
    
    1. Notification of a new article
    2. Sending a message to another user
    
    ### Current email for Notification of a new article
    Subject: A new private message has arrived from [sitename]
    Body:
    > Please log in to [link] to read your message.
    
    ### New email for Notification of a new article
    Subject: New message from [user] at [sitename]
    Body:
    > New Article
    A new Article has been submitted by 'user' entitled 'blog post'.
    > Please log in to [link] to read your message.
    
    ### Current email when sending a message to another user
    Subject: A new private message has arrived from [sitename]
    Body:
    > Please log in to [link] to read your message.
    
    ### New email when sending a message to another user
    Subject: New message from [user] at [sitename]
    Body:
    > [subject]
     [message]
    [login link]
    
    ## Backwards Compatibility
    No issues. The message contains the old login message PLUS the content of the message. So if you were using this message in a custom workflow there is no change required to that workflow
    brianteeman committed Apr 13, 2018
    Configuration menu
    Copy the full SHA
    68b1d8b View commit details
    Browse the repository at this point in the history
  2. subj

    brianteeman committed Apr 13, 2018
    Configuration menu
    Copy the full SHA
    30e53cc View commit details
    Browse the repository at this point in the history
  3. cs

    brianteeman committed Apr 13, 2018
    Configuration menu
    Copy the full SHA
    39509d6 View commit details
    Browse the repository at this point in the history

Commits on Apr 14, 2018

  1. Configuration menu
    Copy the full SHA
    0e97189 View commit details
    Browse the repository at this point in the history