TOPIC:

Right, it's working, but I think I've found a few issue on the way

First the fix
The root of the issue is hosting in Azure which doesn't have the ldap library, for anyone else reading this it's a simple fix

1. Upload the php_ldap.dll (also libeay32.dll and ssleay32.dll) to a folder in the root of the website called bin
2. In the azure portal add an application setting called "PHP_Extensions" with a value of "bin/php_ldap.dll"

The problems
1. The ldap.php file is still looking for settings in the ldap table, but the management screen is saving to sitedetails, I needed to edit the table directly
2. I still cant get logging to work, I ended up putting in my own code in ldap.php to log out the debug messages

Just found logs!

In azure when you FTP in there is a folder called LogFiles in the FTP root, in there I found a file called php_errors which seems to have all the debug messages and errors.

These are the webserver error logs which (obviously) are very usefull.

It seems that something else is not installed that prevents xerte from wrinting it's own debug.log.

In 3.0 the case that the ldap data is in site_details and not in the ldap table really should be ahndled correctly. I'll check the code again. You should not have to edit the ldap table yourself (but of course it helps, because ultimately, that's where the Ldap.php code reads it's configuration from)

Solved the debug logging issue too, looks like it's probably a windows only issue. Writing to "/somefile/path.ext" isn't allowed, but "somefile/path.ext" with the the "/" at the start does work.

E.g. "/tmp/debug.log" needs to be changed to "tmp/debug.log" in Windows.

Thanks
Fran

Windowsve ... that should have triggered it for me too.

You can d:/tmp...

If you use / as the first charcter it will try to write to the current defailt drive, whatever that happens to be.