Bug 316767 - some replacements do not work in template
Summary: some replacements do not work in template
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-15 09:30 UTC by Silver Salonen
Modified: 2017-01-07 22:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Silver Salonen 2013-03-15 09:30:01 UTC 
I've created new template for replying with plain text. When I use the template, quoted text in plain text (%FORCEDPLAIN) and signature is gone (the signature being gone may be related to bug 279602 maybe?). Template is as follows:

%CURSOR

--
%SIGNATURE

%REM="Default reply all template"%-
On %ODATE %OTIMELONG %OFROMNAME wrote:
%FORCEDPLAIN

Reproducible: Always

Steps to Reproduce:
1. Use %SIGNATURE and %FORCEDPLAIN in template
Actual Results:  
Message becomes:

--


On Thursday 14 March 2013 16:22:51 Some Person wrote:


Expected Results:  
Message becomes:

--
Silver Salonen

On Thursday 14 March 2013 16:22:51 Some Person wrote:
quoted text
Comment 1 Laurent Montel 2013-03-15 10:15:16 UTC 
signature html ? plaintext ?
Comment 2 Silver Salonen 2013-03-15 10:16:35 UTC 
HTML
Comment 3 Silver Salonen 2013-03-17 16:33:35 UTC 
BTW, it does not make any difference if I remove/disable my signature from the identity.
Comment 4 Denis Kurz 2016-09-24 18:11:49 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:03:14 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.