6.0.0-beta1
9/9/25

[#4164] Default values for mail_hdr preference don't work
Summary Default values for mail_hdr preference don't work
Queue IMP
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Owners jan (at) horde (dot) org
Requester Otto.Stolz (at) uni-konstanz (dot) de
Created 07/17/2006 (6994 days ago)
Due
Updated 08/01/2006 (6979 days ago)
Assigned 07/19/2006 (6992 days ago)
Resolved 08/01/2006 (6979 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/01/2006 03:36:20 PM Jan Schneider Summary ⇒ Default values for mail_hdr preference don't work
 
08/01/2006 03:35:41 PM Jan Schneider Comment #4
State ⇒ Resolved
Reply to this comment
Default values for this preference don't work with the current 
implementation. It has been turned into a regular preference for CVS 
HEAD/IMP 4.2, but we can't merge this to 4.1.x since the current user 
settings would get lost as a sideeffect.
07/19/2006 10:44:55 PM Jan Schneider Assigned to Jan Schneider
State ⇒ Assigned
 
07/17/2006 02:47:47 PM Otto (dot) Stolz (at) uni-konstanz (dot) de Comment #3 Reply to this comment
The complete PHP message:
Warning: Invalid argument supplied for foreach() in
/opt/test-webmail/horde/imp/message.php on line 340
However, I now have problems reproducing it: Apparently, the setting of

$_prefs['mail_hdr'] ['value'] has no effect on the mail users I have used

for previous tests: they keep their former preference setting, even if I

- hit the "undo" link in the preference window,

- log out from imp, and in again,

- log out from imp and horde, and in again,

- stop and start the Apache server,

- delete the pertinent entry from the mysql table:

     delete  from horde_prefs

     where pref_uid='testaccount@uni-konstanz.de'

     and pref_name="identities";



The only way to reproduce the error message was to lock the entry

in horde/imp/config/prefs.php -- but then I always got that PHP warning

and was not able to find a value that would avoid it.



So the additional questions arise:

- How can I test this issue without genereating a new user-id, for every

   single test-shot?

- How can I propagate a new option (as this one) to all users of the

   previous Imp version?

- How can a user reset an option so as to use the default at run time

   (as opposed to the default at option-setting time)?
07/17/2006 10:18:30 AM Jan Schneider Comment #2
Version ⇒ HEAD
Queue ⇒ IMP
State ⇒ Feedback
Reply to this comment
Please specify the complete error message. This should actually be 
handled gracefully in IMP.



There is no fixed syntax for textarea pref values.
07/17/2006 10:04:04 AM Otto (dot) Stolz (at) uni-konstanz (dot) de Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Describe syntax for textarea type prefs
Queue ⇒ Horde Base
State ⇒ Unconfirmed
Reply to this comment
For documentation on the structure of  horde/imp/prefs.dist, that file 
refers to horde/config/prefs.php. Horde/imp/prefs.dist contains 'type' 
=> 'textarea' entries, but horde/config/prefs.php  gives no syntax for 
their possible values.



An attempt with $_prefs['mail_hdr']['value'] = 
"Message-ID\nX-Spam-Level" has led to a PHP run-time error in 
horde/imp/message.php on line 340, which clearly demonstrates that 
documentation on the configuration syntax is required.



The correct syntax seems to be: "Message-ID\nX-Spam-Level\n", with 
"\n" terminating (not separating) the partial values.

Saved Queries