WordPress.com Webinars: Making Money – July 2021
In this video, you’ll learn everything you need to know to launch your website on WordPress.com.
I recently discovered after trying to import WordPress XML files for a customer that you can use xmllint (within the Command Line or iTerm) to check the validity of the files.
The error message looked like this:
Invalid XML on read in WXR_Large_File_Parser::__construct() for file:///nfs/6a2/156107206/files/2019/01/site-address-here.wordpress.2019-01-09.001.xml_-3.txt (size: 11335507)
After a colleague suggested xmllint, I opened iTerm (equivalent to the Command Line), then made sure to change the directory to where the file were located. For example:
/cd ~/Desktop xmllint --valid filename.xml
Two files were checked and one of the files produced the following error:
If anyone can translate the error messages (from the screenshot), please let me know!
In the end, I tried the import file again but decided to split the first file 11.3 MB using a WXR splitter and all files were successfully imported. 🎉 🤓
Just a quick note to share the news that yesterday was my first official day as a Happiness Engineer for Automattic. The awesome company behind WordPress, Jetpack, Akismet and a whole bunch of cool products.
As many of you know, I’ve always been a huge fan of WordPress so after working at Sydney University for 12 years, let the new adventures begin…