Closed (cannot reproduce)
Project:
Lightweight Directory Access Protocol
Version:
7.x-2.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Mar 2016 at 15:13 UTC
Updated:
18 Nov 2017 at 14:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
Saoirse1916 commentedAdding a few more screenshots indicating that the LDAP query works fine as does the view which calls it -- it's the feed that's the problem, as it only imports 1 node with no title.
Comment #3
Saoirse1916 commentedFor testing, I've changed the import to pull all users into Drupal (including the office name) which works just fine. That would lead me to believe that the problem lies in the Node Processor section, as the User Processor works with the LDAP query.
More specifically, the problem has to do with the combination of LDAP Query Fetcher and Node Processor, as LDAP Query Fetcher/User Processor works as does Drupal User LDAP Entry Fetcher/Node Processor.
Comment #4
martin.knapp commentedI think I have the same problem. I want to set up a query to import LDAP users as Drupal nodes (the idea is to display the members of an agency, but not to provide them with login credentials).
I have :
First thing I notice is that when I try to execute the Feed via cron, nothing appears to happen (the job executes very fast - much too fast for it to have executed the LDAP query, which is long).
I therefore try to execute the Feed via "form submission".
When I first created the Feed, I tried to put the "displayName" LDAP attribute into the Title field of the Agent content type and to make this the unique identifier. However when I submitted the "Create agent" form, I then got an error to the effect that it was unable to match the Title field.
So I tried again, installed Automatic Node Title module to generate a title, and put the displayName into another field.
This time, I got a better result. The return message was "1 node created, 22 updated" - so at least something is getting into the system! But what appears to be happening is that no account is taken of the unique ids. The first entry causes the node to be created, all the others cause it to be updated despite the fact that their unique identifiers (DN => GUID) are different.
Here is the Feed configuration:
Comment #5
Saoirse1916 commented@martin.knapp glad to see I'm not the only one struggling with this!
Comment #6
grahlJust tried to reproduce this and it works fine, here is my minimal example with mail, name and guid set:
See also https://www.drupal.org/docs/7/modules/lightweight-directory-access-proto...