<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>thinkAPI&#187; tiny mce</title>
	<atom:link href="http://thinkapi.com/blog/tag/tiny-mce/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkapi.com/blog</link>
	<description>An interface to tech thoughts</description>
	<lastBuildDate>Fri, 06 Apr 2012 09:23:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>WordPress Visual Editor Problem After Upgrade &#8211; Fix</title>
		<link>http://thinkapi.com/blog/wordpress-visual-editor-problem-after-upgrade/</link>
		<comments>http://thinkapi.com/blog/wordpress-visual-editor-problem-after-upgrade/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 08:18:52 +0000</pubDate>
		<dc:creator>Sukumar</dc:creator>
				<category><![CDATA[Business IT]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[rich editor]]></category>
		<category><![CDATA[tiny mce]]></category>
		<category><![CDATA[TinyMCE]]></category>
		<category><![CDATA[visual editor]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://thinkapi.com/blog/?p=71</guid>
		<description><![CDATA[Many users of wordpress face a problem wherein the visual editor stop working or is stuck after an upgrade. The below screenshot shows the problem. Even though this is a serious, annoying and quite widely observed problem, there has been &#8230; <a href="http://thinkapi.com/blog/wordpress-visual-editor-problem-after-upgrade/">Continue reading <span class="meta-nav">&#8594;</span></a>
No related posts.]]></description>
			<content:encoded><![CDATA[<p>Many users of <a title="Wordpress" href="http://wordpress.org" target="_blank">wordpress</a> face a problem wherein the visual editor stop working or is stuck after an upgrade. The below screenshot shows the problem.</p>
<div class="wp-caption aligncenter" style="width: 556px"><a href="http://lh3.ggpht.com/_f3EtWybcQP4/STD2CUcZWfI/AAAAAAAAAj4/rLvLpDIwf6w/s720/wpproblemyp5.png"><img title="Wordpress Visual Editor Problem" src="http://lh3.ggpht.com/_f3EtWybcQP4/STD2CUcZWfI/AAAAAAAAAj4/rLvLpDIwf6w/s720/wpproblemyp5.png" alt="Wordpress Visual Editor Problem" width="546" height="226" /></a><p class="wp-caption-text">Wordpress Visual Editor Problem</p></div>
<p>Even though this is a serious, annoying and quite widely observed problem, there has been no official fix for it. Lot of posts describe various possible solutions (see links section at the end), this is the one that worked for me.</p>
<p><span id="more-71"></span>The culprit here is the file &#8220;<strong>wp-includes/js/tinymce/tiny_mce_config.php</strong>&#8221; which tries to gzip the tinymce js and the output is just messed up. Disable compression in this file and you are good to go.</p>
<p>Open tiny_mce_config.php located at wp-includes/js/tinymce with your favorite text editor, look for an array initArray</p>
<pre class="brush: php; title: ; notranslate">
// TinyMCE init settings
$initArray = array (
'mode' =&gt; 'none',
'onpageload' =&gt; 'wpEditorInit',
'width' =&gt; '100%',
'theme' =&gt; 'advanced',
'skin' =&gt; 'wp_theme',
'theme_advanced_buttons1' =&gt; &quot;$mce_buttons&quot;,
'theme_advanced_buttons2' =&gt; &quot;$mce_buttons_2&quot;,
'theme_advanced_buttons3' =&gt; &quot;$mce_buttons_3&quot;,
'theme_advanced_buttons4' =&gt; &quot;$mce_buttons_4&quot;,
'language' =&gt; &quot;$mce_locale&quot;,
'spellchecker_languages' =&gt; &quot;$mce_spellchecker_languages&quot;,
'theme_advanced_toolbar_location' =&gt; 'top',
'theme_advanced_toolbar_align' =&gt; 'left',
'theme_advanced_statusbar_location' =&gt; 'bottom',
'theme_advanced_resizing' =&gt; true,
'theme_advanced_resize_horizontal' =&gt; false,
'dialog_type' =&gt; 'modal',
'relative_urls' =&gt; false,
'remove_script_host' =&gt; false,
'convert_urls' =&gt; false,
'apply_source_formatting' =&gt; false,
'remove_linebreaks' =&gt; true,
'paste_convert_middot_lists' =&gt; true,
'paste_remove_spans' =&gt; true,
'paste_remove_styles' =&gt; true,
'gecko_spellcheck' =&gt; true,
'entities' =&gt; '38,amp,60,lt,62,gt',
'accessibility_focus' =&gt; false,
'tab_focus' =&gt; ':next',
'content_css' =&gt; &quot;$mce_css&quot;,
'save_callback' =&gt; 'switchEditors.saveCallback',
'wpeditimage_disable_captions' =&gt; $no_captions,
'plugins' =&gt; &quot;$plugins&quot;,
// pass-through the settings for compression and caching, so they can be changed with &quot;tiny_mce_before_init&quot;
'disk_cache' =&gt; true,
'compress' =&gt; true,
'old_cache_max' =&gt; '1' // number of cache files to keep
);
</pre>
<p>Change the value of the variable compress to false.</p>
<p>Hope this helps.</p>
<p>Links that might help:</p>
<p><a title="Visual Editor Not Working on Upgrade" href="http://wordpress.org/support/topic/165449" target="_blank">Visual Editor Not Working on Upgrade</a></p>
<p><a title="2.5 Visual Editor/TinyMCE problems" href="http://wordpress.org/support/topic/164990" target="_blank">2.5 Visual Editor/TinyMCE problems</a></p>
<p><a title="Wordpress Visual editor not working stuck in HMTL mode" href="http://myitkb.net/wordpress-visual-editor-problems/" target="_blank">WordPress Visual editor not working stuck in HMTL mode</a></p>
<p><a title="More problems with visual editor not working" href="http://en.forums.wordpress.com/topic/more-problems-with-visual-editor-not-working" target="_blank">More problems with visual editor not working</a></p>
<p><a title="Visual editor problem with wordpress 2.5" href="http://dungun.net/2008/04/visual-editor-problem-with-wordpress-25/" target="_blank">Visual editor problem with wordpress 2.5</a></p>
<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://thinkapi.com/blog/wordpress-visual-editor-problem-after-upgrade/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

