Madhurie Singh . Com

How to build my own web site from my wordpress blog !

Archive for the ‘Error in Wordpress’ Category

How to avoid link name getting chopped or truncated?

Posted by Madhurie Singh on September 28, 2009

I have a habit of writing long headings for my articles. I prefer providing as much information about my content just from the headline.But long headlines have their own problems. 😦

Long permalinks can get chopped off as well, with only part of it working properly or with the entire link disabled. This will cause a 404 error to be generated – but not because there’s something wrong with my permalink, rather because the title is too long.

Solution one:
To fix chopped permalinks I need to edit my .htaccess file and add a line:

RewriteRule ^post/([0-9]+)?/?([0-9]+)?/?$ /index.php?p=$1&page=$2 [QSA]

Solution two:
Another way to solve this truncation of link problem is by posting URLs with angle brackets () on either end. Most email and other problematic software won’t truncate URLs formatted this way.

I hope this solves my problem once and for all . πŸ™‚

Posted in Error in Wordpress | Comments Off on How to avoid link name getting chopped or truncated?

How to set Dunstan Error page for 404 Page not found?

Posted by Madhurie Singh on September 24, 2009

In order to activate the Dunstan-style Error Page plugin, I needed the API code.

How to get API code – wordpress?

There in Settings >>> Error Page >>> Enter the API code

Now my Dunstan-style Error Page is working.

But somehow its working only for 3 blogs!

Why on earth its not working for the 4th blog :(.

Ok I Found the culprit!!!!!!!!

Dunstan Error 404 works only with Permalinks setting Β with “Index” i.e. Β  Β /index.php/%year%/%postname%/

No other permalinks setting will work for Dunstan 404 error page!

Posted in Error in Wordpress | Tagged: , , | Comments Off on How to set Dunstan Error page for 404 Page not found?

How to get API code for

Posted by Madhurie Singh on September 24, 2009

In order to activate the Dunstan-style Error Page plugin, I needed the API code.

Now I tried looking for API code in my admin page under Profile page but I did not get anything.

SO I went back to my blog not If I did not have the blog in, I would have to create a blog only for the sake of the API code. How strange?

So I login to my blog.

There in the top left hand corner I found Β  Β  My Account >>Profile >> API code πŸ™‚

I copied that API code and again went to the admin page of my blog.

There in Settings >>> Error Page >>> Enter the API code

Now my Dunstan-style Error Page is working.

But somehow its working only for 3 blogs!

Why on earth its not working for the 4th blog :(.

Ok I Found the culprit!!!!!!!!

Dunstan Error 404 works only with Permalinks setting Β with “Index” i.e. Β  Β /index.php/%year%/%postname%/

No other permalinks setting will work for Dunstan 404 error page!

Posted in Error in Wordpress | Tagged: , , , , | Comments Off on How to get API code for

404 Broken Link Error page – File not found- permalinks

Posted by Madhurie Singh on September 21, 2009

Today I was feeling great πŸ™‚ and saw 472000 search result of my name madhurie singh!

But the happiness did not last long 😦 when I found some of the links to my site were giving error : OOPS ! The Links is broken.
The page it takes the browser to is the dreaded 404 File Not Found!!!!

And the funny part is the link that takes me there was a page that I had never created i.e. !!!

Now I am wondering how on earth did this happen. What does this error mean?

Hmm this site explains it best.

SO I gave a search on 404 error tag link broken:

I see a great number of sites on the same error handling, so lemme start browsing and scanning for the best site:

The first site is

This site claims to resolver all 404 error s by uploading a php file classes.php and functions-post.php πŸ™‚

Ok after reading here and there, one important thing that I have found is that I need a mod_rewrite installed and working and the server able to read the htaccess file.

I checked my .htaccess file which is in the root directory. I use File Manager in Cpanel to view it even though its a hidden file.
Legacy File Manager does not show hidden files.

My .htaccess file is blank 😦 even though I have done changes in permalinks of all my blogs.
It just has this in it
# BEGIN WordPress

# END WordPress

So obviously I need to make sure it has at least the mod_rewrite function to make the necessary changes that I have set through the wordpress admin page to all my blogs!

Let me find out the reason for the .htaccess file not being written !

1. One common reason is that the file is not accessible by the wordpress admin page to make the changes in .htaccess file for desired permalinks.
So I will have to change the permissions to allow the wordpress to write the .htaccess file. So I change its permission to 666 not 777.

Now I changed the permalinks from /%year%/%month%/%date%/%post%/ Β to Β /%index%

This is a great site for explaining the permalinks and how to solve errors because of permalinks:

If nothing works I will check this site later

Posted in Error in Wordpress | Tagged: , , , | Comments Off on 404 Broken Link Error page – File not found- permalinks

How to create 404 Error Page

Posted by Madhurie Singh on September 21, 2009

Some examples of 404 error pages

BROKEN LINK REMOVER AND FIXER plugins makes use of 404 for link building!!

Posted in Error in Wordpress | Tagged: , | Comments Off on How to create 404 Error Page

How to fix and solver Permalinks Problem using .Htaccess

Posted by Madhurie Singh on September 21, 2009

Fixing Permalink Problems
Fixing .htaccess Generation Issues
If your installation of WordPress does not generate a .htaccess file or if it does not write the new rules onto your existing .htaccess file then there are a couple reasons that could be causing this. Work step by step and continue to the next step only if the previous step does not work.

Change File Permissions: You must chmod the .htaccess file to 666 to edit it with the WordPress template editor, but this is not recommended, since if you do that, any user of your blog, who can edit templates will be able to edit it. You can change the permissions to 660 to make it server-writable, which again will have the same limitation.
Server Blockage: Your host might have blocked the SERVER_SOFTWARE variable and this will cause WordPress’ .htaccess generation to fail. If you are sure that your server is running Apache, you can force WordPress to believe that your server is running Apache by changing your wp-includes/vars.php file. Follow the steps below to implement these changes.
Open the wp-includes/vars.php file using the built in file editor in your WordPress Admin panel.

To navigate to this panel, login to WordPress, click on “Manage”, then on “Files”, scroll to the bottom and type in wp-includes/vars.php into the text box under the “Other Files” title.
Look for
$is_apache = strstr($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) ? 1 : 0;
and replace it with
// $is_apache = strstr($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) ? 1 : 0;
Add a new line under
// $is_apache = strstr($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) ? 1 : 0;
and type in
$is_apache = 1;
Users of XAMPP (Windows): Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it β€” and thus enable WordPress to write the .htaccess file needed to create pretty permalinks β€” you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/ (i.e., delete the hash/pound sign at the front of the line).
Permalinks, .htaccess, and MS Frontpage
A note about Microsoft Frontpage: many servers (shared and dedicated) maintained and built by various hosting companies come with mod_frontpage compiled with the apache build, and in many cases with the Frontpage Server Extensions installed, on each virtual server. This is more common than not, many/most binary distributions used in the server build process at most hosting companies these days include both mod_fronpage and the server extensions. Even if you’re not using Frontpage, because of the way that the extensions interact with apache (and the httpd.conf file) you’ll likely get something like a 500 error or blank white page when trying to view your WP install (although the admin panel may operate correctly) simply because extensions/mod_frontpage exist on your server.

WordPress will operate correctly with the Frontpage Extensions installed, however permalinks will not function at all and ANY change to the permalinks section from the WordPress admin interface will cause corruption of the Frontpage server extensions due to the addition of the mod_rewrite rules to the .htaccess file. There is however now a fix for this situation.

Quick Fixes, Frontpage or Permalinks
Frontpage Extensions Fix: If you don’t care about permalinks and just want to make the MS Frontpage server extensions work again, simply edit your .htaccess file and remove the WordPress section with the rewrite rules.

To Use Permalinks: If you don’t care about Frontpage(but your hosting company has the extensions installed)

You will need to remove (or have your hosting company do so) the MS Frontpage server extensions, or simply edit the .htaccess file to removed all of the Frontpage Lines, leaving only the WordPress mod_rewrite code.

Using FrontPage AND Permalinks Together
Finally, A solution.

There have been a number of threads on this issue in the support forums, and until now, no solution to the problem.

Normally, on a Unix server with the Microsoft FrontPage Server extensions installed WordPress works just fine and you are able to edit and publish pages (with Microsoft FrontPage) β€” until β€” you make a change to the permalinks (for example to the date based kind that I like /2005/04/etc). I often suggest that type of URI to folks asking about permalinks etc, as that is the method recommended by the w3c (see ).

Now, the problem is that FrontPage uses the .htaccess file (which the WordPress mod_rewrite rules must access) for its “publishing” and “web authoring” configuration. As soon as the WordPress mod_rewrite code is added to the file, two things happen β€” the permalinks don’t work and the Frontpage Server extensions become corrupt.

I have tried countless ways to get around this, including trying to use rewrite rules that “ignore” the %{HTTP_USERAGENT)% used by FrontPage, to using a second AccessFilename .wpaccess to the httpd.conf file, and a host of other things, and nothing worked to allow use of FrontPage and management and use of permalinks in WordPress at the same time.

The solution is actually simple, and I figured it out by accident.

If you are using, or wish to use FrontPage (or if your hosting package is pre-configured that way) along with WordPress, you’ll need to take the following simple steps on your server or have your hosting company do them for you.

Microsoft FrontPage creates the following directory

Nested within that it creates both
In addition to in your site (or WordPress) root folder in all of those directories you will find additional .htaccess files.

In all three of these directories AND in the root directory, at the top of ALL of the .htaccess files you simply need to add one line:

Options +FollowSymlinks
There may or may not already be a line in each like

Options None
Edit and save each .htaccess file and you’re done. Now everything works perfectly, including FrontPage, AND the permalinks of your choosing.

Long Permalinks
When using extra long permalinks in email and posting in comments and chats, some long permalinks are “chopped off” or only the first section is actually recognized as a link and the end seen as text. Here is an example.
Can result in:
To click on the lower link, the user would get a 404 Page Not Found Error. If you have a tendency to use very long permalink post titles, take these steps to prevent this problem.

1. Check that you are indeed using Permalinks.

2. Edit your .htaccess file and add the following:

RewriteRule ^post/([0-9]+)?/?([0-9]+)?/?$ /index.php?p=$1&page=$2 [QSA]
3. Test it. Find a post’s ID number and type the following (with your information) in your browser and you should be redirected to your post: ID #)
It is also worth noting that most email software will not cut off URLs that have been delineated with angle-brackets (), so when pasting URLs into emails, you should write them as so:

Read my blog post at
Additionally, some decent email clients offer a “preformat” option when composing plain-text emails. Using the “preformat” option when pasting links will force the email client not to insert linebreaks inside the links.

Fixing Other Issues
If your .htaccess file is being generated correctly, but Permalinks still do not function, the following might be a problem. If problems persist, post a note in the WordPress Forum’s How To section.

AllowOverride Not Enabled
Your server may not have the AllowOverride directive enabled. If the AllowOverride directive is set to None in your Apache httpd.config file, then .htaccess files are completely ignored. In this case, the server will not even attempt to read .htaccess files in the filesystem. When this directive is set to All, then any directive which has the .htaccess Context is allowed in .htaccess files. Example of enabled AllowOverride directive in httpd.config:

Options FollowSymLinks
AllowOverride All

You may also have to enable the AllowOverride directive in your DocumentRoot:

# … other directives…
AllowOverride All

You may also have to change the AllowOverride settings for the site. This is surely the case when using Mac OS X Server, but might be likewise with other systems. Usually you can find the site configuration files in /etc/httpd/sites/
If you don’t want to set AllowOverride to all (as it is above) then your AllowOverride list must include the FileInfo directive. You must restart your Apache server for any httpd.config file changes to take effect. For more information on which overrides are allowed, read about Apache Core Features.
Paged Navigation Doesn’t Work
Sometimes navigation to second (and subsequent) pages of posts does not work as expected. Your page may generate a link to a page with one of these URIs:
The result of clicking one of those links is that the page loads with all the surroundings (header, footer, sidebar), but instead of a page of posts, there is an error message: “Sorry, no posts match that criteria.”
This is due to a glitch in the .htaccess file that WordPress generates. To fix it, delete the contents of your .htaccess file and re-create it.
In the Control Panel, go to Manage > Files (More Info on Editing Files)
Click the link to your .htaccess file to edit its contents
Copy the contents of the file and paste it to a text file in a text editor. This is a precaution in case your .htaccess file has manual entries for redirects, denials or other handy htaccess tricks
Delete all contents from your .htaccess file and click the Update File button.
In the Control Panel, go to Options > Permalinks.
Click the Update Permalink Structure button to freshly generate new rewrite rules for your permalinks.
Test the results using a link that had previously broken.
Add any manual htaccess entries back in your file (Place manual htaccess entries before the # BEGIN WordPress or after # END WordPress lines.)
You may also perform similar steps by deleting the .htaccess files from the server, creating a fresh empty .htaccess file, changing its permissions to 666, and then in Options > Permalinks generate a new set of htaccess rules by clicking the Update Permalinks Structure button.
If that still doesn’t work, take a look at the WordPress support forums, specifically, this support post.
Permalinks to pages don’t work
If you’ve tried to navigate to a newly created Page and encounter an error, you likely need to update your Permalink structure. Remember, each time you add a new static Page to WordPress, new rules must be generated and updated to .htaccess (WordPress 1.X) or to the internal rewrites array (WordPress 2.X).
Permalinks to Ultimate Tag Warrior tag pages don’t work
If you get 404 errors on local tag URLs when using the UltimateTagWarrior plugin on WordPress 2.X, it’s because the internal rewrites generated by WordPress are being overly greedy and getting invoked before UTW’s rewrite rules have a chance. This usually occurs only when using a custom permalink structure (like /%postname%/). To fix it, either switch your Permalink structure to “Date and name based” or hack the UTW plugin to place the UTW rewrites at the top of the internal rewrites array. More Info on this.
Permalinks work but no pages are returned
Some versions of PHP 4.4.x and 5.x have a bug that causes mod_rewrite to fail when used with some versions of Apache 2.x. More details at and
More Help
If these steps do not work, search for your problem in the Codex, Troubleshooting, or in the Support Forum. As a last resort, file a bug report.

Tips and Tricks
If you want to list your site in Google News, one of the requirements is to have at least three digit identifier at the end of every url.

This is easily accomplished using %postname%-%post_id% structure, which will append post ID to the end of URL so it becomes

Having your posts end in .html
There’s an easy way to having your posts end in a .html extension, using the structure tags above. Following the example used on properly terminating permalinks, you could have a page like with this rule:

Note that this does not generate static .html files. It only adds the .html extension, pages are still being dynamically generated. The SEO benefit to this is debatable, but it can be useful should you need to migrate away from WordPress, since the pages can easily be made static and retain their URL structure.

WordPress versions prior to 2.3 lacked canonical URLs, making .html something very beneficial to add (forcing the URL to be canonical). Now it only provides limited, if any SEO benefits (see External Resources for further analysis).

Avoiding interpretation as an archive link
Note that even though one might never make more than one posting a day, and thus wishes to use e.g., %year%%monthnum%%day%, links so generated will however be interpreted as the archive of all posts for that day. One needs at least %year%%monthnum%%day%%hour% to target an individual post.

See Also
Linking Posts Pages and Categories for how to link from one article to another
External Resources
Optimize WordPress Permalinks
Beautify your URLs with Permalinks
How to Configure WordPress to Create Search Engine Friendly URLs for Permalinks
The htaccess Rules for all WordPress Permalinks
URL Rewriting Tutorial β€” the whats, hows and wherefores.
Boost Search Engine Optimisation (SEO) using Permalinks
Understanding WordPress Permalinks
WordPress Permalink Canonicalization using htaccess
Customize and Optimize Your Dated WordPress Permalinks
Clean Permalinks for IIS using .htaccess
The Easiest Lighttpd Rewrite Rule
URL rewriting with lighttpd
Permalinks with Lighttpd β€” using mod_magnet; works on 1.4.2+

Posted in Error in Wordpress | Comments Off on How to fix and solver Permalinks Problem using .Htaccess

Corrupt .htaccess – 500 Internal Server Error wordpress installation !

Posted by Madhurie Singh on September 12, 2009

I was again at the end of my wits, rather even now I am lost ! 😦

I was trying to make my 3 blogs installed in 3 different subdirectories. Since I have created one blog just for the homepage, I obviously want that subdirectory to be accessed by my domain name url, The homepage is in a subdirectory, called homepage.

So I tried to redirect the domain to point to my subdirectory calledd homepage, even when the called URL is !

but when I tried to do a lot of redirects for testing purpose, I suddenly was not able to access the /wp-admin.php. I am getting this weird error, 500 Internal Server Error…..!!!!!!!!!!!

Now I can see from google search that, it’s pretty common problem with Apache Server.

This error occurs when the .htaccess file is corrupted.
Now a sharp experienced eye can make out from the error message what culprit is doing this mischief! But I will have to learn.

Creating and editing (.htaccess)
If you do not already have a .htaccess file, create one. If you have shell or ssh access to the server, a simple touch .htaccess command will create the file. If you are using FTP to transfer files, create a file on your local computer, call it 1.htaccess, upload it to the root of your WordPress folder, and then rename it to .htaccess.

You can edit the .htaccess file by FTP, shell, or (possibly) your host’s control panel.

If your .htaccess file contains errors that bring down your site (“Internal Server Error (500)”), you will need to use FTP or your host’s control panel to delete the rogue .htaccess file.
This para is from Codex site: Very clear:)
Automatically updating .htaccess
If WordPress can’t update your .htaccess file automatically, it will tell you something like If your .htaccess file were writable, we could do this automatically, but it isn’t… near the bottom of the Options β†’ Permalinks panel.

If you want to let WordPress do this, you’ll need to give WordPress write access to the .htaccess file. The exact permissions necessary depend on your server setup. Try adding write permissions for the owner, then group, then world, testing after each change; once WordPress has edited the file successfully, don’t add any further write permissions.

After applying the permalinks, you should change the permissions to something stronger like 660 or 644 to prevent others on the server from potentially having access to it.

Read the next post where I explain how to go step by step and make changes to .Htaccess file.

This site tries to clarify a bit of my query.

But the best way is to do reading of .htaccess on my webhost help base.

This site gives steps of solution that I will now:
How To Fix The WordPress Internal Server Error
Here is what you need to do :

Back up your current .htaccess file.
Delete all of the information from your .htaccess file and save it i.e. upload a blank .htaccess file.
Your blog should now be usable again so go into the admin area and set your permalink structure again.
Open your new working .htaccess file in an editor. Now copy over all the non WordPress .htaccecss information from your old backed up .htaccess file eg. any search engine htaccess information, ip blocks etc – basically everything Non-WordPress that you added before.
If you find that adding all the code from the previous .htaccess file is causing an Internal Server Error again then remove it all and enter the information back to the working .htaccess file line by line to see what is causing the problem.

Bear in mind, this might not resolve every Internal Server Error you get though if you suddenly get this error on your WordPress blog, this is the first thing I recommend doing before contacting your host or looking for an alternative solution.

Copyright Β© 2009 Blogging Tips

I saw this site but do not know how to interpret it :(. Looks like I need to read about the .htaccess file thouroghly now.

One good way to avoid Internal Server Error is by using blog URL as the site URL which I want everyone to remember. I set this in the settings page.
The wordpress URL remains =
The Blog URL changes =

Then copy the index.php file from the subdirectory /public_html/webpage to root directory /public_html

That will avoid the redirection problem totally. Also it will avoid the usage of .Htaccess file for redirection path, as this .htaccess file will not be referred for redirection at all. This way the corruption of .htaccess file by redirection purpose is avoided :).

There are other reasons for the .htaccess file to get corrupted.
In case I activate a theme which has some kind of bug and internal redirection, the .htaccess file is referred to but, when it does not get the right path written down in the instructions, it assumes and goofs up by writing something garbage as path.

So I have learnt that I must not use any theme that is already not tried and tested and upload it only if it is recommended in site.

There are several free themes site from where I can easily download attractive themes. But since I have already encountered a major error (am I lucky) Internal Server Error, using Andreas09 theme that I downloaded from Andreas Viklund’s site, which is not in the available themes of the I could see an error in the footer area of the activated Andreas 09 theme on my site.

So the moral of the error called 500 Internal Server Error,
1: when ever there is any redirection be ware, else .htaccess file will get corrupted.

2: when there is a theme to be activated, look for the most used and recommended theme only.

3: when trying to

Posted in Error in Wordpress | Tagged: , , , , | 19 Comments »

Unable to Create / Upload / Parent Directory not Writable by Server !

Posted by Madhurie Singh on September 6, 2009

I am testing my website before I launch to the world.

I tested earlier by writing a test post, which I could post successfully. πŸ™‚

I want to add an image into a page.

I tried browser uploader but it was too slow. So I tried Flash uploader.
Ok it did start uploading the image, but at the end of the upload it gave me this error 😦
error uploading image parent directory not writable

1. The first thing I am going to check is whether I have the Permission to write in the parent directory or not?

I click the “mysqldatabases” in CPanel. And give all the privileges to the user name that I am using to access the wordpress wp-admin account.
give all privileges to user

Let me check again, if now I can upload image.

Bad Luck ! 😦 Still the same error.

I tried changing the option in Miscellaneous Setting by Unchecking the options create directories of months, but that too did not work :(.

So now I need to know if the database is writable or not. Which means, that there are ways to prevent writing accidentally to the database.

I went to the File Manager through CPanel.

I clicked wp-content directory and changed the permission to 777 from 755.
But still the image cannot be uploaded. 😦

I can feel my brain thickening with frustration.

Lemme shut the laptop and sleep over it. Good Nite πŸ™‚

Ok I am fresh, my lappy is also cleaned, no virus, no dupicates, no garbage. Well I ran an updated AVG to scan and clean system. My poor laptop was struggling to cope up with humungus rubbish! I feel lighter too. Slept at 1:00am, which is early by my standard. πŸ˜› . Hehe

Lemme now start with giving a fresh search on my problem. Wow Google search has given back so much so fast that I am in love with the search engine.

Let me try this link.

It says all that I have tried already. I have checked for the uploads directory, changed the permissions, changed the path, deleted the month and year directories.

Ok the comments also are with me, lots of people are in the same boat like me. Done everything possible yet not able to get the picture uploaded !
So now what?

Hmm there is a comment which says Bard
Here’s what fixed it for me…
Go into Misc Settings and check the address for the uploads folder. Mine had an extra slash.
It should be “wp-content/uploads/”
NOT “/wp-content/uploads/”
08/07/2008 at 11:57 A

no slash changed the writable error

Let me see, if that is the problem. I change my path from /wp-content/uploads to wp-content/uploads

IT WORKS !!!!!

But wait ! Why am I not able to upload the image to my page!
OH GAWD ! Not again !

Step 1. Create a test page and check if it is visible/ accessible on the site . Yes it does.
Step 2. Upload a test image and check. Yes it uploads and is visible too.
Step 3. Rename the test page as Movie Review for Kids. And upload the desired picture. Yes all of these works πŸ™‚

Step 4. Thank the Saviour whose comment helped me .
DONE , Since it’s my lucky day , lemme try and do as much work possible wrt wordpress and my website !

Posted in Error in Wordpress | Tagged: , , , , , , , | 16 Comments »