<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: About	</title>
	<atom:link href="https://blog.boro2g.co.uk/about/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.boro2g.co.uk</link>
	<description>Some ideas about coding, dev and all things online.</description>
	<lastBuildDate>Fri, 24 Jul 2015 09:30:28 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.8</generator>
	<item>
		<title>
		By: boro		</title>
		<link>https://blog.boro2g.co.uk/about/#comment-277272</link>

		<dc:creator><![CDATA[boro]]></dc:creator>
		<pubDate>Mon, 11 May 2015 09:33:51 +0000</pubDate>
		<guid isPermaLink="false">http:/?page_id=2#comment-277272</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.boro2g.co.uk/about/#comment-228316&quot;&gt;Mark Stiles&lt;/a&gt;.

Good plan :) I&#039;ll update...]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.boro2g.co.uk/about/#comment-228316">Mark Stiles</a>.</p>
<p>Good plan 🙂 I&#8217;ll update&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mark Stiles		</title>
		<link>https://blog.boro2g.co.uk/about/#comment-228316</link>

		<dc:creator><![CDATA[Mark Stiles]]></dc:creator>
		<pubDate>Fri, 17 Apr 2015 13:53:14 +0000</pubDate>
		<guid isPermaLink="false">http:/?page_id=2#comment-228316</guid>

					<description><![CDATA[You should consider throwing up your name and a photo on the site. So that at the very least you get the attribution you deserve.]]></description>
			<content:encoded><![CDATA[<p>You should consider throwing up your name and a photo on the site. So that at the very least you get the attribution you deserve.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: boro		</title>
		<link>https://blog.boro2g.co.uk/about/#comment-72381</link>

		<dc:creator><![CDATA[boro]]></dc:creator>
		<pubDate>Tue, 12 Aug 2014 15:16:34 +0000</pubDate>
		<guid isPermaLink="false">http:/?page_id=2#comment-72381</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.boro2g.co.uk/about/#comment-69913&quot;&gt;Joey Uhl&lt;/a&gt;.

I would have thought so - at the point you iterate through the tree you could force the language you want to create the item in (rather than running through all available languages). Then for any node that is discovered you would then find an &#039;en&#039; item would exist. The issue I can think of is the new nodes might be missing the content they need to work effectively.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.boro2g.co.uk/about/#comment-69913">Joey Uhl</a>.</p>
<p>I would have thought so &#8211; at the point you iterate through the tree you could force the language you want to create the item in (rather than running through all available languages). Then for any node that is discovered you would then find an &#8216;en&#8217; item would exist. The issue I can think of is the new nodes might be missing the content they need to work effectively.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joey Uhl		</title>
		<link>https://blog.boro2g.co.uk/about/#comment-69913</link>

		<dc:creator><![CDATA[Joey Uhl]]></dc:creator>
		<pubDate>Fri, 25 Jul 2014 13:52:12 +0000</pubDate>
		<guid isPermaLink="false">http:/?page_id=2#comment-69913</guid>

					<description><![CDATA[Hello,

We have an issue where the &quot;en&quot; language was removed, which orphaned many key Sitecore items. Unfortunately, Globalization Export / Import only works with child nodes and can not fix the issue. I am interested in the Create an Item in all languages post you made and if it could be adopted to check all items in Sitecore and create a &quot;en&quot; version if one is not present.]]></description>
			<content:encoded><![CDATA[<p>Hello,</p>
<p>We have an issue where the &#8220;en&#8221; language was removed, which orphaned many key Sitecore items. Unfortunately, Globalization Export / Import only works with child nodes and can not fix the issue. I am interested in the Create an Item in all languages post you made and if it could be adopted to check all items in Sitecore and create a &#8220;en&#8221; version if one is not present.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
