6.0.0-alpha12
6/8/25

[#6711] Viewing Inline HTML vs text message as user settable option
Summary Viewing Inline HTML vs text message as user settable option
Queue IMP
Queue Version Git master
Type Enhancement
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester dion.rowney (at) usask (dot) ca
Created 05/15/2008 (6233 days ago)
Due
Updated 09/27/2010 (5368 days ago)
Assigned
Resolved 09/27/2010 (5368 days ago)
Milestone
Patch No

History
09/27/2010 08:45:55 PM Michael Slusarz Comment #12
Assigned to Michael Slusarz
State ⇒ Resolved
Reply to this comment
This is now possible with the new prefs UI framework.
12/16/2009 04:35:22 AM Michael Slusarz Comment #10
State ⇒ Rejected
Reply to this comment
I'm going to reject.  Maybe in the future there will be some 
Horde_Prefs_Ui way to interact with mime_drivers.php settings.
12/15/2009 09:53:50 PM Jan Schneider Comment #9 Reply to this comment
That's a good point, it would indeed make the configuration a bit confusing.
12/15/2009 08:41:25 PM Michael Slusarz Comment #8 Reply to this comment
I still don't agree with this.  I don't want the same configuration 
option appearing in 2 different locations: mime_driver config needs to 
stay in the mime_driver config files where everything else about that 
driver is configured.
12/10/2009 12:19:08 AM Jan Schneider Comment #7 Reply to this comment
We should lock the preference by default, so that it mimics the 
current behavior of the mime_drivers.php setting.
12/09/2009 11:36:54 PM Michael Slusarz Comment #6
State ⇒ Feedback
Version ⇒ Git master
Reply to this comment
Should this really be user settable?  This implicates both security 
and server load concerns (XSS/Phishing filtering is not cheap) and 
seems to be better left to the discretion of an admin.
12/14/2008 03:48:02 PM Chuck Hagenbuch State ⇒ Accepted
 
11/06/2008 04:23:43 PM dion (dot) rowney (at) usask (dot) ca Comment #5 Reply to this comment
PS, I am sure there is a better way to do this and am hoping the horde 
team can do it better than my hack of a solution.
11/06/2008 04:22:29 PM dion (dot) rowney (at) usask (dot) ca Comment #4 Reply to this comment
You said you were modifying files for this - can you submit a patch?
I can tell you what I did as its not that difficult.  In 
mime_drivers.php I added an if statment and changed the boolean value 
to be a variable name:





if ( $GLOBALS['prefs']->getValue('html_inline_viewing') === '0' ) {

         $viewHtmlInline = false;

} else {

         $viewHtmlInline = true;

}





/**

  * HTML driver settings

  */

$mime_drivers['imp']['html'] = array(

     'inline' => $viewHtmlInline,





and created a new preference in prefs.php:



$_prefs['html_inline_viewing'] = array (

        'value' => 1,

        'locked' => false,

        'shared' => false,

        'type' => 'checkbox',

        'desc' => _("View messages as HTML when both HTML and plain text are 
available (this change takes effect after log out)?"),

        'help' => 'prefs-notavailable'

);
11/06/2008 02:19:29 AM Chuck Hagenbuch Comment #3
State ⇒ Feedback
Reply to this comment
You said you were modifying files for this - can you submit a patch?
05/16/2008 09:13:57 AM Jan Schneider Comment #2
Version ⇒ HEAD
State ⇒ Accepted
Reply to this comment
Makes sense.
05/15/2008 10:49:45 PM dion (dot) rowney (at) usask (dot) ca Comment #1
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Viewing Inline HTML vs text message as user settable option
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ New
Reply to this comment
I am currently modifying the prefs.php and mime_drivers.php files to 
add the ability to give users the choice of viewing messages in HTML 
or text by default as a preference option.



Has the Horde team looked at adding this as a user settable option if 
inline HTML and text are being permitted (and a message has both 
formats being sent in message)?



Can this be added as a request for future releases?

Saved Queries