<?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 - Topic: Broadscope not working properly after upgrading to WP 3.5</title>
		<link>http://www.kriesi.at/support/topic/broadscope-not-working-properly-after-upgrading-to-wp-35</link>
		<description>Support Forum - Topic: Broadscope not working properly after upgrading to WP 3.5</description>
		<language>en-US</language>
		<pubDate>Thu, 20 Jun 2013 08:15:07 +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/topic/broadscope-not-working-properly-after-upgrading-to-wp-35" rel="self" type="application/rss+xml" />

		<item>
			<title>wekudata on "Broadscope not working properly after upgrading to WP 3.5"</title>
			<link>http://www.kriesi.at/support/topic/broadscope-not-working-properly-after-upgrading-to-wp-35#post-88719</link>
			<pubDate>Tue, 18 Dec 2012 07:52:52 +0000</pubDate>
			<dc:creator>wekudata</dc:creator>
			<guid isPermaLink="false">88719@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Thank you very much, it works!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Dude on "Broadscope not working properly after upgrading to WP 3.5"</title>
			<link>http://www.kriesi.at/support/topic/broadscope-not-working-properly-after-upgrading-to-wp-35#post-88618</link>
			<pubDate>Mon, 17 Dec 2012 17:07:58 +0000</pubDate>
			<dc:creator>Dude</dc:creator>
			<guid isPermaLink="false">88618@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;This issue is caused by a small syntax error in wp-content/themes/broadscope/framework/js/avia_option_pages.js - open up the file and replace:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;$(&#38;#39;.avia_header .avia_button_inactive, .avia_footer .avia_button_inactive, &#38;#39;).removeClass(&#38;#39;avia_button_inactive&#38;#39;);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;with:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;$(&#38;#39;.avia_header .avia_button_inactive, .avia_footer .avia_button_inactive&#38;#39;).removeClass(&#38;#39;avia_button_inactive&#38;#39;);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;I'll mark this thread for Kriesi and ask him to include the fix in the next update.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>wekudata on "Broadscope not working properly after upgrading to WP 3.5"</title>
			<link>http://www.kriesi.at/support/topic/broadscope-not-working-properly-after-upgrading-to-wp-35#post-88567</link>
			<pubDate>Mon, 17 Dec 2012 12:43:26 +0000</pubDate>
			<dc:creator>wekudata</dc:creator>
			<guid isPermaLink="false">88567@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Hi!&#60;br /&#62;
I've upgraded wordpress to 3.5 with broadscope theme(version 1.3) but the &#34;save all changes&#34; button is &#34;greyed out&#34; on the &#34;theme options page&#34;. I have tested on two different servers with the same result. It doesen't help to inactivate the plugins either.&#60;/p&#62;
&#60;p&#62;When I downgrade to 3.4.2 the problems disappear. Do you have any solution to this problem or any idea?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
