OST 1.10 "Lookup or Create User" bug..

[philbertphotos]

In the "Lookup or Create User" dialog box only pre imports user data if they are local it seems to ignore the LDAP/remote users and does nothing and just refreshes.

[greezybacon]

Would you be able to test the patch in osTicket/osTicket-plugins#85?

[philbertphotos]

Yes I can

Sent from my iPhone

On Sep 24, 2015, at 10:10 PM, Jared Hancock notifications@github.com wrote:

Would you be able to test the patch in osTicket/osTicket-plugins#85?

—
Reply to this email directly or view it on GitHub.

[Mbatey88]

I'm having this issue as well. I would like to test the patch, but i'm not sure how to re phar the files after i've extracted and edited the authentication.php file. I used unphar.com to convert the auth-ldap.phar to a zip so i could edit the files. How do i put them back into a phar?

[Mbatey88]

After some digging I've finally found the cause of this problem.

I started with the v1.10-rc2 branch and started adding commits from the develop-next branch one by one until I found which one broke the user lookup from LDAP when creating a new ticket via the agent panel. It seems that the culprit is commit 2763707 from #2479.

[kest874]

Can confirm this is broken again.

[philbertphotos]

IS there is fix for this?

[ntozier]

Plugins are usual updated after a release. (Or just before)

So I doubt it.
On Mar 17, 2016 1:22 AM, "Joseph Philbert" notifications@github.com wrote:

IS there is fix for this?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#2582 (comment)

[philbertphotos]

Wait you mean the actual plugin has to change but in what way?? I can easily alter my plugin but i need to know what changed:

Sent from my iPhone

On Mar 17, 2016, at 3:48 AM, ntozier notifications@github.com wrote:

Plugins are usual updated after a release. (Or just before)

So I doubt it.
On Mar 17, 2016 1:22 AM, "Joseph Philbert" notifications@github.com wrote:

IS there is fix for this?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#2582 (comment)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub