Support Forum
When a user on the WP side is deleted, WP offers to reassign posts to another existing members, before really deleting that user, as an alternative to wiping out also that user's submitted posts and links. That proves a very useful feature when e.g. there's a problem with that user's database record and you just need to delete and re-create; it avoids that all existing posts end up in unassigned limbo.
Of course, this does require that the new user has already been created before deleting the old one and take over that old one's posts.
No idea how complex this is - but my suggestion would be to essentially hook into that "last chance to reassign" routine, and offer to also (or separately) reassign all SPF posts created by the old user.
Currently, all existing posts on the SPF side end up assigned to a "guest" type user, with a blank user profile.
The main problem is that oddly and annoyingly WP provides no hooks on the wp delete user admin page. This means we can not collect data on the user to be deleted and take action accordingly.
We have this as an open ticket and, co-incidentally, it was only a couple of days ago I performed another check of the options to see if WP 3.3.1 had given us anything new to work with and sadly they still have not.
There is a possibility (and this is something I do plan to try) of cutting into the flow AFTER a user has actually been removed by WP and we may be able to do so before the SP removal. One of the even more annoying factors here though is if a re-assignment of WP posts has been ordered then that data is NOT passed into the post-delete hook by WP so we would have to ask for that information again which is sloppy and should be unnecessary.
This just all seems to be an area that the WP team believe a plugin should not get involved in! But I assure you that when we can we will do something.
YELLOW
SWORDFISH
|
yes, we can get notice of the deletion right before it occurs... we cannot stop or alter it, but we can take action on what is about to happen...
thankfully, its better than the user delete action we use now to remove the sp data...
we do have an open ticket to allow reassignment of posts to someone else, just no chance for us to work it... small team...
Visit Cruise Talk Central and Mr Papa's World
Aha, that's clear as a bell, that explanation.
Maybe, as a sorta kinda stopgap solution, this is a workaround: to create that "ID / post takeover" function - obviously strictly a "super-admin" capability - so that admins can reassign before proceeding to delete the "old" (at that point, shell) user.
Dunno.
It's just that those orphaned posts, particularly on more busy forums, can create some confusion - think e.g. with older posts, that are dredged up via a search, to which one wants to respond, or send a PM to its author...
Anyway - given the explanation I fully understand it's anything but a piece of cake.
It'd just be a very handy membership management tool, methinks.
Having said that: thanks for the thorough explanation!
np. glad to explain. we will get it changed up, just perhaps not before 5.0 release... we really need to get this sucker out there...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)