<?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: Shoutbox - broken menu area on update to 3.3</title>
		<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33</link>
		<description>Support Forum - Topic: Shoutbox - broken menu area on update to 3.3</description>
		<language>en-US</language>
		<pubDate>Sat, 25 May 2013 10:23:32 +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/shoutbox-broken-menu-area-on-update-to-33" rel="self" type="application/rss+xml" />

		<item>
			<title>rumblefish on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-37011</link>
			<pubDate>Mon, 09 Jan 2012 09:00:35 +0000</pubDate>
			<dc:creator>rumblefish</dc:creator>
			<guid isPermaLink="false">37011@http://www.kriesi.at/support/</guid>
			<description>&#60;blockquote&#62;&#60;p&#62;Is there a way around having to re-do all that work on a new site?
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;In theory your database should hold most of the design elements inside it. You shouldn't need to redo things manually if you export the old one and reimport it properly. The other important file is your custom.css (remember to update urls inside this file if you added any). If all the images have been copied to the uploads folder and your plugin folder has the plugins reinstalled etc, you shouldn't have too many problems.&#60;/p&#62;
&#60;p&#62;I highlight all the shoutbox files I have changed in a different color. that way its much easier to see which ones have been modified if I ever need to update. Same with the plugin files and core wordpress files, but usually those don't need changing.&#60;/p&#62;
&#60;p&#62;Once your database starts to get big, importing and exporting with phpmyadmin may not work. You may have to find a new method (I use the mysql import in the Terminal on a Mac) or split it into sections. There is a great &#34;plugin&#34; which rebuilds the database properly after an import. It's called searchreplacedb2.php by Interconnectit. It saved my ass after moving my wordpress site to a new host.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lbdesign on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-37009</link>
			<pubDate>Mon, 09 Jan 2012 06:04:52 +0000</pubDate>
			<dc:creator>lbdesign</dc:creator>
			<guid isPermaLink="false">37009@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Turns out it was a conflict with a plugin.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lbdesign on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-36524</link>
			<pubDate>Wed, 04 Jan 2012 07:55:01 +0000</pubDate>
			<dc:creator>lbdesign</dc:creator>
			<guid isPermaLink="false">36524@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;This is the site with the menus that I can no longer edit:&#60;br /&#62;
&#60;a href=&#34;http://www.lbdesign.com/hillary/&#34; rel=&#34;nofollow&#34;&#62;http://www.lbdesign.com/hillary/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;I'm just staging it here until I finish working out all the design aspects, then we will install it at the correct URL, so anyone reading this post in a few months may find that it no longer exists.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lbdesign on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-36523</link>
			<pubDate>Wed, 04 Jan 2012 07:53:27 +0000</pubDate>
			<dc:creator>lbdesign</dc:creator>
			<guid isPermaLink="false">36523@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;I don't know. I'll try to check on that. I created a whole new instance of WP 3.3 from scratch, re-imported everything to the fresh database, and that new site is working fine, so I'm abandoning the old one. But I have to manually re-do a bunch of things like the widgets. And the mega-menu customizations.&#60;br /&#62;
Is there a way around having to re-do all that work on a new site?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Dude on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-36426</link>
			<pubDate>Tue, 03 Jan 2012 12:07:29 +0000</pubDate>
			<dc:creator>Dude</dc:creator>
			<guid isPermaLink="false">36426@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Hey,&#60;br /&#62;
Maybe it's a problem caused by the php execution time or allocated php memory?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lbdesign on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-36400</link>
			<pubDate>Tue, 03 Jan 2012 06:35:50 +0000</pubDate>
			<dc:creator>lbdesign</dc:creator>
			<guid isPermaLink="false">36400@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;The error is:&#60;br /&#62;
&#34;The website encountered an error while retrieving &#60;a href=&#34;http://www.lbdesign.com/hillary/wp-admin/nav-menus.php&#34; rel=&#34;nofollow&#34;&#62;http://www.lbdesign.com/hillary/wp-admin/nav-menus.php&#60;/a&#62;. It may be down for maintenance or configured incorrectly.&#34;&#60;/p&#62;
&#60;p&#62;but that file exists at the specified path.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lbdesign on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-36397</link>
			<pubDate>Tue, 03 Jan 2012 03:54:16 +0000</pubDate>
			<dc:creator>lbdesign</dc:creator>
			<guid isPermaLink="false">36397@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;FYI, I did a manual upload of the new them on top of the existing theme directory.&#60;br /&#62;
All other aspects of the site are running normally (as far as I know)
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lbdesign on "Shoutbox - broken menu area on update to 3.3"</title>
			<link>http://www.kriesi.at/support/topic/shoutbox-broken-menu-area-on-update-to-33#post-36396</link>
			<pubDate>Tue, 03 Jan 2012 03:29:37 +0000</pubDate>
			<dc:creator>lbdesign</dc:creator>
			<guid isPermaLink="false">36396@http://www.kriesi.at/support/</guid>
			<description>&#60;p&#62;Yesterday, I upgraded to WP 3.3, and downloaded and installed the latest Shoutbox, and now I can't edit the navigation menu.&#60;br /&#62;
When I hit &#34;Save Menu&#34;, I get this error: &#60;/p&#62;
&#60;p&#62;&#34;HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.&#34;&#60;/p&#62;
&#60;p&#62;Do you have any ideas about whether this is a Shoutbox issue with the 3.3 update, or any other ideas about how to overcome this? Because right now, I can't launch the site on schedule. &#60;/p&#62;
&#60;p&#62;Thank you,&#60;br /&#62;
--Lee
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
