First, is the cipler-none patch that adds none as a valid argument to the -c command line option. By using it, the transferred data is not encrypted. Pros: eliminates the data encryption overhead. Cons: totally insecure method of transferring sensitive data.

cipher-none-patch

Note: the OpenSSH server, even if it has been patched with this code, does not accept unencrypted connections by default. This has to be enabled explicitly in the sshd configuration (sshd_config) by adding the none “cipher” to the list of the accepted ciphers:

Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr,none

Note2: here is step-by-step guide how to configure the SSH authentication using public keys.

Second, is a set of patches, created at the Pittsburgh Supercomputing Center, which eliminate the bottlenecks caused by some of the internal buffers that control data flow in network connections through OpenSSH. This project is called High Performance SSH/SCP (aka HPN-SSH). Benchmarks show that even encrypted network connections using HPN-SSH perform extraordinarily better than the usual encrypted OpenSSH connections.

OK, this info exists here for completeness, as those HPN-SSH patches have not been designed for home networks! Possibly it might make no difference if you use the regular OpenSSH or HPN-SSH in your home LAN.

Note: the HPN-SSH patches also contain code that adds the none cipher, similar to the cipher-none patch, so, if you intend to use HPN-SSH, it is not required to apply both on the OpenSSH source.

Finally, apart from all these, if you ever decide to use SSH for networking seriously consider using SSHfs (see also SSHfsFAQ).

Related Articles

• How to configure mod_gnutls to use the RC4 cipher to mitigate the SSL/TLS vulnerability
• Assign Virtual IPs to your NIC
• Setup the SSH server to use keys for authentication
• Encrypt devices using dm-crypt and LUKS
• TrueCrypt on 2.6.18 kernels

Taking these things into consideration, I decided to write Fast-Static-Feed, a plugin that can cache the site’s entries feed, and deliver a static XML file instead of constantly generating the feed content on every client request. This, combined with the fact that the web server can compress the web content on-the-fly, has greatly reduced the waste of bandwidth and system resources.

How it works

Fast-Static-Feed performs the following actions:

• Every time a post is published or an already published post is edited, the plugin dumps the entries feed (that is the feed of the blog posts) to a file. This way, the static XML file is always contains the most fresh content of your blog.
• Every time a feed is requested, instead of re-generating the XML content over and over, this plugin delivers the static XML file. This is completely transparent to the client as there are no HTTP redirects involved. Your content is just being delivered faster!
• If the plugin is enabled, but the static files have not been created yet, the plugin will try to generate them automatically. Upon failure to do so, a 404 Not Found HTTP error code will be returned to the client.
• It also checks if the client’s request includes the If-Modified-Since HTTP header and, in such a case, it checks the static file’s modification time. If the client’s cache is current, it just returns a 304 Not Modified status to further reduce bandwidth usage.

The plugin caches all four types of feeds WordPress supports -RSS 2.0, Atom 1.0, RDF, RSS 0.92-.

Only the feeds that contain your blog posts are cached. The comments feed, each individual post’s comments feed, feeds for categories, tags, authors etc are still generated dynamically every time they are requested.

This plugin does not interefere in any way with the generation of rewrite rules and the generation of your site’s feed links.

Configuration

Generally, the plugin does not require any configuration in order to work.

One mandatory prerequisite is that the wp-content/ directory is writable by the web server. If it is not, the plugin will not be able to create the static files and, consequently, the clients who request a feed will receive a 404 Not Found HTTP code.

Furthermore, there are two options within the source code fast-static-feed.php that can be set.

// By default, the WordPress feeds contain elements of the 'wfw' namespace
// (CommentAPI), so a feed reader can fetch each feed entry's comments.
// By setting the following to 1, these elements will be stripped
// from the static feed.
// It is recommended to set this to 1 in order to save bandwidth.
// More info: http://wellformedweb.org/news/wfw_namespace_elements/
$FSF_STRIP_COMMENTS = 0;
// Set the following to 1 and various messages will be recorded in the logfile,
// which is located in the cache dir (wp-content/cache-xml/)
$FSF_DEBUG = 0;

It has already been mentioned, but it is important to note it again: The only mandatory prerequisite is that wp-content/ is writable by the webserver.

Installation

Make any changes to the configuration options within fast-static-feed.php and upload the file to wp-content/plugins/ directory. Then, activate the plugin through the WordPress administration panel.

License

Fast-Static-Feed is an open-source project, released as Free Software under the terms of the Apache License version 2.

Downloads, Issue Tracking, Support

For the latest releases of Fast-Static-Feed please visit the downloads section of the Fast-Static-Feed Development Portal.

The development website also hosts an issue tracking facility, where you can submit your feature requests or report bugs, and discussion boards, where you can get first class support from the community of users.

Donate

This plugin is released as free software. Nevertheless, its development requires time and effort. A small donation, as a sign of appreciation of the effort, is welcome. Please, use the following button to visit the Donations page. Thanks in advance for your support!

Related Articles

• More-Feed-Excerpt WordPress Plugin
• Bot-Allow-Content WordPress plugin
• How to enable WP-Super-Cache in WordPress
• Add-Meta-Tags WordPress Plugin
• My-Tags WordPress Plugin

Introducing mod_deflate

Apache prepares the response that will be sent back to the client in several stages. One of those stages involves the modification or conversion of the data using output filters. mod_deflate, once loaded and activated, inserts such a filter, named DEFLATE, in Apache’s chain of output filters, which compresses all data that goes through it according to some rules the web server administator has defined. For instance, one can set the compression level, restrict the compression to particular MIME types or prevent some problematic web browsers or other HTTP clients from receiving compressed data from the server.

mod_deflate also offers an input filter which can be used to decompress compressed HTTP requests, but this feature is outside of the scope of the current document.

Here follow some instructions on how to configure mod_deflate. Most of it can be found inside HTTPd’s official documentation, so you’d better read this resource as well.

Note that all of the following configuration directives can be inserted in Apache’s main server context or can be saved to a file that will be loaded from within the main server or any other virtual host context. If the configuration directives are inserted in the main server context, then they will be inherited by all virtual hosts.

Load mod_deflate

mod_deflate can be loaded like any other Apache module:

LoadModule deflate_module modules/mod_deflate.so

Please note that this directive can only exist in the main server configuration.

Enable Compression

The compression of the data can be enabled for all data that goes through the DEFLATE filter or selectively depending on its MIME type.

To enable the compression for any type of content, insert the following directive:

 SetOutputFilter DEFLATE

Alternatively, to define which filetypes should pass through the DEFLATE output filter use the AddOutputFilterByType directive. The following is an example:

AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript

Set the Compression Level

Generally, the deflate compression algorithm is fast enough, so setting the compression level to the maximum (9) will not cause any noticeable trouble, even to relatively old hardware.

DeflateCompressionLevel 9

Custom Rules for problematic browsers

The compression can be turned-off or be restricted to files of type text/html for known problematic web browsers. These are taken from the official documentation.

BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html

Keep track of the compression

Finally you can keep track of the compression in order to evaluate the effectiveness of the use of mod_deflate in your server.

The following directives define some variables, such as:

• instream : the size in bytes of the data as received by the DEFLATE filter.
• outstream : the size in bytes of the compressed data as returned from the DEFLATE filter.
• ratio : the compression ratio, (Output/Input)x100

DeflateFilterNote Input instream
DeflateFilterNote Output outstream
DeflateFilterNote Ratio ratio

Finally, you can define a custom logformat so to be able to record the aforementioned values to a logfile:

LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate

The deflate logformat can be used for the main server’s or for any vhost;s logfile.

Effectiveness of Compression

It is well known that not all document types can benefit the same from compression. Generally, the deflate algorithm can compress text surprisingly fast and with a very high efficiency ratio. On the other hand, it is almost useless when used to compress images which have been prepared for the web such as PNG, JPEG, GIF and generally all other image types in which the data has already been compressed. The same goes for compressed audio files, such as MP3, AAC, OGG, videos, PDF documents and all other already compressed files.

So, the benefits of using mod_deflate to reduce the bandwidth usage and speed up the content delivery are heavily dependent on the type of files your web server delivers.

Browser Support

A web server that sends compressed data to clients would be completely useless if the HTTP clients couldn’t decompress that data. All modern and popular web browsers support accepting content that has been compressed using the gzip or deflate algorithms, so there should be no problem at all.

Appendix I

Here is the complete mod_deflate configuration as described in this article. Save it in a file, named deflate.conf and import it in the main server’s configuration using the Include directive

(Include /path/to/deflate.conf):

#
# mod_deflate configuration
#
LoadModule deflate_module modules/mod_deflate.so
<IfModule mod_deflate.c>
        AddOutputFilterByType DEFLATE text/plain
        AddOutputFilterByType DEFLATE text/html
        AddOutputFilterByType DEFLATE text/xml
        AddOutputFilterByType DEFLATE text/css
        AddOutputFilterByType DEFLATE application/xml
        AddOutputFilterByType DEFLATE application/xhtml+xml
        AddOutputFilterByType DEFLATE application/rss+xml
        AddOutputFilterByType DEFLATE application/javascript
        AddOutputFilterByType DEFLATE application/x-javascript
        DeflateCompressionLevel 9
        BrowserMatch ^Mozilla/4 gzip-only-text/html
        BrowserMatch ^Mozilla/4\.0[678] no-gzip
        BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
        DeflateFilterNote Input instream
        DeflateFilterNote Output outstream
        DeflateFilterNote Ratio ratio
        LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
</IfModule>

This configuration will be inherited by all virtual hosts.

To disable it just comment out the line that loads the mod_deflate module (#LoadModule ...).

To record mod_deflate‘s specific variable (instream, outstream, ratio) values for a virtual host, just add a new log file of type deflate:

CustomLog /path/to/vhost/logs/deflate_log deflate

This will give you an idea of how efficient is the use of mod_deflate in that particular vhost.

Related Articles

• Optimize and Compress CSS Files
• SSL-enabled Name-based Apache Virtual Hosts with mod_gnutls
• Script for Apache Error Report
• Speed up Apache by including htaccess files into httpd.conf
• Check Server HTTP Headers with CURL

Copy the file to your bbPress root directory, decompress it and apply it:

$ gunzip registration-functions.php.patch.gz
$ patch -p0 -b < registration-functions.php.patch

Here follows the full patch:

--- bb-includes/registration-functions.php	2007-07-10 13:29:56.000000000 +0300
+++ bb-includes/registration-functions.php.new	2007-07-10 13:29:50.000000000 +0300
@@ -41,11 +41,10 @@
 	$resetkey = bb_random_pass( 15 );
 	bb_update_usermeta( $user->ID, 'newpwdkey', $resetkey );
 	if ( $user ) :
-		mail( bb_get_user_email( $user->ID ), bb_get_option('name') . ': ' . __('Password Reset'), sprintf( __("If you wanted to reset your password, you may do so by visiting the following address:
-%s
-
-If you don't want to reset your password, just ignore this email. Thanks!"), bb_get_option('uri')."bb-reset-password.php?key=".$resetkey ), 'From: ' . bb_get_option('admin_email') );
+		$message  = sprintf(__("%s,\n\nA request to reset the password for your account has been made at %s\n\nIf you wanted to reset your password, you may do so by visiting the following address:\n\n%s\n\nIf you don't want to reset your password, just ignore this email. Thanks!\n"), "$user->user_login", bb_get_option('uri'), bb_get_option('uri')."bb-reset-password.php?key=".$resetkey );
+		$message .= sprintf("\n______\n%s\n%s [%s] %s %s\n", __("Password reset request details:"), $_SERVER['REMOTE_ADDR'], gethostbyaddr($_SERVER['REMOTE_ADDR']), __("at"), date("Y-m-d\TH:i:sO"));
+		mail( bb_get_user_email( $user->ID ), bb_get_option('name') . ': ' . __('Password Reset'), $message, 'From: ' . bb_get_option('admin_email') );
 	endif;
 }
@@ -62,7 +61,7 @@
 			bb_block_current_user();
 		if ( !$user->has_cap( 'change_user_password', $user->ID ) )
 			bb_die( __('You are not allowed to change your password.') );
-		$newpass = bb_random_pass( 6 );
+		$newpass = bb_random_pass( 8 );
 		bb_update_user_password( $user->ID, $newpass );
 		bb_send_pass           ( $user->ID, $newpass );
 		bb_update_usermeta( $user->ID, 'newpwdkey', '' );
@@ -85,7 +84,7 @@
 	return $user_id;
 }
-function bb_random_pass( $length = 6) {
+function bb_random_pass( $length = 8) {
 	$number = mt_rand(1, 15);
 	$string = md5( uniqid( microtime() ) );
  	$password = substr( $string, $number, $length );
@@ -98,7 +97,8 @@
 	$user = $bbdb->get_row("SELECT * FROM $bbdb->users WHERE ID = $user");
 	if ( $user ) :
-		$message = __("Your username is: %1\$s \nYour password is: %2\$s \nYou can now log in: %3\$s \n\nEnjoy!");
+		$message = __("%1\$s,\n\nThank you for registering at %3\$s.\n\nYou may now log in at %3\$sbb-login.php using the following username and password:\n\nusername: %1\$s \npassword: %2\$s \n\nAfter logging in, you may want to visit %3\$sprofile-edit.php so you can change your password.\n");
+		$message .= sprintf("\n______\n%s\n%s [%s] %s %s\n", __("Registration request details:"), $_SERVER['REMOTE_ADDR'], gethostbyaddr($_SERVER['REMOTE_ADDR']), __("at"), date("Y-m-d\TH:i:sO"));
 		mail( bb_get_user_email( $user->ID ), bb_get_option('name') . ': ' . __('Password'),
 			sprintf( $message, "$user->user_login", "$pass", bb_get_option('uri') ),
 			'From: ' . bb_get_option('admin_email')

I hope WordPress does not mess up the backslashes.

Related Articles

• bbPress for WordPress
• Permanently remove deleted posts and topics in bbPress
• HTTP Status Codes
• A temp solution for the is_preview WP issue

First, I do not remember being warned about running out of free space. GNOME is supposed to do this, but, in my case, either it did not raise that warning message or I was too focused on my work so I didn’t notice it. I’d bet that the latter is what actually happened.

Second, I have setup several profiles in firefox and I have adjusted its launcher in the GNOME menu to start the profile manager each time I want to use the browser. Firefox keeps the profile information in the ~/.mozilla/firefox/profiles.ini file. Under the “no free space” conditions, something had caused the file to be re-created as a zero-size file, losing all of my profile information. Fortunately, this was the only file that was affected. My profile directories were in tact, so it was rather easy to recover from this situation by setting my profiles again with the profile manager.

The third observation has to do with the FTP client, gftp. As I have mentioned earlier I was also working with this client when I run out of free space. It is strange to me how some things happen sometimes, but at that moment I was adding some ftp sites to the gftp bookmarks. Well, it seems that if you happen to save your bookmarks or settings in gftp while there is no free space in the partition that holds gftp’s config files, you are LOST! All the files in ~/.gftp/ are replaced with zero-size files and all your settings and bookmarks are lost, unless you have a recent backup of them. Well, I didn’t have one and that’s why I was angry (against myself). This was fixed – but not my bookmarks :-( – by completely removing the ~/.gftp/ directory and getting it recreated when launching gftp.

After this incident, I kept wondering if there were more configuration files in my user account’s home that were affected. I guess it is impossible to know in advance. Time will show.

An application which acted absolutely professionally and actually was the one that made me realize that there was something wrong with the free space is Evolution. It displayed proper warning messages about not being able to write the newly fetched email and news messages to the disk and, generally, the problematic situation had absolutely no effect on it. I take my hat off to Evolution (v2.8.3).

This incident made me think if software developers ever test how their software would behave if there is no free space available, especially if its usage involves reading/writing/appending from/to files. I would bet that other programs might have problems under such conditions too, but I guess these situations are rare. On the other hand, if it happens and the software is not designed to work well, then your personal data could be at risk. At this point, I am rather happy I was not running my password manager at that critical period of time! ;-)

Anyway, as I have already written earlier, I blame noone. Unfortunately, I do not have the required free time or will to reproduce those errors in a test environment, but I guess I will do this at some later time. All the above might just be wrong conclusions and something else might was the cause of the problem. I really do not know, but I felt like writing about that experience.

Related Articles

• Featured Epiphany Plugins
• Descramble Passwords from gftp Bookmarks using Python
• Testing gnome-blog-poster…
• Epiphany Browser Review
• Access gvfs mounts from the command line

I would like to thank all who have provided their feedback, either positive or negative. The important thing is that, in either way, you have contributed to the deverlopment of this plugin.

This is by far the most popular of the plugins I have written so far and I have been maintaining, fixing and actively supporting it for over a year now. If you use this plugin and would like to give something back, I’d be happy to read a small review on your blogs. ;-)

Related Articles

• Add-Meta-Tags WordPress Plugin
• Add-Meta-Tags and WordPress 2.3
• Announcement: Add-Meta-Tags v1.5 for WordPress
• Add-Meta-Tags – Legacy
• Remove-Generator-Meta-Tag WordPress Plugin

Before proceeding, make sure you have backed up your current non-optimized style-sheet. CSSTidy will not touch your original file, but taking some precautions is a good habit.

Launch csstidy without arguments for a rather short description of the command line switches:

csstidy

Although it is possible to define each parameter individually, some pre-defined templates are what you will most probably use. These include: low|high|highest. The higher the optimization level, the smaller the CSS filesize. More on templates here.

I tried the high and highest templates. The latter produces a style sheet that contains all code in a single line, but that file would not validate, so I used the high template:

csstidy style.css --template=high style.css.out

The compression ratio for my file was 34.86% which was quite satisfactory. Also, the final file validated properly.

CSSTidy does a good job either you want to optimize the stylesheet for readability or for filesize. On the other hand, the CLI interface does not provide enough information about each of the CLI switches. They are pretty self-explanatory, but I guess a little description for each one of them wouldn’t hurt anyone. Also, I could not make the “--remove_last_;” option to work.

The only difference I could notice in my stylesheets between the high and the highest templates was that the whole code was squeezed in a single line when highest was used. Probably, this template performs some more optimizations than just deleting the line-feed characters, but it seems that there was nothing else that could be optimized in my CSS file.

Apart from this command line utility, there are also a lot of online CSS optimizers. I didn’t have the time to try them all, but I think I can recommend the following:

• Clean CSS – this seems to be the PHP version of CSSTidy. Everything seems to work as expected and the results are the same as before.
• Icey CSS Compressor – This is another web-based CSS optimizer which performs very well. By using the default settings you get a single line with highly optimized CSS code. The compression ratio is similar to CSSTidy’s. In order to separate each selector with a line-feed character, so that the final CSS validates, you can pass the optimized CSS through sed:

  sed -i 's/}/}\n/g' style.css.out

If anyone knows about any other utility I would be very glad to know about.

Related Articles

• Use mod_deflate to Compress Web Content delivered by Apache
• VeriTAR – Verify checksums of files within a TAR archive
• How to annotate PDF files in Linux using Xournal
• Creative-Commons-Configurator WordPress Plugin
• WordPress 2.2.1 bugs

The features at a glance

The following list outlines how and where META tags are added to a WordPress blog by this plugin. Please note that this list does not provide all the details you need to know about how to customize the added metatags. Its purpose is to provide a general idea of what this plugin supports. For detailed info, proceed to the next section.

• Front Page
  • Automatically.
  • Customization is possible from the plugin’s configuration panel.
• Single Posts
  • Automatically. (On WordPress v2.3 or newer tags are also used in addition to the post’s categories)
  • Customization of the “description” META tag:
    • either via custom excerpt
    • or via custom field (note that this overrides the custom excerpt).
  • Customization of the “keywords” META tag via custom field only.
• Static Pages
  • No automatic generation of meta tags.
  • Customization is possible with custom fields like it can be done in posts.
• Category Archive Pages
  • The description of the category, if set, is used for the description META tag. The name of the category is always used at the keywords metatag.
• META Tags on all pages
  • It is now possible to set any other META tag, which does not require any computation, to be added to all blog pages.

Here follow all the details about how this plugin works.

Features – How to use it

The simplest way to use this plugin is to activate it in the WordPress administration panel and forget about it. At this basic level of usage, it automatically adds the “description” and “keywords” META tags to the front page and to single post view, which, of course, can be customized in the ways outlined below.

META Tags on the Front Page

By default, the blog’s tagline (Options->General) and all the used categories are being used automatically as description and keywords for the meta tags on the front page. These can be overridden by setting a custom description and keywords for the front page in the plugin’s configuration panel (Options->MetaTags).

The description and keywords defined in the plugin’s configuration panel have higher priority and, if any of them is set, it will be used instead of the automatically calculated respective metatag.

META Tags in Single Posts

In single post view, the post’s excerpt and its categories and tags (tags are supported in WordPress 2.3 or newer) are automatically used as description and keywords. While editing a post, it is possible to define a custom excerpt. If this excerpt is not set, then the description is calculated from the post itself. This calculation is based on the following:

1. the plugin tries to use the first complete sentences of the post, if possible.
2. it also tries to keep the calculated excerpt at a length around 250 characters. As you can guess, this cannot be always achieved, so I’d say that the calculated description will be about 150-350 characters.

This automatic behaviour can also be overridden, by adding custom fields to the post. Note that the custom fields have the higher priority and, if set, their values are used in the META tags.

The contents of a custom field named description will be used in the description META tag instead of the post’s excerpt.

Contrariwise, a custom field named keywords can contain a comma-delimited list of keywords, which will be used in the keywords META tag instead of the post’s categories and tags. It is still possible though to quickly include the post’s categories and tags to this list by using the words %cats% and %tags%, which are replaced by the post’s categories and tags respectively when the page is displayed in a browser.

For example, when the post’s categories are not enough and tags are not enough for you, you can add a custom keywords field to the post, and add the extra keywords you want together with %cats% and/or %tags% :

keyword1, keyword2, %cats%, %tags%

This makes it possible to adjust and optimize the post’s keywords without having to create a huge number of blog categories and tags.

META Tags in Pages

It is possible to add the description and keywords meta tags in WordPress Pages by assigning custom fields to each page as it was discussed previously for posts. Pages do not belong to categories in WordPress, so metatags will not be added automatically without using custom fields. Also, the tag %cats%, if used in the keyword list, will not be replaced by any categories.

META Tags in Category Archives

Finally, META tags are automatically added to category archive pages, for example when viewing all posts that belong to a specific category. In this case, if you have set a description for that category, then this description is added to a “description” META tag.

Furthermore, a “keywords” META tag – containing only the category’s name – is always added when viewing category archives.

Installation

Extract the compressed package in a temporary directory and copy the add-meta-tags.php file in your /wp-content/plugins/ directory and activate the plugin in your administration panel (Options->Meta Tags).

As it has been mentioned, no configuration is required for the plugin to function. It will add meta tags automatically to the front page and to each post in single post view.

The administration page (Options->Meta Tags) contains all the information that was mentioned in the previous section, so you can access it quickly.

License

Add-Meta-Tags is an open-source project, released as Free Software under the terms of the Apache License version 2.

Downloads, Issue Tracking, Support

For the latest releases of Add-Meta-Tags please visit the downloads section of the Add-Meta-Tags Development Portal.

The development website also hosts an issue tracking facility, where you can submit your feature requests or report bugs, and discussion boards, where you can get first class support from the community of users.

Translations

Add-Meta-Tags is ready for localization.

Generally, the installation of the translation file involves copying the mo file in the plugins directory, where add-meta-tags.php exists.

Translation files are hosted by their authors and are distributed separately from the main plugin.

Currently available translations:

• Japanese Translation by coliss – This is the translation of the 1.6 version of the plugin.

A huge thanks to all for your work.

Donate

This plugin is released as free software. Nevertheless, its development requires time and effort. A small donation, as a sign of appreciation of the effort, is welcome. Please, use the following button to visit the Donations page. Thanks in advance for your support!

Other Info

This page had become the heaviest page on this web site (>120kb), so some sections have been removed to save some space and bandwidth.

The list of contributors has become too big for this page, so it has been moved inside the distribution package (file THANKS).

The changelog has been removed and is included inside the distribution package (file ChangeLog).

The comments can be found at the Add-Meta-Tags Legacy page.

Thanks for your understanding.

Related Articles

• WordPress Meta Tags plugin stable release
• Announcement: Add-Meta-Tags v1.5 for WordPress
• My-Tags WordPress Plugin
• Add-Meta-Tags – Legacy
• Add-Meta-Tags and WordPress 2.3