WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

#15579 closed enhancement (fixed)

Add XML mention to WP import instructions

Reported by: rosso99 Owned by: duck_
Milestone: WordPress.org Priority: normal
Severity: normal Version: 3.0
Component: Import Keywords: ux-feedback has-patch needs-testing
Focuses: Cc:

Description

When exporting from WordPress, there is mention of both an .XML file and WXR:
"When you click the button below WordPress will create an XML file for you to save to your computer.

This format, which we call WordPress eXtended RSS or WXR, will contain your posts, pages, comments, custom fields, categories, and tags."

But when you import a WP file, there is no longer a mention of .xml - I think this is confusing for novice users (I just walked one through the import) as they have a .xml sitting on their computers:

"Upload your WordPress eXtended RSS (WXR) file and we’ll import the posts, pages, comments, custom fields, categories, and tags into this site.

Choose a WordPress WXR file to upload, then click Upload file and import."

I suggest adding a line to the import text like:

Choose a WordPress WXR file (this file will end in .xml) to upload, then click Upload file and import.

Attachments (1)

wordpress-importer_diffSR.txt (798 bytes) - added by rosso99 3 years ago.
patch for wording change

Download all attachments as: .zip

Change History (8)

comment:1 dd323 years ago

  • Keywords ux-feedback added; naming nomenclature user instructions removed
  • Milestone changed from Awaiting Review to Future Release

rosso993 years ago

patch for wording change

comment:2 rosso993 years ago

  • Keywords has-patch needs-testing added

I made the change by adding (.xml) into the wording:

"Choose a WordPress WXR file (.xml) to upload, then click Upload file and import. "

This should be easy to apply to all branches since it won't require further translation but rather just insertion at the proper point.

comment:3 westi3 years ago

  • Owner set to duck_
  • Status changed from new to reviewing

comment:4 nacin3 years ago

  • Milestone changed from Future Release to WordPress.org

In the future please upload patches as .patch or .diff so we get the full syntax highlighting. Congrats on your first patch :-)

comment:5 follow-up: rosso993 years ago

Ah, sorry didn't know about that .diff - best to update our Codex - it says:
http://wordpress.org/download/svn/

"You can output this to a file by using redirection:

svn diff > my-patch.txt"

I will see if we can add underneath that:

"If you're submitting a patch for review to Trac, be sure to use .patch or .diff as the file extension so full syntax highlighting is preserved."

comment:6 in reply to: ↑ 5 nacin3 years ago

Replying to rosso99:

Ah, sorry didn't know about that .diff - best to update our Codex - it says:
http://wordpress.org/download/svn/

"You can output this to a file by using redirection:

svn diff > my-patch.txt"

I will see if we can add underneath that:

"If you're submitting a patch for review to Trac, be sure to use .patch or .diff as the file extension so full syntax highlighting is preserved."

Fixed and currently deploying.

comment:7 duck_3 years ago

  • Resolution set to fixed
  • Status changed from reviewing to closed
Note: See TracTickets for help on using tickets.