| Summary | Horde5 webmail-install script fails when installing into seperate pear |
| Queue | Horde Base |
| Queue Version | 5.0.1 |
| Type | Bug |
| State | Unconfirmed |
| Priority | 1. Low |
| Owners | |
| Requester | daniel (at) daniel-ritter (dot) de |
| Created | 11/08/2012 (193 days ago) |
| Due | |
| Updated | 11/09/2012 (192 days ago) |
| Assigned | |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch | No |
separate pear environment?
Probably you will find config data as:
...s:14:"pear.horde.org";a:1:{s:9:"horde_dir";s:15:"/var/www/horde4";}...
change that to:
...s:14:"pear.horde.org";a:0:{}...
and now you could manage both installations as expected.
separate pear environment?
I installed Horde 5 into a seperate PEAR following the instructions
in the INSTALL document.
There is already a Horde4 installation in production on the machine,
so a seperate PEAR was needed.
The webmail-install script failed for me, because
require_once PEAR_Config::singleton()
->get('horde_dir', null, 'pear.horde.org') . '/lib/Application.php';
always resolved to the path of the existing horde installation. I
was following the instructions in the INSTALL document, setting the
environment variable for PHP and PEAR, before running the script,
but it always resolved to my old Horde installation.
I fixed it quick and dirty by putting the right path into the script.
require_once "/var/www/horde5/lib/Application.php";
require_once PEAR_Config::singleton()
->get('horde_dir', null, 'pear.horde.org') . '/lib/Application.php';
always had /var/www/horde4 as result.
separate pear environment?
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ Horde5 webmail-install script fails when installing into seperate pear
Type ⇒ Bug
Priority ⇒ 1. Low
I installed Horde 5 into a seperate PEAR following the instructions in
the INSTALL document.
There is already a Horde4 installation in production on the machine,
so a seperate PEAR was needed.
The webmail-install script failed for me, because
require_once PEAR_Config::singleton()
->get('horde_dir', null, 'pear.horde.org') . '/lib/Application.php';
always resolved to the path of the existing horde installation. I was
following the instructions in the INSTALL document, setting the
environment variable for PHP and PEAR, before running the script, but
it always resolved to my old Horde installation.
I fixed it quick and dirty by putting the right path into the script.
require_once "/var/www/horde5/lib/Application.php";
require_once PEAR_Config::singleton()
->get('horde_dir', null, 'pear.horde.org') . '/lib/Application.php';
always had /var/www/horde4 as result.