[Tickets #13732] Re: [move_innocent_after_report'] not set globally

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13732
------------------------------------------------------------------------------
  Ticket             | 13732
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | [move_innocent_after_report'] not set globally
  Queue              | IMP
  Version            | 6.2.3
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-12-02 15:54) wrote:

> After configuring $_prefs['move_innocent_after_report']['value']  
> within prefs.local.php within the IMP path, this setting has _no  
> effect on the global configuration_. New users still need to  
> configure this value manually.

Can't reproduce.

> I've tested this with new users. And with existing users where I've  
> run the mysql statement "DELETE FROM horde_prefs...."

Even though you said you did this, your description sounds exactly  
like this is still the issue: you have existing prefs still remaining  
in your prefs backend.

Either that or you have a move_ham_after_report preference still  
existing in your prefs backend and, for some reason, the upgrade  
script is running on every login and copying over that old value.

> delete_spam_after_report for example, works.

Considering the code handling innocent and spam after report is  
identical (they are both used in only 1 place), this is more evidence  
that your prefs backend is not pristine.