| Summary | Overwriting include_path in core.php |
| Queue | Horde Groupware Webmail Edition |
| Queue Version | 1.2.2 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | rdorfner (at) sysdesign-edv (dot) de |
| Created | 04/08/2009 (5935 days ago) |
| Due | |
| Updated | 04/17/2009 (5926 days ago) |
| Assigned | |
| Resolved | 04/16/2009 (5927 days ago) |
| Milestone | |
| Patch | No |
groupware bundle.
But why no create a new item in the Configuration "PHP Settings"
section (horde config.php), e.g. "Additonal Include Paths" and use the
values/variable to expand the path?
Advantages:
- Furthermore "clean" include_path
- Flexibility to expand it within configuration panel
Disadvantages:
- some work to implement
complete, well defined package of components. We don't want any
interference with outside PEAR installs. If you need more
flexibility, install the Horde applications separately.
State ⇒ Rejected
complete, well defined package of components. We don't want any
interference with outside PEAR installs. If you need more flexibility,
install the Horde applications separately.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Groupware Webmail Edition
Summary ⇒ Overwriting include_path in core.php
Type ⇒ Enhancement
State ⇒ New
"include_path" within apaches VHOST directive.
Unfortunately, horde overwrites the whole "include_path" in core.lib.
lib/core.php:
ini_set('include_path', dirname(__FILE__) . PATH_SEPARATOR .
dirname(__FILE__) . '/../pear' );
Should it not be better to expand the "include_path" like with
something like that?
ini_set('include_path', dirname(__FILE__) . PATH_SEPARATOR .
dirname(__FILE__) . '/../pear' . PATH_SEPARATOR . get_include_path());