To spare you a long story about how Windows locates dlls to load, the path C:\Program Files\OSGeo\MapGuide\Web\Php is not a known path to look for dependent dlls to load under a default MapGuide/Apache configuration.
Thus if there are possibly dependent dlls in this path that certain PHP extensions need, they have to be explicitly loaded through LoadFile directives in httpd.conf That's what the preceding LoadFile directives are there for, to make sure all the dependencies of the PHP MapGuide extension (php_MapGuideApi) are satisfied so that it works out of the box. Your Oracle and SQL Server examples are I assume because said dlls sit in $INSTALL\Server\Fdo, which MapGuide already is configured to know to look for dlls in that location. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/MapGuide-Open-Source-v3-1-LDAP-Fails-to-Load-tp5307623p5307956.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
