Rationale for include_path change?

- ☆ A M B ☆
- 209 Posts
pbowyer Reply #1, 19 years, 3 months ago
Hi,

I wrote a module that relies on external libraries (PEAR in this case), and ran into problems with the way the manager changes the include_path. Specifically lines 82&84 of manager/index.php, they restrict the path to [tt]manager/includes[/tt] only.

I have changed these lines manually in my install and would like to propose the following replacements for future versions:
```
if(version_compare(phpversion(), "4.3.0")>=0) {
    set_include_path($incPath . PATH_SEPARATOR . get_include_path()); // this now works, above code did not?
} else {
    ini_set("include_path", $incPath . PATH_SEPARATOR . ini_get('include_path')); // include path the old way
}
```
Regards,
Peter
MAPLEDESIGN MODX development and MODX web design and custom development. Proud to serve UK and International clients!