Notice: Undefined variable: synch_context in ldap_user_ws() (line 39 of ldap/ldap_user/ldap_user.ws.inc).

CommentFileSizeAuthor
#1 undefined_synch_context-1572118-1.patch603 bytesmallezie

Comments

mallezie’s picture

mallezie
Primary language Dutch
Location Loenhout
commented
StatusFileSize
new undefined_synch_context-1572118-1.patch603 bytes
johnbarclay’s picture

johnbarclay commented
Title: create user through webservice: undefined variable: synch_context » LDAP User: create user through webservice: undefined variable: synch_context

Thanks. Appreciate it. Simpletests aren't even finished for the 7.x-2.x branch. If you are just trying to get a sense of the module, that's great and appreciate the patch. If you are trying to get a site up and running, stick with the 7.x-1.x branch and subscribe to #1115704: Drupal 7 Status Updates

mallezie’s picture

mallezie
Primary language Dutch
Location Loenhout
commented

I was actually looking to see the status on provisioning.
But it seems i will probably be able to do most with feeds. Which i will check in te 7.1 version.
If i should need to use provisioning, i'll try to update patches for version 2. But i already send this patch, before realizing it was stil highly in development (seeing al debug messages).
BTW: to enable your webservices, you only have one bug, that your user name isn't passed to user_save.

I fixed it in ldap_user.ws.inc by adding the drupal_user_name to the user_edit variable.
You can create new user in LdapUserConf with $account = user_save($account, $user_edit);

If there are places where i can help with 2.x version. Please let me know.

johnbarclay’s picture

johnbarclay commented

I'm focused on getting the synch and provision actions to be executed at the correct time based on the way things are configured and the user interface for the mapping. Help on the two functions themselves would be the most useful:

ldap_user_synch() and $ldap_user_conf->provisionDrupalAccount
ldap_user_provision() and ldap_user_conf->synchToDrupalAccount

I think feeds is the best approach and originally was going to make it a requirement for ldap_user, but couldn't get any commitment to a roadmap let alone a timeline on feeds. It will likely needs some feed tamper code to deal with puid, username, email, etc but that should be able to leverage some functions in ldap_user.

johnbarclay’s picture

johnbarclay commented
Status: Active » Fixed

I committed this with a general daily commit of head.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.