This whole thing is puzzling because I created a test Silva instance from scratch and I didn't manually add an LDAPUserFolder, yet one was there whilst I was trying to document the process after I added that particular extension.
In fact, I have a screenshot from this (attached) which is a subtly different screen to that which is used if I manually create one (as you suggest) and then go in and edit it afterwards (notice the Zope mapping option, and the fact that the User ID Attribute option is missing from the form you get when you create one manually on arana now).
Has anything changed on arana that would make this behave differently? Maybe a different Zope LDAP product or another upgrade that has changed this behaviour in some way? Creating the acl_users folder manually is *not* the same process that I followed when I created my 'test' Silva instance previously.
This whole thing is puzzling because I created a test Silva instance from scratch and I didn't manually add an LDAPUserFolder, yet one was there whilst I was trying to document the process after I added that particular extension.
In fact, I have a screenshot from this (attached) which is a subtly different screen to that which is used if I manually create one (as you suggest) and then go in and edit it afterwards (notice the Zope mapping option, and the fact that the User ID Attribute option is missing from the form you get when you create one manually on arana now).
Has anything changed on arana that would make this behave differently? Maybe a different Zope LDAP product or another upgrade that has changed this behaviour in some way? Creating the acl_users folder manually is *not* the same process that I followed when I created my 'test' Silva instance previously.