User not being set through CLI

[boblmartens]

Trying to commit to a page via the CLI results in a "1" being set as the user. It looks like something is happening at inc/cli.php at line 424 where if you supply a user, it will just set it to true and be done. I changed it to 5 for fun and has "5" in the commit logs for the page when supplying a username.

Wondering if this is a known issue when using LDAP as the authentication plugin or something else. Thanks!

[boblmartens]

Thanks. I'll give this a test and let you know if it is fixed.

[boblmartens]

I'm now getting this:

E: Unable to obtain lock for [page name]

Even after unlocking I still get that same error message even when not specifying a user. Are there other commits I need to bring over?

[boblmartens]

I should also state that I am more than willing to attempt any changes you would like me to do.

[mclei-asw]

Removing this line from dwpage.php:
$SERVER['REMOTE_USER'] = ''.$this->username.'_';
causes that next "checklock" reports no lock because lock is held by the same user. But in this code it assumes it returns that file is locked correctly.

[yodahome]

I do get the same problem when trying any commits. When making the commit as root (as it was done usually) the script reports
E: Unable to obtain lock for intern:lmc2:20151014axyz
and when I then use another user it reports
E: Page intern:lmc2:20151014axyz is already locked by another user

Lockfiles seem to be there.
I'm using Release 2015-08-10a "Detritus"