Jo, I'd recommend getting one of the 2 things working first not trying to combine the loop and the update until you know you can update 1 user. I've provide something (untested) to try below. Hope its helpful but its been years since I wrote one of these.
<dyn> <!-- start with a known user to simplify complexity of not confusing the loop with the update user --> <rde-dm:attribute mode="write" source="request" attribute="userlogin" value="expert" /> <rde-dm:user mode="load" user="[#request:userlogin#]" /> <rde-dm:attribute mode="write" source="user" attribute="rde-edit-user.rde-attributes.test.telephoneNumber" op="set" value="020 28283498" /> <!-- visually validate the tree of attributes updated as expected - debug only --> <rde-dm:user/> <!--- you had test so it was trying to update the user making the HTTP calls test attribute. the paths not really needed from samples in the manual --> <rde-dm:user mode="update" path="rde-edit-user.rde-attributes.test" /> <rde-dm:attribute mode="flush" /> <!-- not sure what you had this all wrapped in a user tag. User is called as an empty tag usually your code may have been ignored --> </dyn> -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/-4DIhcljp3IJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
