I did apply the patch to the core as suggested.
The only effect I got is the pointed user is disabled, not deleted.
I can't tell whether the reason for the mentioned problem is I didn't use the administration theme. Anyway I noticed when an administrator asks for a user deletion he is asked something like whether he wants to delete all data related to the user or not. In other words users deletion does not look like a one-step process, though letting a sub-admin user to delete users does not offer that choice. Not so bad for me, if only I could actually delete users with a sub-admin user! ;-)
Thanks in advance!
Andrea
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 06-outcome.png | 38.98 KB | appleaday |
| #3 | 05-options.png | 30.29 KB | appleaday |
| #3 | 04-selections.png | 73.31 KB | appleaday |
| #3 | 03-bulkactions.png | 26.64 KB | appleaday |
| #3 | 02-view.png | 9.41 KB | appleaday |
Comments
Comment #2
adamps commentedFor a good bug report you need to describe the sequence of steps you took, what you saw and what you expected to see. Bear in mind that this modules does work in the mainline case for other users. Therefore you need to identify what specifically makes it not work for you.
My guess is that your sub-admin does not have permission "Select method for cancelling account".
Comment #3
appleaday commentedYou're perfectly right, AdamPS, I apologize for being so sparing with information. Yesterday I was terribly tired and frustrated and I meant to hurry up in asking for help. I try to mend for that by supplying an ordered sequence of snapshots I just took in order to reproduce the problem. I'm referring to a user who has been assigned the role "CRM Manager". The list of users is made with a clone of the display of the view that comes with the installation of the module (showed in one of my scraps). This time I got the choice concerning the data of the user being canceled, but the outcome is the same: the user is successfully disabled, instead of canceled.
Is there anything else I can supply?
Thanks in advance!
Andrea
Comment #4
adamps commentedHi Andrea no need to worry and I should have said: thank you for trying out the module. Everything is a bit more difficult with a core patch and alpha releases, but if we all work together we will get there.
On image 3, I see 7 actions selected, which seems odd. Did you select "Cancel the selected user account(s)"?
On image 5, it's not in English and I can't read it! I see the second option selected, which on my system is "Disable the account and unpublish its content." If you want to delete the account instead of disable, you will need to pick either the third or fourth item:
Comment #5
appleaday commentedAdamPS > On image 3, I see 7 actions selected, which seems odd. Did you select "Cancel the selected user account(s)"?
Yes, I did, as you can see that's the fifth checkbox. The extra action come from the existance of a "CRM Manager" role. Actually I granted the sub-admin user (a "CRM Manager") everything but the chance to make anyone administrator or revoke that priviledge. Of course, I might have done the reverse condition ("grant all except the option selected"), in that case you would have seen just two checked boxes.
Concerning the second remark, I'm sorry for the Italian, anyway you are right: I mistakenly chose a "disable" option and the reason I went wrong is the fourth option is involving the anonymous user and that didn't sound like a complete removal, and the last option in my case is not simply "delete the account and its content" but instead something like - I translate from the Italian without changing the language back to English - "use a confirmation email in order to delete the account", and that, as well, didn't sound like the "delete the account right away" as I had in mind.
I recognize whatever comes for that final multiple choices is not due to the module, so eventually my reporting my case as a bug was definitely improper. In fact by selecting "Delete the account and make its content belong to the Anonymous user." I could actually delete the account - though I can't tell now how the Anonymous user could possibly show up as a consequence of that deletion. Anyway, I'm sorry! I'm happy to see my issue has been correctly categorized as "support request".
I hope my report will anyway help somebody not to make the same mistake! ;-)
Many many thanks anyway! :-)
Andrea
Comment #6
adamps commentedNo need to be apologetic Andrea. As you say the community benefits as one person getting confused can help the next one understand.
I realise that the permission "Select method for cancelling account" is not documented in this module's README/help. I will fix that and have changed the issue to cover that.
There is one thing that you could do to help. Now that you have tested the patch for #2854252: User forms broken for admin without 'administer users', I would be very grateful if you could set the status to "Reviewed and Tested by the Community".
Comment #7
appleaday commentedI'm still willing to help, AdamPS, though, for the sake of comprehension I have to ask: since I used core 8.5.0 patched with the supplied patch, and module 8.x-2.0-alpha5, what is the connection with 8.6.x-dev core and 8.x-2.0-alpha3 module mentioned there?
Thanks!
Andrea
Comment #8
adamps commented@AppLEaDaY Thanks for the offer to help.
According to #64, AUBR 8.x-2.0-alpha5 is the version to test with so you are OK for that part.
It is a good point about the version of core. Luckily at the moment 8.5.0 and 8.6.x-dev are the same in the areas relating to the patch, so the same patch works for both. The automatic tests run on 8.6.x-dev so we know that it is working. I suggest that you could add a comment to say you have tested the patch and be very clear that you tested with core 8.5.0. You can set "Reviewed and Tested by the Community", and if anyone has any concerns they can raise them.
It will be a great help to everyone using AUBR if we can get the patch accepted, and hopefully if we all work together towards it we can succeed.
Comment #10
adamps commented