Webmasters can however utilize tag pages better in their Wordpress blogs by creating so called custom tag pages which can contain any information they want. If you open the page above you notice that it does not contain a listing of blog excerpts but a custom page for that tag.

Wordpress provides the means to create those custom tag pages easily. Custom tag pages can be created in the theme directory of the Wordpress directory by adding a new template file to the theme. This new template file needs to begin with tag followed by the post slug of the tag. In the case of the Windows 7 Download tag it would have to be named tag-windows-7-download.php.

Custom tag pages have a higher priority than the default ones that show only excerpts of the posts. The easiest way to fill the custom tag with content is the following:

Wordpress looks for the following files in order to create those tag pages:

• tag-slug.php
• tag.php
• archive.php
• index.php

Look into your theme folder and see if there is a tag.php file. If it is copy its contents and create a new php file that is using the tag-slug.php as its name. If ther eis no tag.php look for archive.php and finally index.php.

Now simply add content to the file. It might take some experimentation at the beginning but it can be really worth it in the long run. If you have any questions or additions let me know in the comments.

Related posts

• Wordpress: Your attempt to edit this post has failed (8)
• Wordpress 2.6.5 Security Update (0)
• How to show 5 top categories in Wordpress (9)
• Zoundry Raven portable Blog Editor (6)
• Wordpress SEO: Advanced Nofollow (3)

You can download the latest version of Wordpress from the official website or apply the upgrade manually in the Wordpress interface. You can take a look at in depth file changes by following this link or at the 68 tickets that have been closed here.

The update includes six tickets with a high rating and more than 50 rated as normal. While the update does not list many security fixes it is still recommended to update as soon as possible. The update will not alter the database and should not break anything including plugins or themes.

Related posts

• Wordpress 2.6.5 Security Update (0)
• Wordpress 2.5.1 released (1)
• Wordpress: Your attempt to edit this post has failed (8)
• Wordpress Issues (16)
• Wordpress Incorrect Password (2)

There have been some problematic messages occasionally when trying to publish posts lately. The error message Your attempt to edit this post [..] has failed appeared occasionally after upgrading to Wordpress 2.7. Wordpress was not able to publish the article which was bad enough but the underlying problem was that all work up to the point of the last auto save was lost as well.

This usually meant that the tags, categories and other last minute edits (like urls) were missing from the posts and had to be added again. The second edit and publishing always succeeded without difficulties.

The first thought was that this could have something to do with the automatic saves of posts before publishing. A quick research on the Wordpress support forum seemed to confirm that.

The fix is apparently the following:

Locate the file post-new.php in the wp-admin folder of the Wordpress installation. Find the following line in that file wp_enqueue_script('autosave'); and replace it with //wp_enqueue_script('autosave');.

The // in front of the row make the entire row a comment which essentially means that the command will not be executed. This will practically disable auto save during post publishing meaning that you will hacve to click on the Save Draft button before you leave an unfinished post page.

Related posts

• Wordpress Blogs: Create Custom Tag Pages (5)
• Wordpress 2.6.5 Security Update (0)
• Flash 10 Breaks Wordpress Flash File Uploader (3)
• Zoundry Raven portable Blog Editor (6)
• Wordpress Remote Admin Password Reset Vulnerability (13)

Alternatively only the files wp-includes/feed.php and wp-includes/version.php can be copied from the new release over the old files to update the blog. The security vulnerability is unlikely to affect a large number of Wordpress blogs though as it only only affects IP-based virtual servers running on Apache 2.x.

There might also be some confusion about the versioning of Wordpress. The last official Wordpress version was Wordpress 2.6.3. Wordpress 2.6.4 was skipped because of a fake malicious release that made its round. The official new release is therefor Wordpress 2.6.5.

Related posts

• Wordpress 2.8.2 Security Patch (1)
• Wordpress 2.7.1 Update (3)
• Wordpress 2.6.1 released (1)
• Wordpress 2.5.1 released (1)
• Wordpress: Your attempt to edit this post has failed (8)

So far so good. Several issues appeared over time that I would like to address in this short article. I tried to fix them before but I failed to really find solutions for them. I did post a few help requests at the official Wordpress forum which remained unanswered even after pushing them a few times and a search on Google did not return the desired results as well.

So, here we start with my personal Wordpress issues that other webmasters might also experience:

• Akismet is not perfect: Akismet is the default Wordpress anti-spam plugin which is delivered with the default installation of Wordpress. That puts it in an unfair advantage over other spam plugins like Spam Karma which is in many aspects a better plugin. But I do not want to talk about politics here. Akismet comes with no configuration options at all. The only things that can be added are the Wordpress Api Key which is mandatory and a checkbox to delete spam that is older than a year.

  If you compare it to Spam Karma you are comparing Notepad to Notepad++. That’s the difference in usability. Akismet divides spam into user comments, trackback and pingback spam but it is not possible to delete only one category. The delete all button always deletes all spam.

  Akismet does have a search field but that search field is global, there is no way to only search the author name, email or filter by other parameters like only showing posts with one link or less in the body.

  It does catch quite a few valid comments which are then lost forever because it is impossible to work with Akisment on websites that get 1000+ spam comments a day unless you do that full time.

• Spammers can still register accounts although registration has been turned off: When I turn off registration to my website in the settings of Wordpress I expect to see no new users in the future unless I add them manually. The option however does not really help because even though it has been turned off spammers can still register accounts on my blog.
• There is no history: – The admin cannot see what authors or subscribed users of the blog have been doing. He cannot see if an author deleted an article that he wrote earlier, he cannot see if a user edited or removed a comment.
• Publishing an pending article: When someone else with not enough user rights is writing an article that article gets added to the Pending Articles and an user with enough rights can publish it after reviewing it. The problem that I face is that I have a hard time figuring out how to publish the article so that it is published in that instance and not in the past. If I just hit publish the article is published when the author of it saved the final version. This can be a few hours or even a few days in the past.

  I have not investigated that matter further but I suppose it could be problematic for RSS Feeds and even the site itself. I tried to change the date to the current one and publish it but it still felt like I missed something here. It’s definitely a strange behavior in my opinion.

Those are my issues with Wordpress and I always cross my fingers and hope that they get fixed in one of the next updates.

Related posts

• Zoundry Raven portable Blog Editor (6)
• Wordpress: Your attempt to edit this post has failed (8)
• Wordpress Blogs: Create Custom Tag Pages (5)
• Wordpress 2.7.1 Update (3)
• Wordpress 2.6.5 Security Update (0)