WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 13 months ago

Last modified 13 months ago

#23466 closed enhancement (wontfix)

In user selection WXR importer should not suggest importing to subscriber

Reported by: mark-k Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Import Keywords: close
Focuses: Cc:

Description

right now when associating a user from the WXR file with a wordpress user there is a dropdown containing all users. IMO there is no point in even offering associating with a subscriber as he will not be able to edit anything related to the imported content, and including subscribers can make the list needlessly long.

Change History (5)

comment:1 @SergeyBiryukov19 months ago

  • Milestone changed from Awaiting Review to WordPress.org

comment:2 follow-up: @jeremyfelt13 months ago

  • Keywords close added

A user's current role may be subscriber, but there may be reason to assign content authorship to them for historical or other reasons. I don't think we can make this decision at the importer level.

comment:3 in reply to: ↑ 2 @helen13 months ago

  • Milestone WordPress.org deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Replying to jeremyfelt:

A user's current role may be subscriber, but there may be reason to assign content authorship to them for historical or other reasons. I don't think we can make this decision at the importer level.

Agree.

comment:4 @mark-k13 months ago

Isn't "decisions not options" is the wordpress development moto now? Yes there might be some edge case in which you might want to import content to a user which doesn't have the privilege to edit it but I fail to imagine it. In practice on 99% of the wordpress sites subscribers are users created in order to manage mailing list or to be able to comment and for neither of these user types you will ever want to import content.

So maybe limiting it by role is really not the best option, so what about limiting it to users which have edit permissions or have posted content? This should probably cover even the edge case.

For the 0.5% of the use cases for which this will not work the explanation that "You need a user to have edit permissions to be able to import content for it" is both logical and easy to follow.

comment:5 @bi0xid13 months ago

In my opinion you are trying to complicate a simple task. The importer writes in database and follow your rules.

I had a case like the one @jeremyfelt is taking about. An user that now is not an active user, but that was an editor, who wrote content in a site. The role for this user is now subscriber.

Note: See TracTickets for help on using tickets.