[horde] Upgrading to 4 from Groupware 1.2.9

Simon Brereton simon.brereton at buongiorno.com
Fri Oct 7 13:52:18 UTC 2011


> -----Original Message-----
> From: Brian Spraker [mailto:spraker at yahoo.com]
> ________________________________
> 
> From: Simon Brereton <simon.brereton at buongiorno.com>
> To: horde at lists.horde.org
> Sent: Tuesday, October 4, 2011 10:07 AM
> Subject: Re: [horde] Upgrading to 4 from Groupware 1.2.9
> 
> > -----Original Message-----
> > From: Brian Spraker [mailto:spraker at yahoo.com]
> > ________________________________
> >
> > From: Simon Brereton <simon.brereton at buongiorno.com>
> > > -----Original Message-----
> > > From: horde-bounces at lists.horde.org [mailto:horde-
> > > bounces at lists.horde.org] On Behalf Of Jan Schneider Zitat von
> Brian
> > > Spraker <spraker at yahoo.com>:
> > >
> > > > Greetings all,
> > > >
> > > > I am looking to perform an upgrade of the Horde system from
> > > Groupware
> > > > 1.2.9 to the new system I've seen that appears to be stable and
> > > > working.
> > > >
> ---
> 
> OK - I am attempting to update tonight - but it isn't working.  I've
> ran through and am trying to do the 'run-scripts horde/Horde_Role'
> and put in the path.  But each time I attempt to do so, I get error:
> 
> Could not save horde_dir configuration value to PEAR config.
> 
> The folder that I am using is in the web server path and exists.
> I've even attempted to do a pear install in that directory (which
> works successfully) and use that install - but it still returns the
> same error.

See http://wiki.horde.org/FAQ/Admin/Troubleshoot?version=73


Some classes cannot be found, even though I installed the package that should contain them.

These symptoms may be caused by two issues:

   1. The installation failed and you didn't notice. Installing Horde through PEAR produces a lot of output, and it's too easy to miss the single error message that's buried in all that informational output. Search the output of the installation process carefully for any failed installations or required dependencies that cannot be installed.
   2. The PEAR configuration setting "horde_dir" is not set correctly. If this configuration is not correctly set, or cannot be received from PEAR, then some files are not installed into the correct web root, or cannot be found there. This can be caused by any of:
          * You didn't run the Horde_Role post-install script. One of the steps of installing Horde through PEAR is to install the Horde_Role package: http://www.horde.org/apps/horde/docs/INSTALL#installing-with-pear. You forgot to run pear run-scripts horde/horde_role.
          * You ran the Horde_Role post-install script, but entered a wrong path. The path you need to enter there must be an existing directory on the filesystem inside the web root directory of your server (aliases and symlinks aside). If for example your web server's web root (http://www.example.com/) directory is /var/www, and you want Horde to be accessed through http://www.example.com/groupware/, you need to create the directory /var/www/groupware and enter exactly that when running the post-install script for Horde_Role.
          * You have a correct horde_dir set (verify by running pear config-show -c horde), but it's not correct received when running Horde. This was reported to happen with some web server setups if the user that is running the web server has a local PEAR configuration, e.g. a .pearrc in his home directory. This local configuration is overriding the system-wide configuration for the horde_dir. Remove that configuration, or use it to set horde_dir manually.

I suspect your issue is the last one.  The last person that reported this error message fixed it by correcting a typo (according to google).

Simon





More information about the horde mailing list