Recent Posts « How to Build Site from a Blog

How to avoid link name getting chopped or truncated?

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 .

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

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!

How to get API code for wordpress.org?

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 wordpress.com blog not wordpress.org. If I did not have the blog in wordpress.com, I would have to create a blog only for the sake of the API code. How strange?

So I login to my wordpress.com 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 wordpress.org 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!

How to create 404 Error Page

http://www.mattcutts.com/blog/free-direct-text-links/

http://www.google.com/support/webmasters/bin/answer.py?&answer=93641

http://www.google.com/support/webmasters/bin/answer.py?answer=100044&cbid=-6o2s9sgm6no7&src=cb&lev=answer

http://codex.wordpress.org/Creating_an_Error_404_Page

http://www.codinghorror.com/blog/archives/000819.html

http://teqsnacks.com/2007/08/11/wordpress-turning-404-not-found-random-visitors-to-blog-readers/

http://www.gravytrain.co.uk/blog/2009/07/10/how-to-manage-broken-links-and-404-error-pages/

http://www.spotonseoservices.com/custom-404-error-pages-site-usability/

http://www.goldseo.com/news/customize-word/

Some examples of 404 error pages

http://andrewferguson.net/wordpress-plugins/dunstan-style-error-page/

http://www.blogcatalog.com/search.frame.php?term=error+404+wordpress&id=adac469ca34fa44577c7f945d788a294

http://www.blogcatalog.com/search.frame.php?term=error+404+wordpress&id=c154e5fa70de5b126287f8bd9e2c87af

BROKEN LINK REMOVER AND FIXER plugins

http://www.dailyseoblog.com/2009/06/8-wordpress-plugins-to-make-your-404-error-pages-user-friendly-efficient/

http://techblissonline.com/broken-links-remover-wordpress-plugin/

broken-links-remover.zip

http://blog.semetrical.com/link-building-using-404-error-reports/ makes use of 404 for link building!!

How to save custom changes in the existing Atahualpa theme for wordpress.

I have four blogs that I plan to host under one domain name !

Hehehe I know it’s a tall want.

But I know the benefits of promoting one domain with different sections. I could have gone for categorizing the posts but I can foresee that my each blog is catering to different audiences.

So One thing I want is a different themes for each different blog. That way people will get confused.

There is one thing I have already encountered with customization of themes. When I reinstall wordpress or take a back up the settings have to be either re done manually or if if I am sensible, I make a file while has all the settings.

Initially I was using Andreas 09 theme but unfortunately it’s not designed well and has run time error. So I had to switch back to my favourite theme Atahualpa

I am in love with this brilliant theme. I can do so many custom changes but I cannot save these custom changes. That is a drawback which I hope the makers of this theme will get over soon)

One funny thing happened today. I had dark green header. So when I added subscribe by email, I just could not see the words! I was quite fed up. Then I saw an option Over Style and Config. Under it was the first option Body Text Links.
I clicked it and found that by default the link colour is black. So in gark green background it was hardly visible. So what I did was change the link color to #FFFFFF which is white.
Then I went to change the other features. Later while cheching my website I was shocked to find that none of my links were visible. I was wondering now what kind of error was that! Then suddenly I realized that what if the link color had something to do with it. I found the reason for my error links. The links were there, but in while color, hence invisible in white background .
So I changed back the link color to #999999, steel grey color. My problem solved.

In Atahualpa theme, there is a lot that is ready made but still it allows nearly everything to be customized.

If you notice using the same theme I have now three blogs up as three sites under one domain name .

I have tried to keep the basic layout same but changed only the color. The color are also that which I have tried to keep as much close to the wordpress blog.
so www.madhuriesingh.wordpress.com = www.madhuriesingh.com/superindiankid
www.singhmadhuri.wordpress.com = www.madhuriesingh.com/howtobuildsite
www.singhmadhurie.wordpress.com = www.madhuriesingh.com/superindianmom

Now I have one home page www.madhuriesingh.com which redirects to different blogs.
That’s the advantage of going for BlueHost , they allow multiple blogs to be hosted under one single domain name.

To bring the Blog Title in the center, there is no provision. But it can still be achieved by pushing the logo to the right.

So Under Style and Edit the Header Area, edit the Logo Inage :Styling to margin: 0 10px 0px 480px;

I prefer soild border instead of Dashed. So where I see Dashed, I change it to Solid.

Also I perfer to have my PAGES displayed below the logo and images. So I have changed the Configure Header area to %logo %image %pages. I have removed unwanted lines and borders.

The rest of the stuff is easy to handle in Atahualpa.

How to fix and solver Permalinks Problem using .Htaccess

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/mod_rewrite.so (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 http://www.w3.org/Provider/Style/URI ).

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

_vti_bin
Nested within that it creates both
_vti_adm
and
_vti_aut
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.

http://yourdomain.example.com/2005/10/4/article-about-joe-fred-sally-and-bog

Can result in:

http://yourdomain.example.com/2005/10/4/article-about-joe-fred-sally-and-bog

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:

http://yourdomain.example.com/post/(the 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:

http://www.example.com/page/2/

http://www.example.name/category/categoryname/page/2/

http://www.example/year/month/day/page/2/

http://www.example/year/month/page/2/

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 http://bugs.php.net/bug.php?id=35096 and http://bugs.php.net/bug.php?id=35059.
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 http://mysite.com/cooking-tips-tricks-344.

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 http://yoursite.com/2006/01/01/happy-newyear.html with this rule:

/%year%/%monthnum%/%day%/%postname%.html
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+

Code for RSS, Technorati, Digg, Del-ic-ious, subscribe, email for wordpress.

All websites must have at least a single point contact with the site content.

I wanted to add various ways to allow people reading my posts to be in touch with the content and possibly allow them to subscribe to the new posts, comments in general.

I tried a lot but did not fine one single place where I could get all my requirements. Hence this post.

I am pasting the code for all the means that readers use to get linked to my site.

1. BOOKMARK

<!– AddThis Button END –> <!– AddThis Button BEGIN –> <div><a href=”http://www.addthis.com/bookmark.php?v=250&pub=madhuriesingh” title=”Bookmark and Share” target=”_blank”><img src=”http://s7.addthis.com/static/btn/lg-bookmark-en.gif” width=”125″ height=”16″ alt=”Bookmark and Share”></a></div> <!– AddThis Button END –>

2. Technorati

<!– AddThis Button BEGIN –><a href=”http://technorati.com/faves?sub=addfavbtn&add=http://www.madhuriesingh.com”><img src=”http://static.technorati.com/pix/fave/tech-fav-1.png” alt=”Add to Technorati Favorites” /></a><!– AddThis Button END –>

3. DIGG

<!– AddThis Button BEGIN –><a href=”http://digg.com/”> <img src=”http://digg.com/img/badges/100×20-digg-button.gif” alt=”Digg!” width=”100″ height=”20″ /> </a><!– AddThis Button END –>

4. RSS SETTINGS

for subscribing to posts, comments through RSS select Yes for all options.

Select Yes for Subscription By Email, and type Subscription by Email in title.

Write YOURSITEFEEDBURNERID without any space in the the box for feedburner id.

To get my FeedBurner id. I went to www.feedburner.com. Created a google id, login and went to my feeds. Entered the site name for which I wanted a feedburner id. And followed the instructions. There I get my feedburner id.

5. Download Plugin ZIP file for Feedburner Feedsmith from this link

http://www.google.com/support/feedburner/bin/answer.py?answer=78483&topic=13252

And download the zip file to extract FeedBurner_FeedSmith_Plugin.php file
upload it in plugins site and from admin site activate this plugin FeedSmith.

6. Google icon RSS

7. MY YAHOO

8. NEWSGATOR

9. SEND to PHONE

10. Free Dictionary

11. RSS ICON for SUBSCRIBE BY EMAIL

<a rel=”alternate” href=”http://feeds.feedburner.com/YOURSITEFEEDBURNERID”><img src=”http://www.feedburner.com/fb/images/pub/feed-icon32x32.png” alt=”" /></a> < powered by feedburner

2. Thank Feedburner

Creating Multiple subdirectories wordpress installation in one single database one domain.

I am gonna try creating multiple wordpress installations as I have three wordpress blogs that I want to publish in one domain.

I initially thought of trying different database for different installations but then I realised I will have lots of back related work in future!

Also I know my target readers will be nearly the same like minded people who are like me and want all that I seem to be writing about.
So keeping all related data in one database makes sense provided I keep different tables for different wordpress installations.

Now I have done it for my four blogs, ofcourse only the database and wordpress installation part till today.:) But that is an achievement.
I encountered 500 internal server error, then 404 page not found and multiple redirection to a url as errors . But I managed to solve but the internal sever error. See my next post for the 500 internal server error solution.

So to start with when I have three blogs which I want to install in one domain, I must have a way to redirect people to each one of them seprately, right?
So it makes sense that I create a homepage where I will have all the links to my several other blogs.

So for that homepage also I created a separate wordpress installation. I name it homepage obviously.

Since when ever someone types in my domain url i.e. www.madhuriesingh.com, I want it to goto the homepage.

So I create a subdirectory in the root /public_html a subdirectory called “Homepage” and install wordpress in it through the Simple Scripts. All the files are now under one subdirectory call /public_html/Homepage .

Now I make a temporary directory in root directory, and name it “Tempdir”. so I have public_html/Tempdir

Again I select the “Homepage” directory, and copy it into “Tempdir”.

Then I rename this copied directory which has same name as “Homepage” as my new Blog name i.e. “OnlyForKids”

Now I move this subdirectory from “Tempdir” to my root directory /public_html/OnlyForKids

So now under root directory I have three subdirectories

/public_html/HomePage
/public_html/OnlyForKids
/public_html/Tempdir

I delete “Tempdir” .

Now I type www.madhuriesingh.com/homepage .

I am taken to the page where wordpress wants me to enter the Blog Name and my email id .

After I enter the details, a login id and password is generated by wordpress. I copy the password and login the admin page of my blog.

The first thing I do is change the password in my profile page to a more memorable password.

I repeat the same procedure for my other blog and type www.madhuriesingh.com/OnlyForKids.

Again I get new login and new password for the second blog.
I change the password and I own two different blogs under one domain name but a single database.

Now I need to change the URL such that, even when I type www.madhuriesingh.com I am actually redirected to the subdirectory URL www.madhuriesingh.com/homepage !:)

So to enable this, I first goto the admin page of my first blog, HomePage.

I select the settings page.

Here I leave the first URL, i.e. WordPress Blog URL as it is to www.madhuriesingh.com/homepage
but I change the second line i.e Blog URL as typed by others to www.madhuriesingh.com
I save this setting.

Now I go back to the cPanel of my webhost.
Here I locate the index.php file under the subdirectory HomePage.

I COPY (not move) the index.php file from subdirectory HomePage to the root directory /public_html

Now I open the index.php file in any editor.

I goto the line 17 and change the call
require(‘./wp-blog-header.php’); to require(‘./HomePage/wp-blog-header.php’);

I save this index.php file and close it.

Now I type in browser www.madhuriesingh.com

I am taken to the url www.madhuriesingh.com/HomePage directly !

yippppppppyyyyyyy I have done it again !:)

Corrupt .htaccess – 500 Internal Server Error wordpress installation !

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, www.madhuriesingh.com. 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 www.madhuriesingh.com !

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.

This site tries to clarify a bit of my query.

http://www.recommendedwebtools.com/index.php/69/htaccess-and-wordpress/

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

http://helpdesk.bluehost.com/index.php/kb/article/000115

This site gives steps of solution that I will now:

http://www.pupuweb.com/blog/fix-wordpress-internal-server-error/

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.

http://shop.alterlinks.com/htaccess-validator/htaccess-validator.php

http://httpd.apache.org/docs/2.2/howto/htaccess.html

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 = www.madhuriesingh.com/homepage
The Blog URL changes = www.madhuriesingh.com

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 wordpress.org 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 wordpress.org. 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