Simple Machines Community Forum

SMF Development => Bug Reports => Fixed or Bogus Bugs => Topic started by: Pentaxian on November 18, 2010, 11:14:27 AM

Title: Don't allow post text in notifications doesn't function
Post by: Pentaxian on November 18, 2010, 11:14:27 AM
SMF 2.0 RC4/
Ad management/
Only standard themes from install
Language: Dutch
Not using UTF8

Description:
In Admin/Features and options/General, the last option is: Don't allow post text in notifications
As was the same in RC3 this option doesn't work. It makes no difference if one checks or unchecks this option. The notification mail always contains the text of the PM.
Title: Re: Don't allow post text in notifications doesn't function
Post by: emanuele on January 14, 2012, 03:00:56 PM
But probably it should...

A similar situation is with BBCode: if it is disabled in the entire forum it is disabled also in the signatures.
Title: Re: Don't allow post text in notifications doesn't function
Post by: emanuele on June 28, 2012, 04:33:25 AM
I think I added at some point a checkbox to disallow PM text in notifications (pretty sure since at the same time I moved the email text to EmailTemplates), so this should be solved.
Title: Re: Don't allow post text in notifications doesn't function
Post by: szinski on March 10, 2013, 01:03:00 PM
Quote from: emanuele on June 28, 2012, 04:33:25 AM
I think I added at some point a checkbox to disallow PM text in notifications (pretty sure since at the same time I moved the email text to EmailTemplates), so this should be solved.

So where is this checkbox? Under which settings? Thanks!
Title: Re: Don't allow post text in notifications doesn't function
Post by: emanuele on March 10, 2013, 01:10:12 PM
In 2.1 is the same option that removes the text for other notifications (i.e. posts).
Title: Re: Don't allow post text in notifications doesn't function
Post by: szinski on March 10, 2013, 01:11:23 PM
Oh, v2.1... I'm running 2.0.4.
Title: Re: Don't allow post text in notifications doesn't function
Post by: emanuele on March 10, 2013, 01:40:06 PM
Since it's not a security issue, this is "fixed" in 2.1 that is the next release. ;)