Opera 9.5 failed to process TinyMCE correctly. so if you enterd something in the HTML editor and came back to Visual editor mode.. you won’t see any text. Check out thses screen shots.

Actually it is caused by wrong implementation of JavaScript in TinyMCE. More about it is explained at opera development blog. In the race to win Acid3 test Opera made the implementation of web standards strict. It was this that caused the error.

This text doesn’t show.

As of now the problem has been solved in Opera 9.51 and this post is being written using Opera 9.51. Another known issue with TinyMCE was scrabling of text when pressing the ENTER key. This is also solved now.

Does anybody notice the rising CPU usage of your browser when you are at the create post page (Tiny MCE) of your self hosted Wordpress blog? Previously when I was using Firefox the CPU usage rose to 50 percent and FF was running fast like a snail. I thought it was because of problems with FF. Last day when I was using Opera Process Explroer was open. I couldn’t believe that Opera too used very much CPU resources. It was then that I realised the culprit was the Wordpress Create Post page (A intersection B, lol).

I was amazed when a Google search provided me only one relevent result. The problem is actually with the Wordpress “autosave” feature. If autosave is enabled, then the “Save” “Publish” buttons on my post page used to blink. Everything will come to normal once you “Disable AutoSave” on your blog.

To disble AutoSave you need to comment out the function wp_enqueue_script(‘autosave’); from the following file by adding “//” before them. Comment the line in the following files – /wp-admin/post.php  /wp-admin/page.php  /wp-admin/post-new.php  /wp-admin/page-new.php

After commenting the lines should look like – //wp_enqueue_script(‘autosave’);

Upload these files back and you will have solved the problem. Remember that since SutoSave is disabled you must manually save changes while writing a post.

I didn’t notice the CPU usage while using Opera because Opera is better than Firefox at managing memory and CPU. Also the overall perfomance of the Opera was not affected by the presence of the post page. But in FireFox when the page ws open I couldn’t scroll through any of the pages or couldn’t switch tabs by cliking on them.

I found all these information from Richard Timothy’s blog. Thanks Thimothy .

Wordpress has released its new version 2.5.1 It has got many security fixes and some minor bug fixes. You may either replace the security fixed files or do a complete update. The files that were fixed with security issues were – wp-includes/pluggable.php, wp-admin/includes/media.php, and wp-admin/media.php. You can just replace your existing files with the above one.

This release of Wordpress also adds a new security key feature to the wp-config.php file that will let you randomize cookie encryption. You can visit this link we set up to get a unique secret key for your config file. (It’s unique and random on every page load.) Having this line in your config file helps secure your blog.

It is completely normal that a site doesn’t load. but it is not that normal when the site won’t load only on Firefox. Well of late I have found that Firefox running on certain Windows XP boxes infected with virus won’t load a Wordpress blog correctly.

An example is the machine I am currently writing this post on. My Blog and Wordpress homepage will not load on this machine even if you waited for a month or so. First I thought it had something to do with my blog. But I found out later that only Firefox does not load my page but IE and OPERA will load it correctly.

The simple and easy solution comes right through your address bar. Just add a “?” mark (no quotes) at the end of the URL after the “/” that is the new address is http://exnol.com/? And the site will load perfectly.

Actually this can be applied to other sites also which wont load after a long time.