Closed (works as designed)
Project:
Wordpress Import
Version:
6.x-2.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
6 Sep 2010 at 17:44 UTC
Updated:
26 Dec 2010 at 22:23 UTC
Running the import gave an error, so I deleted all instances of wp:meta_value as per the readme.txt and there were no instances of atom:link
I re-ran the export from Wordpress after having deactivated all plugins then re-ran the import and it still fails.
# warning: XMLReader::read() [xmlreader.read]: /usr/local/tmp/wordpress.2010-09-06_4.xml:2: parser error : XML declaration allowed only at the start of the document in /home/.krone/dubber/test07v2.lightbeingcreations.org/sites/default/modules/wordpress_import-6.x-2.1/wordpress_import/wordpress_import.module on line 1424.
# warning: XMLReader::read() [xmlreader.read]: <?xml version="1.0" encoding="UTF-8"?> in /home/.krone/dubber/test07v2.lightbeingcreations.org/sites/default/modules/wordpress_import-6.x-2.1/wordpress_import/wordpress_import.module on line 1424.
# warning: XMLReader::read() [xmlreader.read]: ^ in /home/.krone/dubber/test07v2.lightbeingcreations.org/sites/default/modules/wordpress_import-6.x-2.1/wordpress_import/wordpress_import.module on line 1424.
# warning: XMLReader::read() [xmlreader.read]: An Error Occured while reading in /home/.krone/dubber/test07v2.lightbeingcreations.org/sites/default/modules/wordpress_import-6.x-2.1/wordpress_import/wordpress_import.module on line 1424.My XML file (renamed to .txt) is attached
| Comment | File | Size | Author |
|---|---|---|---|
| wordpress.2010-09-06.txt | 376.87 KB | Dubber Dan |
Comments
Comment #1
Dubber Dan commentedAny suggestions folks?
Comment #2
1kenthomas commentedI've had similar issues. Breaking the WordPress export in to smaller chunks (by date, for example) seems to resolve.
Good luck!
Comment #3
bgogoi commentedBreaking the WP export into year by year chunks helped me pinpoint the errors and fix:
-- there were few sql injected data redirecting to some spam sites!!! -- I removed them -- I think my anti-virus played an important role .. I disabled and did some fine-replace for display:hidden (thats how the injected codes were!), overflow:hidden, etc etc.
-- in 2/3 places, there were non-UTF characters -- I removed them
-- I will now do a fresh import ...
BUT now my challenge is how to add a < br /> or < p > .. as WP data has no < br > or < p > tags in between paragraphs ..
While importing, how to set the default input type into : basic ,, instead of full html?? wish there would hv been a option for this too in the module!
Thanks a lot.
Comment #4
bgogoi commentedOK, after importing I fixed the formating issue by editing the Input Type "Wordpress format" -- HTML corrector and Line Break converter checked :)
Comment #5
bgogoi commentedThe import I was doing into a ProsePoint version of Drupal.
ok. after the import, formating, issues --- I just found that the workflow for each imported stories were set to Draft (which is `sid` is teh workflow table)
From my phpMysqlAdmin, I changed the SID's of each NID's with
UPDATE workflow_node (also of `workflow_node_history`)
SET `sid`=4
WHERE `sid`=2
BUT that didn't help me.... The nodes are still not accessible for public!
Any idea, please?
Comment #6
lavamind commented@Dubber Dan : There's an extra line return at the beginning of your WXR file. I'm not sure how it got there. Remove it and it should work fine.
@bgogoi : I can't help you with this, you should submit this problem to the maintainers of ProsePoint Drupal.