<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Vacation filter - save and enable</title> 
  <pubDate>Fri, 10 Apr 2026 11:23:08 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5901</link> 
  <atom:link rel="self" type="application/rss+xml" title="Vacation filter - save and enable" href="https://bugs.horde.org/ticket/5901/rss" /> 
  <description>Vacation filter - save and enable</description> 
 
   
   
  <item> 
   <title>Ingo is configured with the preferences backend:



How to r</title> 
   <description>Ingo is configured with the preferences backend:



How to reproduce the problem:

- click on filters

- click on vacation

- change the subject or the test

- click on &quot;save and enable&quot;



Result:

- new message is in place in sieve

- no change has been made in the vacation preference in the preferences postgres database backend



If I click only on &#039;Save&#039; instead of &#039;Save and Enabled&#039;, the script is saved correctly.





The problem leading to the bug is that when I click &#039;Save and Enable&#039;,

first the &#039;vacation&#039; preference is set, then the &#039;filter&#039; preference (to

enable the vacation message). Unfortunately, when the preference &#039;store&#039; method is 

executed, only the &#039;filter&#039; preference is saved, but not the &#039;vacation&#039; one.



The problem can be circumvented by adding an explicit preferences &#039;store&#039; call at the end of the _store method in lib/Storage/prefs.php as follows:

$prefs-&gt;store();

</description> 
   <pubDate>Mon, 19 Nov 2007 15:01:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t38754</link> 
  </item> 
   
  <item> 
   <title>What Horde version are you using? Are you up-to-date with In</title> 
   <description>What Horde version are you using? Are you up-to-date with Ingo HEAD or is it an old version? What prefs backend are you using?</description> 
   <pubDate>Mon, 19 Nov 2007 19:58:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t38767</link> 
  </item> 
   
  <item> 
   <title>&gt; What Horde version are you using? Are you up-to-date with </title> 
   <description>&gt; What Horde version are you using? Are you up-to-date with Ingo HEAD 

&gt; or is it an old version? What prefs backend are you using?



Horde version is 3.2 cvs, Ingo is CVS checkout and the prefs backend is a postgresql database using the sql driver</description> 
   <pubDate>Mon, 03 Dec 2007 17:32:20 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t39293</link> 
  </item> 
   
  <item> 
   <title>Have you tried changing multiple preferences in a regular Op</title> 
   <description>Have you tried changing multiple preferences in a regular Options screen and seeing if both are saved?



To Jan or another developer: seems like with all of the Prefs::singleton() calls it&#039;s possible something is getting mixed up with shutdown functions. If that&#039;s the case I wonder if skipping the singleton in _retrieve() and _store() and just doing factory - and maybe adding an explicit store() call, since it is a store method - and then unset($prefs), might help.



I don&#039;t have the backends set up to test this right now.</description> 
   <pubDate>Tue, 04 Dec 2007 05:54:48 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t39322</link> 
  </item> 
   
  <item> 
   <title>&gt; Have you tried changing multiple preferences in a regular </title> 
   <description>&gt; Have you tried changing multiple preferences in a regular Options 

&gt; screen and seeing if both are saved?



Regular options (apart from the filters) work fine

</description> 
   <pubDate>Tue, 04 Dec 2007 12:49:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t39340</link> 
  </item> 
   
  <item> 
   <title>I still can&#039;t reproduce this. And it&#039;s probably a duplicate </title> 
   <description>I still can&#039;t reproduce this. And it&#039;s probably a duplicate of bug #5901.</description> 
   <pubDate>Fri, 07 Dec 2007 18:05:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t39593</link> 
  </item> 
   
  <item> 
   <title>I tried with both PHP 4.4 and PHP 5.2 by the way.</title> 
   <description>I tried with both PHP 4.4 and PHP 5.2 by the way.</description> 
   <pubDate>Fri, 07 Dec 2007 18:06:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t39596</link> 
  </item> 
   
  <item> 
   <title>Can you please try if the attached patch fixes this for you?</title> 
   <description>Can you please try if the attached patch fixes this for you?</description> 
   <pubDate>Tue, 18 Dec 2007 18:45:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t40041</link> 
  </item> 
   
  <item> 
   <title>The duplicate reference is actually bug 4370.</title> 
   <description>The duplicate reference is actually bug 4370.</description> 
   <pubDate>Tue, 18 Dec 2007 18:48:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t40047</link> 
  </item> 
   
  <item> 
   <title>Hello?</title> 
   <description>Hello?</description> 
   <pubDate>Mon, 07 Jan 2008 12:48:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5901#t40847</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
