RSS import not working

Neil,

I was helping a friend migrate a Blogger blog (which uses Atom) to WordPress. I couldn’t use the Blogger importer, as I couldn’t reach her for the account password, so I found myself in the same position as you. Here is what I did, and it worked for me:

1) You need to find an XSLT processor. If you’re on a Mac, you’re in luck: download TestXSLT from entropy.ch at https://www.entropy.ch/software/macosx/welcome.html. If you’re on a PC, you should be able to find something similar.

2) Download this Atom to RSS XSL template: https://atom.geekhood.net/atom2rss.xsl

3) Use your Atom file as the source XML file.

4) Use atom2rss.xsl as your style sheet.

5) Process. The result is an RSS file that you can import into WordPress.

Thank you very much for your reply!

That has taken me a huge step forward! I can convert the xmp, import it and all the entries are there with the correct links and the correct dates. Unfortunately, the full entries are not imported. All links to images (inline within the posts) have been stripped, and only the summary of the post text is shown.

I assume this is by the design of the XSL sheet you linked for me. Is there a version that preserves the images and the full post text?

If you can help me get this working I’d be happy to help you out in whatever way I may be able to, somehow! I wish I could buy you a drink ??

Looking at that XSLT file, I see this:

<x:choose>
	<x:when test="atom:summary">
	<description>
<x:apply-templates select="atom:summary" mode="asHTML"/>
<x:if test="atom:content"> (...)</x:if>
</description>
</x:when>
	<x:when test="atom:content">
	<description>
<x:apply-templates select="atom:content" mode="asHTML"/>
</description>
</x:when>
</x:choose>

Note that it’s using description for both the summary and content there. Try changing the content (second piece) to use <content:encoded> instead of <description>. Then convert your feed and import that. Might work better given the way WordPress’s import works.

Thanks for the reply. I tried what you suggested, and this is how the xsl in question looked after the change:

<x:choose>
		<x:when test="atom:summary"><description><x:apply-templates select="atom:summary" mode="asHTML"/> <x:if test="atom:content"> (...)</x:if></description></x:when>
		<x:when test="atom:content"><content:encoded><x:apply-templates select="atom:content" mode="asHTML"/></content:encoded></x:when>
	</x:choose>

Is this correct?

Unfortunately, the same thing seems to have happened. The images are stripped and only the summary is shown in the post.

What does the resulting RSS feed look like though? It’s really hard to tell you what to do when we have zero information about the results of what we tell you are.

BTW, that’s why you had such a hard time getting any responses in the first place. Not enough information. You have to spill your guts, the more info you give, the more likely somebody will understand what you’re talking about, and the more likely you will get some help. I read through your first 8 posts and kept saying to myself “why did he keep bumping without actually giving any useful information to work with?”

When you need help in the future, tell the whole story. Every little detail. Post everything that is tangentially related. We need to see the details, because details matter.

Sorry I didn’t give the link, you’re right, it should have been obvious to me to give you an example. Here is the converted rss feed:

https://www.orionvisuals.com/temp/blog.xml

I’ll try to provide as much information as possible in the future. I was completely lost and not sure exactly what would have helped. I just need to look arder and deeper I guess.

Does the xml file give any further clues? Looking at it myself, I can’t see the full content of the posts anywhere. The <description> tag only seems to appear once per item.

Okay, I see. It’s ignoring the full content because of the choose construct. So, just get rid of the choose entirely.

Change this:

<x:choose>
<x:when test="atom:summary"><description><x:apply-templates select="atom:summary" mode="asHTML"/> <x:if test="atom:content"> (...)</x:if></description></x:when>
<x:when test="atom:content"><description><x:apply-templates select="atom:content" mode="asHTML"/></description></x:when>
</x:choose>

To this:

<x:if test="atom:summary"><description><x:apply-templates select="atom:summary" mode="asHTML"/></description></x:if>
<x:if test="atom:content"><content:encoded><x:apply-templates select="atom:content" mode="asHTML"/></content:encoded></x:if>

That will put the summary bits in the description and the normal content in content:encoded, which is the usual way WordPress does things.

I’ve been looking for a solution as well. Here’s what I’ve recently found and am about to try:

https://y360users.multiply.com/journal/item/7/How_to_Save_Your_Yahoo_Blog_To_Disk

Firefox to the rescue!

Otto42’s suggestion, changing <description> to <content:encoded> solved my problem of only getting partial imports in no time flat. God bless this place. Or the Flying Spaghetti Monster bless this place, whatever floats your boat.