<?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"
	>
<channel>
	<title>Comments on: WordpressMU Migration Drama</title>
	<atom:link href="http://www.librarywebchic.net/wordpress/2008/03/19/wordpressmu-migration-drama/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarywebchic.net/wordpress/2008/03/19/wordpressmu-migration-drama/</link>
	<description>Resources for librarians who are interested in the application of web design and technologies in libraries</description>
	<pubDate>Sun, 12 Oct 2008 04:53:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Peter Murray</title>
		<link>http://www.librarywebchic.net/wordpress/2008/03/19/wordpressmu-migration-drama/#comment-60541</link>
		<dc:creator>Peter Murray</dc:creator>
		<pubDate>Thu, 20 Mar 2008 15:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarywebchic.net/wordpress/2008/03/19/wordpressmu-migration-drama/#comment-60541</guid>
		<description>Karen --

Your post reminded me about &lt;a href="http://dltj.org/article/wordpress-ssl-xmlhttprequest/" rel="nofollow"&gt;a problem and a hack I put in place&lt;/a&gt; on my own WordPress installation to deal with a problem with SSL on admin pages.  I don't know if you've run into this or not, but AJAX functions on SSL-encrypted admin pages will fail because of the browser's security settings.  I've documented the problem and a solution/hack at the URL above.  You might find it useful, too.</description>
		<content:encoded><![CDATA[<p>Karen &#8211;</p>
<p>Your post reminded me about <a href="http://dltj.org/article/wordpress-ssl-xmlhttprequest/" rel="nofollow">a problem and a hack I put in place</a> on my own WordPress installation to deal with a problem with SSL on admin pages.  I don&#8217;t know if you&#8217;ve run into this or not, but AJAX functions on SSL-encrypted admin pages will fail because of the browser&#8217;s security settings.  I&#8217;ve documented the problem and a solution/hack at the URL above.  You might find it useful, too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
