<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<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">
	<channel>
		<title>Support Forum - Tag: add elements - Recent Posts</title>
		<link>http://www.kriesi.at/support/tags/add-elements</link>
		<description>Support Forum - Tag: add elements - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Sun, 19 May 2013 12:06:11 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.kriesi.at/support/search.php</link>
		</textInput>
		<atom:link href="http://www.kriesi.at/support/rss/tags/add-elements" rel="self" type="application/rss+xml" />

		<item>
			<title>Nick on "Template pages and SEO"</title>
			<link>http://www.kriesi.at/support/topic/template-pages-and-seo#post-94057</link>
			<pubDate>Wed, 30 Jan 2013 02:14:29 +0000</pubDate>
			<dc:creator>Nick</dc:creator>
			<guid isPermaLink="false">94057@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;Propulsion Theme has been expertly crafted by Kriesi to provide the highest level of SEO thereby maximizing the optimization of your website for search engines. General rules should be for you to provide unique content with 400-600 words that are unique to that page and can be found nowhere else on the internet. The content that is closer to the top of the page has more seo value than the content lower on the page.. However the content lower on the page is important because it should validate and reinforce the content on the top of the page. So I think your strategy delivered through Propulsion's SEO optimized code will be looked favorably upon by search engine spiders.&#60;/p&#62;
&#60;p&#62;Thanks,&#60;/p&#62;
&#60;p&#62;Nick
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Ismael on "Template pages and SEO"</title>
			<link>http://www.kriesi.at/support/topic/template-pages-and-seo#post-94049</link>
			<pubDate>Wed, 30 Jan 2013 01:53:07 +0000</pubDate>
			<dc:creator>Ismael</dc:creator>
			<guid isPermaLink="false">94049@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;I'm really not sure about this because I'm not an SEO expert but Avia Themes are coded with SEO best practice in mind. Anyway, let me tag the rest of the support team to help us out.&#60;/p&#62;
&#60;p&#62;Regards,&#60;br /&#62;
Ismael
&#60;/p&#62;</description>
		</item>
		<item>
			<title>KingConga on "Template pages and SEO"</title>
			<link>http://www.kriesi.at/support/topic/template-pages-and-seo#post-93993</link>
			<pubDate>Tue, 29 Jan 2013 21:16:39 +0000</pubDate>
			<dc:creator>KingConga</dc:creator>
			<guid isPermaLink="false">93993@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;If I add additional elements so that there is a second Post/Page Content area , or a Text Area/Callout/Quote  does this additional are add to the SEO content of the page?&#60;br /&#62;
I would like some page content (with SEO value), followed by some Portfolio Items, and then some more page content.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>SteveYoung on "JSON data from server could not be parsed. Error"</title>
			<link>http://www.kriesi.at/support/topic/json-data-from-server-could-not-be-parsed-error#post-89398</link>
			<pubDate>Sun, 23 Dec 2012 15:03:30 +0000</pubDate>
			<dc:creator>SteveYoung</dc:creator>
			<guid isPermaLink="false">89398@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Thank you I woke up overnight thinking about that option.  To be honest we have to delay upgrades on that plugin, often bugs exist for a few revisions.&#60;/p&#62;
&#60;p&#62;So no you did not miss anything, I did...  &#60;/p&#62;
&#60;p&#62;Thanks for your help.  Especially the extremely prompt response and personal service!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Dude on "JSON data from server could not be parsed. Error"</title>
			<link>http://www.kriesi.at/support/topic/json-data-from-server-could-not-be-parsed-error#post-89371</link>
			<pubDate>Sat, 22 Dec 2012 21:20:44 +0000</pubDate>
			<dc:creator>Dude</dc:creator>
			<guid isPermaLink="false">89371@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Maybe I'm missing something but I updated your Cart66 to version 1.5.1.3 and the error message is gone. I just hit the &#34;Check for Updates&#34; button on the debug page (Cart66 &#38;gt; Settings &#38;gt; Debug &#38;gt; Debug Data) and it showed me that you're using version 1.5.0.3 and that an update is available (1.5.1.3). I installed the update and voila - no error message :)&#60;/p&#62;
&#60;p&#62;Tbh - I'd update all other plugins too because you're using WP3.5.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>SteveYoung on "JSON data from server could not be parsed. Error"</title>
			<link>http://www.kriesi.at/support/topic/json-data-from-server-could-not-be-parsed-error#post-89370</link>
			<pubDate>Sat, 22 Dec 2012 20:52:33 +0000</pubDate>
			<dc:creator>SteveYoung</dc:creator>
			<guid isPermaLink="false">89370@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Done, sent through the website when I made the user.&#60;/p&#62;
&#60;p&#62;I did the 1.6 not the 1.4 let me know if you need that.&#60;/p&#62;
&#60;p&#62;Thank you for your kind help.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Dude on "JSON data from server could not be parsed. Error"</title>
			<link>http://www.kriesi.at/support/topic/json-data-from-server-could-not-be-parsed-error#post-89359</link>
			<pubDate>Sat, 22 Dec 2012 17:50:53 +0000</pubDate>
			<dc:creator>Dude</dc:creator>
			<guid isPermaLink="false">89359@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Hey! &#60;/p&#62;
&#60;p&#62; Please create me a wordpress admin account and send me the login data to: &#60;a href=&#34;mailto:kriesi2000-dude@yahoo.com&#34;&#62;kriesi2000-dude@yahoo.com&#60;/a&#62;&#60;br /&#62;
I'll check the error with the dev console. &#60;/p&#62;
&#60;p&#62; Best regards,&#60;br /&#62;
Peter
&#60;/p&#62;</description>
		</item>
		<item>
			<title>SteveYoung on "JSON data from server could not be parsed. Error"</title>
			<link>http://www.kriesi.at/support/topic/json-data-from-server-could-not-be-parsed-error#post-89354</link>
			<pubDate>Sat, 22 Dec 2012 16:08:37 +0000</pubDate>
			<dc:creator>SteveYoung</dc:creator>
			<guid isPermaLink="false">89354@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Well I turned on the most important plugin first Cart66.  With Choices 1.6 and Cart66 turned on JSON error is there and the screen greys out when trying to add an image to the slide show.&#60;/p&#62;
&#60;p&#62;The entire intent of this site is ecommerce.&#60;/p&#62;
&#60;p&#62;We have a testbed running Choices version 1.4 in maintenance mode that does not have this problem, it is running Cart66.  Sounds like a solution (a bad one) would be to go back to 1.4.&#60;/p&#62;
&#60;p&#62;If I change to a default WP theme for testing I think I loose the settings on yours.  If not let me know I can do that as a test.&#60;/p&#62;
&#60;p&#62;I will do further testing and report back.  We bought a similar theme from another developer on Themeforest, I will upload and try that.  Just for testing information.  You guys have been so good over the years, I want to stay with a Kriesi product.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>SteveYoung on "JSON data from server could not be parsed. Error"</title>
			<link>http://www.kriesi.at/support/topic/json-data-from-server-could-not-be-parsed-error#post-89347</link>
			<pubDate>Sat, 22 Dec 2012 15:41:54 +0000</pubDate>
			<dc:creator>SteveYoung</dc:creator>
			<guid isPermaLink="false">89347@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Working on a site that is not public yet we upgraded to 1.6 in the past few weeks.  When upgrading we had a problem where the &#34;add elements&#34; to the template stopped working.  We documented it well in this topic.&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.kriesi.at/support/topic/unable-to-access-element-details-after-loading-in-template-builder?message=update-support-forums-topic-status-error&#34; rel=&#34;nofollow&#34;&#62;http://www.kriesi.at/support/topic/unable-to-access-element-details-after-loading-in-template-builder?message=update-support-forums-topic-status-error&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;We found a solution by deleting the theme choices completely and reloading it.&#60;/p&#62;
&#60;p&#62;However, now the following &#34;JSON data from server could not be parsed. This is caused by a JSON formatting error&#34; is displayed when you enter the backend going to the dashboard.  One of our people continued development since we were almost done, adding widgets.  That all worked fine except for this error when she went into the backend.&#60;/p&#62;
&#60;p&#62;Then I had her start working on the last item, the home page.  To do that she need to add images to the slide show on pages we would want to show up in the home page with links.  When opening any page to edit and &#34;add image to slide show&#34; the page the gets grayed out.  You can not add an image or edit anything.&#60;/p&#62;
&#60;p&#62;I did shut off all plugins, and I can now add the image without the error.  I do not get the JSON error when going into the backend.  I am now adding them one by one to see when it fails.  I will report back when I have more data.&#60;/p&#62;
&#60;p&#62;However, I added no plugins since upgrading to 1.6 all we did was upgrade choices.&#60;/p&#62;
&#60;p&#62;Is this related to the JSON error?&#60;/p&#62;
&#60;p&#62;What is JSON?&#60;/p&#62;
&#60;p&#62;When the incomplete install, the installation that had the first error in the &#34;element details&#34; happened, did that corrupt our database somehow?&#60;/p&#62;
&#60;p&#62;How do I solve the error, and at the same time not loose what we have done?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
