<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>.vacation.db always empty</title>
  <pubDate>Sun, 07 Sep 2008 04:42:36 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/5797</link>
  <atom:link rel="self" type="application/rss+xml" title=".vacation.db always empty" href="http://bugs.horde.org/ticket/5797/rss" />
  <description>.vacation.db always empty</description>

  
  
  <item>
   <title>When using vacation, whatever type of database driver I use </title>
   <description>When using vacation, whatever type of database driver I use (empty, hash, hash3 ...) the .vacation.db file is created empty.
The .forward file is created fine.</description>
   <pubDate>Mon, 15 Oct 2007 12:38:33 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t37690</link>
  </item>
  <item>
   <title>I work around it with this hack:
empty.empty.bin -&gt; empty.h</title>
   <description>I work around it with this hack:
empty.empty.bin -&gt; empty.hash3.bin

empty.empty.bin is now a simbolic link to empty.hash3.bin (the db I wanted to use).</description>
   <pubDate>Mon, 15 Oct 2007 13:17:35 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t37691</link>
  </item>
  <item>
   <title>So you had set the dbtype parameter to 'hash3', but it was d</title>
   <description>So you had set the dbtype parameter to 'hash3', but it was defaulting to 'empty'?</description>
   <pubDate>Mon, 24 Dec 2007 16:49:39 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40267</link>
  </item>
  <item>
   <title>&gt; So you had set the dbtype parameter to 'hash3', but it was</title>
   <description>&gt; So you had set the dbtype parameter to 'hash3', but it was defaulting 
&gt; to 'empty'?

It was always empty, whatever dbtype I selected.</description>
   <pubDate>Mon, 07 Jan 2008 07:09:17 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40838</link>
  </item>
  <item>
   <title>I'm sorry, but I'm not entirely sure we're talking about the</title>
   <description>I'm sorry, but I'm not entirely sure we're talking about the same question - in the config file, is the setting correct? In other words, is the dbtype right in the configuration file, but not being honored? Or is it not even getting into the configuration file correctly?</description>
   <pubDate>Tue, 08 Jan 2008 17:18:09 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40933</link>
  </item>
  <item>
   <title>This is what I have in my conf.php:
$conf['server']['params</title>
   <description>This is what I have in my conf.php:
$conf['server']['params']['default']['dbtype'] = 'hash3';
but it alwys take empty.empty.bin .

Could you reproduce the problem?</description>
   <pubDate>Wed, 09 Jan 2008 03:22:21 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40944</link>
  </item>
  <item>
   <title>Do you have a realm defined?  If so, you need to define it w</title>
   <description>Do you have a realm defined?  If so, you need to define it with the realm name. If not,
then it should work as shown (using &quot;default&quot; for the realm).</description>
   <pubDate>Wed, 09 Jan 2008 12:26:06 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40950</link>
  </item>
  <item>
   <title>&gt; Do you have a realm defined?

Yes, I have a realm define</title>
   <description>&gt; Do you have a realm defined?

Yes, I have a realm defined in 
imp/config/servers.php
within $servers['imap'] = array( ....

&gt; If so, you need to define it with the 
&gt; realm name.

It's not very clear to me what should I do.</description>
   <pubDate>Thu, 10 Jan 2008 04:47:49 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40980</link>
  </item>
  <item>
   <title>Try manually editing your conf.php and changing the realm na</title>
   <description>Try manually editing your conf.php and changing the realm name from &quot;default&quot; to
the value of your realm.  So if you realm was &quot;example.com&quot; you could try changing

$conf['server']['params']['default']['dbtype'] = 'hash3';

to 

$conf['server']['params']['example.com']['dbtype'] = 'hash3';

If that works, then it is a realm issue.  You'd then have to look at the conf.xml stuff to
see if it is supporting realms correctly or not, and if so how to use them with it...
For now, try manually editing the file to see if it works or not.
</description>
   <pubDate>Thu, 10 Jan 2008 14:17:43 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t40995</link>
  </item>
  <item>
   <title>&gt; Try manually editing your conf.php and changing the realm </title>
   <description>&gt; Try manually editing your conf.php and changing the realm name from 
&gt; &quot;default&quot; to
&gt; the value of your realm.  So if you realm was &quot;example.com&quot; you could 
&gt; try changing
&gt;
&gt; $conf['server']['params']['default']['dbtype'] = 'hash3';
&gt;
&gt; to
&gt;
&gt; $conf['server']['params']['example.com']['dbtype'] = 'hash3';

Done. When trying to submit my vacation message I get this:

Error  Failure in modifying vacation notice: Unable to write VFS file &quot;.vacation.pag&quot;.</description>
   <pubDate>Mon, 14 Jan 2008 08:45:31 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t41122</link>
  </item>
  <item>
   <title>I guess you are using the FTP VFS driver? Try editing horde/</title>
   <description>I guess you are using the FTP VFS driver? Try editing horde/lib/VFS/ftp.php and remove the @ characters in front of the ftp_put() call in the write() method. Then see if you get some more useful PHP warnings.</description>
   <pubDate>Wed, 16 Jan 2008 17:42:58 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t41207</link>
  </item>
  <item>
   <title>I noticed that maybe I should have changed _all_ the entry o</title>
   <description>I noticed that maybe I should have changed _all_ the entry of type:
$conf['server']['params']['default']['XXXXXX']
to:
$conf['server']['params']['example.com']['XXXXXX']

After doing this I don't get the warning anymore.

Also, I noticed that whatever ['default'] or ['example.com'] I use it works fine now. I was sure it didn't work before (but maybe I only forgot to relogin in horde after changing configuration? I was, however, pretty sure I did a relogin).

The bug could then be closed. I'll reopen if I'll have other problem.</description>
   <pubDate>Thu, 17 Jan 2008 09:07:52 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/5797#t41272</link>
  </item>
  

 </channel>
</rss>
