Jon Cave
Forum Replies Created
-
No problem. Probably tomorrow if not later today.
If you change line 469 of wordpress-importer/parsers.php from
$return = $wpdb->escape( trim( $return ) );to
$return = trim( $return );i.e. remove the call to $wpdb->escape(). It should work for you. The entire line can probably be commented out too.
If you change line 469 of wordpress-importer/parsers.php from
$return = $wpdb->escape( trim( $return ) );to
$return = trim( $return );i.e. remove the call to $wpdb->escape(). It should work for you. The entire line can probably be commented out too.
Unfortunately it seems that there’s a problem with the importer and some serialized values on some systems (without the simplexml or xml PHP extensions), see http://wordpress.org/support/topic/plugin-wordpress-importer-missing-serialized-meta-value?replies=4. Hopefully a fix will be available soon. Thanks for the report.
The importer attempts to use two different XML parsers included in PHP, but has a fallback to a regular expression based parser (yuck!). I tracked the issue down to this regex parser doing something funny to serialized values, but I’m not sure exactly why yet as it only seems to affect some meta values as you noticed. I’ll try to get a fix out soon.
Thanks for the report 🙂
I just tested it with the following post meta:
<wp:postmeta> <wp:meta_key>_custom_meta</wp:meta_key> <wp:meta_value><![CDATA[a:4:{s:5:"keyed";s:4:"with";s:7:"strings";s:3:"not";s:4:"with";s:6:"digits";s:4:"look";a:2:{i:0;s:8:"subarray";i:1;s:2:"yo";}}]]></wp:meta_value> </wp:postmeta>and it all worked fine. Automated tests also exist which test serialized meta being imported, so I don’t think it’s caused by the serialization alone.
Could you paste some unedited post meta that didn’t import? If a lot of text then use a pastebin like pastie.org.
Are you using the latest version of the importer (0.5.2 at time of writing)?
Can you perform any uploads to the website? Try uploading some media to find out. It might be that file uploads are blocked for some reason.
This is likely a permissions issue that is being incorrectly reported by the importer plugin. The actual error is that the uploaded file cannot be moved to the uploads directory. See http://core.trac.wordpress.org/ticket/19800 for further details.
Forum: Plugins
In reply to: [WordPress Importer] [Plugin: WordPress Importer] Importer BustedIt seems that this is caused by a bug in WordPress core. The actual error is that the uploaded file cannot be written to your uploads directory (permissions error), but it is being incorrectly reported by the importer plugin.
Check this core ticket for further details: http://core.trac.wordpress.org/ticket/19800
Forum: Plugins
In reply to: [WordPress Importer] Won't import attachment in WordPress 3.2@brohism: Did you select “All Content” whilst exporting or one of the filtered options (e.g. “Posts”)?
If it wasn’t All Content then you will not have had any attachments exported. This is currently a known limitation of the export/import process (http://core.trac.wordpress.org/ticket/17379).
If it was All Content then make sure that you checked the import attachments box during the import process. Also open up the XML file that you downloaded and check for attachments (you should be able to search for something like “<wp:post_type>attachment</wp:post_type>”).
Forum: Plugins
In reply to: [WordPress Importer] [Plugin: WordPress Importer] Importer BustedCan you tell me if you can find the <wp:wxr_version> tag in your export file. Open the XML file in a text editor (e.g. Notepad on Windows, vim on Linux) and try to find “wxr_version”. Then paste the whole tag and its contents here, e.g.:
<wp:wxr_version>1.1</wp:wxr_version>
If there is no such tag could you please email me the XML file you have? My address is: wp AT joncave.co.uk
Could you confirm that you receive the same error message as sheatsb. Thanks.
Forum: Plugins
In reply to: [WordPress Importer] [Plugin: WordPress Importer] Importer BustedThis works fine for me.
Have you tried disabling other plugins first. Is there any more information you could provide? (e.g. reported errors, what the screen looks like when it “fails”)
Yeah, sorry about that. I was on a plane trip the day after 3.3 was released. Expect an update to the plugin later today (I cannot do it right now as I’m waiting for some SVN issues to be resolved).
Forum: Alpha/Beta/RC
In reply to: WP 3.3 RC2 – RSS excerpt and content functions INOPThe rss2 feed works okay for me in testing. Have you tried disabling plugins and trying again? The wp-recaptcha plugin messes with the_content_rss and the_excerpt_rss, for example.
Forum: Alpha/Beta/RC
In reply to: Ctrl-BkSp Not Deleting Last WordThis is an upstream bug in TinyMCE and it looks like it only affects WebKit browsers. It has been reported to them and was fixed 10 days ago.
This is too late to be fixed for 3.3, but we might backport the fix for 3.3.1 and it will definitely be fixed by updates to TinyMCE in future versions.
Thanks for the report 🙂