This post is about automatically generating sitemaps. I chose this topic, because it is fresh in my mind as I have recently started using sitemaps for Podcastpedia.org After some research I came to the conclusion this would be a good thing – at the time of the posting Google had 3171 URLs indexed for the website (it has been live for 3 months now), whereby after generating sitemaps there were 87,818 URLs submitted. I am curios how many will get indexed after that…

So because I didn’t want to introduce over 80k URLs manually, I had to come up with an automated solution for that. Because Podcastpedia.org was developed with Java, it came easy to me to select sitemapgen4j

Maven depedency

Check out the latest version here:

	com.google.code
	sitemapgen4j
	1.0.1

Podcastpedia.org makes use of Apache Tiles for its layout. This approach was taken because the website pages share a similar structure. Please read first the Getting started guide and Tiles concepts to have a better understanding of what follows. This post will present how Tiles is integrated with Spring MVC for Podcastpedia.org

Note: Spring is the basic technology used for developing Podcastpedia.org

Necessary artifacts

First of all Tiles jars are required in the classpath. They can be directly downloadded from the official website, but Tiles has also been published to the public Maven repository.

You can use one dependency to download all Tiles supported technologies with the following dependency declaration:

<dependency>
    <groupId>org.apache.tiles</groupId>
    <artifactId>tiles-extras</artifactId>
    <version>2.2.2</version>
</dependency>

My first entry in the blogosphere is not “About us”, but about the problems I encountered trying to install WordPress on my GoDaddy Virtual Private Server (VPS).

For the installation I followed the steps from Installing WordPress. Everything went fine until Step 5: Run the Install Script. After calling https://www.codepedia.org/wp-admin/install.php , my excitement to have finished quickly finished the installation was ruined by the infamous

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@codepedia.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.