My JS console was showing the above errors

replace_element.insertAdjacentHTML is not a function       tiny_mce.js (line 1)

this.contentWindow has no properties            tiny_mce.js (line 1)

So it was something related to tinymce. Well that was my problem but for the same reason you might encounter another error…So, what’s the fix for this problem?

Since last time this tinymce worked I did one change to Firefox indeed. I’ve changed the user agent and looks like that broke the JavaScript.

So, if you have this problem, type about:config in your Firefox and search for general.useragent.extra.firefox. Make sure this has a value something like this Firefox/2.0.0.1. Also, lookup for general.useragent.override and make sure it has an empty value. If you can’t find this last one than there’s no problem.

Hope this helped somebody out there!

Thanks for reading

What I always notices is that if your wordpress 404 page is bigger than 512 bytes than it is always loaded in IE.

So Put more than 512 bytes and you’ll force the buggy IE to work

The installation process  is a very simple and basic one so I didn’t  make a readme or detailed instructions. Just upload it to your plugin directory and activate it. Than when you’ll go to the write page menu you’ll see the categories widget on the right sidebar.

page_category.zip

hope you find this usefull

Keywords and Post Titles in the Permalink or Link Structure

The default installation of WordPress uses URLs like www.mywebsite.com/?id=1234 to point to your individual blog articles. This works fine, but you can add few benefits if you change the link structure to: www.mywebsite.com/category/title-of-post like:

1) Having in the link the title of the post, will be a benefit because the words that you use for your categories and titles automatically become keywords that the search engines can index every time someone links to you.

Remember that Google takes into account the words given in the anchor text to determine if your page is relevant for any given search engine query. This may not be a huge benefit but it matter. Imagine you have a link referred in a site and an user will decide if it worth to continue reading.

2) Another advantage of having friendly URLs is that you may change with another blogging tool and having your URLs in the form of www.mywebsite.com/?p=1234, how will you maintain such a script-specific URL? What happens if the new software assign another number to your blog entries when you import your existing blog database?

Changing URLs has enormous search engine ramifications. Imagine that all the links from external sites that currently point to those pages will be instantly broken, and along with it, the search engine will penalize your website. It is better to pre-empt the problem by configuring WordPress to use page titles as the permalinks.

How to Put Your Post Titles into Your URLs in WordPress

WordPress makes it easy for you to change your URLs. Follow the steps:

• Log into your WordPress blog.
• Click on the “Options” menu.
• Click “Permalinks“.
• Before you change anything, make sure that you don’t have a category that conflicts with one of WordPress scripts or directory names. For example, check to see that you don’t have a category by the name of wp-admin. If you do, you should change your category names first before proceeding.
• Scroll down to the “Common options” section and select “Custom, specify below“. In the box below, type “/%category%/%postname%/” without the opening and closing inverted commas (quotes). Click “Update Permalink Structure“.
• You will see a message “Permalink structure updated“.
• You can now view your blog and check the individual post pages to see your new site structure.

Post Titles in the TITLE Tag

Also if you want to create a search engine friendly website make sure that your HTML title tags contain relevant text. In WordPress the title tags are created automatically from your post titles.

How to Modify the Default Template to Place Post Titles First

• Log into your WordPress account and click “Presentation“.
• Click the “Theme Editor” link.
• Look at the right hand side of your browser window to locate the “Header” link, and click on it.
• The browser should now display “Editing header.php“. Somewhere in the box below this, locate the line that says

<title><?php bloginfo('name'); ?> <?php if ( is_single() ) { ?> » Blog Archive <?php } ?> <?php wp_title(); ?></title>

Change it to the following:
<title><?php wp_title(); ?></title>

If you want to have the name of your blog at the end in the title, change it to the following instead:

<title><?php wp_title(); ?> - <?php bloginfo('name'); ?></title>

• Click the “Update File” button when you are through. You should receive the message “File edited successfully“.

• Forces content editors to produce accessible web pages (up to AAA-compliant)
• Is highly intuitive and easy-to-use
• Ensures web pages are highly optimised for search engines

The most accessible CMS available

The CMS is not only capable of creating highly accessible, standards compliant web pages - it actually forces content editors to create accessible pages (up to AAA-compliant).

Through a variety of innovative techniques content editors are forced to:

• Provide accurate and appropriate ALT text for all images
• Use a correct heading structure with just one main heading
• Produce accessible and well-written page content
• Use predefined styles for both formatting and layout effects
• Insert table headers into data tables

Content editors can additionally copy and paste text over from programs such as Microsoft Word. Our accessible CMS will automatically ‘clean up’ the code so it’s standards compliant and fully accessible!

The back-end too has been built with accessibility in mind so any employees with special needs can use the content management system too.

Our revolutionary CMS goes way above and beyond merely allowing accessible web pages to be produced. Rather it forces editors to produce both accessible code and accessible content.

More reasons our accessible CMS is unique

In addition to being the most accessible CMS out there, the system also has the following features:

• Extremely easy-to-use and highly intuitive - Our CMS has been through countless rounds of usability testing
• Produces search engine optimised pages - Users specify the page name and our CMS will ensure these keywords are placed in the positions search engines look for them
• Advanced AJAX functionality enhancing the user experience and ease of use (with accessible, non-JavaScript alternatives available)
• Simple search engine-friendly URLs

How the CMS works

The accessible CMS can be used by anyone regardless of technical know-how. Simply login through any web browser (it works in all major browsers) and you’re instantly be able to add, move, delete or edit pages on your website.

To create or edit a page content editors use our highly intuitive WYSIWYG editor, with a similar interface to Microsoft Word. You don’t need any prior technical or web knowledge.

Other features of our accessible CMS include:

• Image management
• Different levels of administrative rights
• Automated site map
• Preview pages before saving

Visit Webcredible’s website to get a quote or discuss specific requirements.

You’ll find out how to easily help search engines to find links that changed, and more than that, replace old URLs with the new ones.

Of course you know about HTTP response codes. That’s the key here. When an URL changes, it’ll return 404 obviously. There is a way though to tell search engines that URL X can now be found at Y location. that’s what 301 status stands for (Moved Permanent). Now how do we do that?

Htaccess redirect old url to new one with a 301 code

Yes that’s a solution but that’s for advanced users, the ones that know a bit about url rewriting and such. We do not intend to talk about that in here ( If you wanna read more about that , just go into the appropriate section or use the advanced search to look for).

What we intend to do here is provide a way of doing such redirects in an extremely easy way for wordpress users. The solution comes off course with a plugin. That can be downloaded here.

Some of the features of this cool plugin are:

• 404 error monitoring - captures a log of 404 errors and allows you to easily map these to 301 redirects
• Custom ‘pass-through’ redirections allowing you to pass a URL through to another page, file, or website.
• Full logs for all redirected URLs
• All URLs can be redirected, not just ones that don’t exist
• Redirection methods - redirect based upon login status, redirect to random pages, redirect based upon the referrer!
• WordPress 2.1+ only
• Automatically add a 301 redirection when a post’s URL changes
• Manually add 301, 302, and 307 redirections for a WordPress post, or for any other file
• Full regular expression support
• Apache .htaccess is not required - works entirely inside WordPress
• Strip or add www to all your WordPress pages
• Redirect index.php, index.html, and index.htm access
• Redirection statistics telling you how many times a redirection has occurred, when it last happened, who tried to do it, and where they found your URL
• Fully localized

Google-ing away I found that someone else did a plugin that does exactly what I wanted to do. I was happy to find it and I published it here so others can easily find it. The plugin can be found at CodeHooligan or download it by clicking here.

Thanks for that great plugin.

I tested it on WP 2.2 and works great.

Wordpress is a great blog by its features and user friendly admin interface but is also a great CMS. It is extremely SEO with it’s nice URL’s. But speaking of URL’s, wordpress uses some internal rewriting rules with Apache’s aid. Problems appear when you try to password protect a directory via http authentication. It conflicts with the default wordpress’s .htaccess resulting in a 404 error.

The Solution

The solution comes by “telling” apache how to handle our pasword protected directory. But let’s take it step by step. Let’s first password protect the directory via .htaccess (that offers http auth; user/pass are sent as plain text to the server; the password is crypt). To do that we create a .htaccess file in our directory. Let’s say we want to protect the directory called “secure” that lays into the web-server’s root .

AuthUserFile /your/directory/here/
.htpasswdAuthGroupFile /dev/null
AuthName "Secure Area"
AuthType Basicrequire valid-user

Now we need to create password file that will hold our username:password pairs. To do that could be use scripting or the easiest just type htpasswd -c .htpasswd username wich will prompt for the password to be used for user ‘username’.

Note: The path to the .htpasswd file should be the right one in your .htacces file

Ok, what we have done until now would work in any usual configuration. Though it wouldn’t work if you have an wordpress installation in your web-server root. Accessing the protected folder will give you 404. To fix that you have to modify the original wordpress .htacces file.

It looks something like this:

# BEGIN WordPress

RewriteEngine On

RewriteBase /

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

# END WordPress

Add above that this piece of code:

RewriteEngine On

RewriteBase /

RewriteCond %{REQUEST_URI} ^/secure/(.*)$

RewriteRule ^.*$ - [L]

Now your secured folder will be accessible after entering username and password offcourse . Enjoy