#2665 closed enhancement (wontfix)
Xanga Archive Importer
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 2.1 |
| Component: | Import | Keywords: | |
| Focuses: | Cc: |
Description
I tweaked the livejournal importer around to get it to read in Xanga archives. Seems to work fine for the files I have access to. Only thing is that since there are no titles in the files I have, I used the date and time for the wordpress titles. Xanga has added in titles since the archive files I have so I have no way to test that part of it out. Other than that, it works great for the 3 people I've had try it out so far.
Attachments (5)
Change History (24)
#2
@
18 years ago
- Resolution set to wontfix
- Status changed from new to closed
Closing WONTFIX for now. As this likely needs additional maintenance and testing to check in.
Owner anyone?
#3
@
17 years ago
- Keywords archive added
- Resolution wontfix deleted
- Status changed from closed to reopened
- Summary changed from Xanga archive importer to Xanga Archive Importer
Old version was no longer working with WP 2.1.x.
Bugs:
Dates for posts and comments in the 1970's (parsing error) - CORRECTED
Timestamps still not parsing correctly - IN PROCESS 5/10/2007
#6
@
17 years ago
BUG CORRECTION - script was not parsing entries correctly; only importing first line.
Corrected as of 05-11-2007.
#8
in reply to:
↑ description
@
17 years ago
Be sure to download xanga_LATEST.php!
#9
@
17 years ago
- Keywords dev-feedback added; import xanga archive removed
Do we want to include a Xanga Archive importer in core, or is it plugin territory as importer plugins became possible in 2.3?
#10
@
17 years ago
For importers I think we should make as many core as possible. (It's an exception to our normal guideline of leaving things to plugins.)
#12
follow-up:
↓ 13
@
17 years ago
With alot of the recent changes from when the last patch was added here, is it possible for this importer to be updated? OR, will it still be okay the way it is, or what?
#13
in reply to:
↑ 12
;
follow-up:
↓ 14
@
17 years ago
Replying to spencerp:
OR, will it still be okay the way it is, or what?
I think thats it.. It looks to use wp_insert_post() and wp_insert_comment(), The API's shouldn't've changed any.
Why dont you give it a test and see if the importer still works? :) - A Test Export file might be useful to attach for non-Xanga users to test with too..
#14
in reply to:
↑ 13
;
follow-up:
↓ 15
@
17 years ago
Replying to DD32:
Why dont you give it a test and see if the importer still works? :) - A Test Export file might be useful to attach for non-Xanga users to test with too..
Oh geez, I never even used Xanga before. Hahaha. See, this is where it'd be awesome to have just anyone from the public come around and "try things out". Well, especially for things like this. I know there's probably alot of folks out there that used Xanga before. *cough* I just happen to be one of those folks that haven't. LOL!
#15
in reply to:
↑ 14
@
17 years ago
Replying to spencerp:
Oh geez, I never even used Xanga before.
Honestly, Its the same here, I've never even heard of it (Well, i probably have in passing). I'd gladly test it out if i had a example export though.
#16
@
17 years ago
Like some of the tickets with patches that need testing, I'd say... slap it in Trunk and it's bound to be "tested" eventually. That's partially the reason for "us" testers anyway. Heck, if all else fails, before release they can just revert back / remove the stuff that doesn't hold up to it's duties. =P
xanga importer