Deleted user still associated with posts
-
I deleted a user from a blog and selected the “reassign” content option. Received the success message after hitting ‘Delete’. Verified user not part of site anymore.
However, their content was not reassigned; it’s still associated within the site to them.
Does anyone have info on why the reassign content function doesn’t actually work as described/expected? That content isn’t reassigned, leaving an interesting orphan situation?
Is it because the user still exists within WP-at-large and therefore isn’t really deleted and can still own content? Grasping for answers.
-
Hi there,
Can you please let me know your site’s address so I can point you in the right direction of getting support?
Please note that these forums are for WordPress.com hosted sites only. If your site is using the open source WordPress.org software you need to seek help at these forums:
-
This is the correct forum. I don’t own the site and am not authorized to provide. It’s on a free plan, and all posts involved are 2017 or earlier. There are also numerous users who were deleted previous to my involvement but who are still ‘attached’ to published posts.
-
Does anyone have info on why the reassign content function doesn’t actually work as described/expected? That content isn’t reassigned, leaving an interesting orphan situation?
It normally works. There might be a glitch, but without knowing the site or which user was deleted it’s tough for us to find that.
I do see you have a test site where you removed a test user. Would you mind if we try removing the user from our end to see if we can duplicate what you’re seeing?
-
No, I don’t mind but it’s wasted effort. My personal account is not related to this situation. As stated previously, I’m not authorized to provide the site (multi-author and many years of content) involved. I can privately if that is possible? I saw no option to do so unless on a business plan.
We thought this would be something others have encountered in the past but appears not or no one has noticed.
Just seems like there’s an obscure condition(s) within the delete user processing that is causing the reassignment to be ignored. Like maybe it recognizes the content is to be kept b/c the radio button is selected but then just skips on to deleting the user?
-
Just noting I went ahead and did some testing on one of my own sites, and was able to duplicate the issue. I’ve filed a bug report here:
https://github.com/Automattic/wp-calypso/issues/32079 -
Thank you!! I really appreciate your testing and filing a bug report. Will monitor and see what pans out.
-
You bet. And if you are needing help with the other unmentioned site in the meantime, would you be able to log in as an admin and then try to reach support here?
If the site has a paid plan, that will take you to private support. Just mind the form posting message to be sure it won’t be posted publicly or to a community member.
-
Tx but it’s a free plan so no go.
Is there a way to get some movement on the bug report tho?
-
Our developers prioritise bug reports based on the severity of the issue and how many people it affects, and we are not able to make a particular report jump the queue, as it were. So unfortunately I cannot give you a timeline on when this might be fixed.
-
Fair enough, but has it been established if it is a fix? Or, is it functioning as WP expect it to, even tho WP instructions / documentation are incongruent with what actually happens? Stuff happens, I get it.
This is the info I’m looking for at this point, as it will provide instruction on we proceed on our end going forward. Not to mention, it will aid in considering what to do with our existing ‘orphan’ data if there is a fix.
Since this potentially impacts every past, current, and future non-Jetpack multi-user site, I’d think it worthy of ‘some’ movement.
-
Fair enough, but has it been established if it is a fix? Or, is it functioning as WP expect it to, even tho WP instructions / documentation are incongruent with what actually happens?
We don’t know, as our developers have not investigated the cause yet. When there’s an update on the bug report, we’ll let you know, but for now we have no further information on this.
This is the info I’m looking for at this point, as it will provide instruction on we proceed on our end going forward. Not to mention, it will aid in considering what to do with our existing ‘orphan’ data if there is a fix.
If you provided the URL of the actual site, we can take a look and might be able to help you fix things. But without any further details we cannot help.
There is no database access on WordPress.com, so no way for you to fix this yourself. The only thing that might work is to assign an author to the posts manually by editing the individual posts. You can do this using the bulk-edit feature at Posts ->All Posts in WP-Admin.
https://en.support.wordpress.com/posts/edit-posts-screen/#bulk-edit
- The topic ‘Deleted user still associated with posts’ is closed to new replies.
WordPress.com Forums 