Since I’m currently in the process of entering a new market (Software for mobile devices), I’m looking for at least one talented logo / graphics designer. The software (several very different products) I’m currently developing will be free of charge, so I won’t be able to pay you in the short term. Work will start with a couple of logos and later expand.

What’s in it for you:

• You will be credited both in the distributed software and on any support pages.
• Since I usually hit a nerve after a couple of attempts and/or different applications (and I will bring that to a whole other level) this could make you quite popular in the long term.
• As soon as I have developed a business model we can switch to “monetary forms of payment” if you prefer that.

Some things to consider:

• Some apps will be provided by entities different from me (uberdose), that is, other brands and/or creators, but the terms you and me agreed to stay the same. They are fully endorsed and marketed by me and I have enough control over the content to ensure our terms.
• Since I will communicate very sensitive information to you before product releases I expect you to act under NDA.
• This is intended as a long-term agreement and the rewards might take some time, so your making-a-living should be secured somehow.

I know I could actually hire as many designers as I want, it’s not a financial problem. But I’m looking for a long term relationship that’s not focused on money but on something beyond and I hope to attract the right kind of people with this post. The money will follow anyway.

If you are interested please leave a comment … If you want to do this anonymously just put a link in your comment body (starting with http:// …) so you will land in the moderation queue and not be published.

• Backup!
• Rename the OldProject.xcodeproject, and the folder it is in.
• Inspect the contents of your OldProject.xcodeproject (”Show Package Contents” in finder), there should be a file project.pbxproj. Edit that in your text editor. I used Emacs, but I guess you should be fine with any decent editor that repects the character encoding. Close the project before editing, or make sure your editor auto-loads changed files.
• In project.pbxproj, replace some occurrences of your old project name with your new one. Don’t replace anything in comments, and no filename replacements (like OldProject.m). Some important locations are OldProject.app (there should be one occurrence where it’s not in a comment) and some constructs with “path”, “PBXProject”, “PBXNativeTarget”, “PRODUCT_NAME”, “productName”, “name”.
• Test loading, building and running the project. It should work as before and feature your new project name in the relevant locations (e.g. it should be NewProject.app now). If xcode complains about corruption it might be because you ignored character encoding or didn’t hit all locations of OldProject.
• Optional: As soon as your project is working as before, you can rename all your source files that have OldProject in their name and all references (like #import and the like). This might take some time in a large project.
• Optional: If you renamed your source files, your xibs will probably be wrong too. Correct all references to OldProject until your app is running smoothly again. Also check your code if you’re using “initWithNibName”.
• Done! You should probably test your app thoroughly, especially if you’re lazy-loading views and the like. They could still be erroneous references to OldProject classes.

I hope that helps. I know it sounds like a lot but it should be feasible in about 5 minutes, without the optional source file renaming which could take quite a while in a large project. Again, backup!

Anyways, there are error messages in Cocoa that  are straight lies, like the one in the title. I initialized my controller like this:


newEntryController = [[NewEntryController alloc] initWithNibName:@"NewEntryController.xib" bundle:nil];

All went fine until my NavigationController wanted to show it. Then I got the error message, of course only in the debug console. The app itself simply didn’t show the view I would have expected.

After some digging through the documentation (especially the team play of  initWithNibName, loadView and viewDidLoad) I still had no clue. I looked at some sample application and then it hit me: The nib name should be just NewEntryController without the extension!

I would really appreciate a good error message when a nib file can’t be found …

How to use it

Simply type in an address (http … mandatory) or drag and drop something from your browser or text editor and click analyze.

After a while you should notice that backlinks appear and then all the anchor texts are searched that link to the page. In the third column you’ll see the percentage of the anchor text, that is how often this anchor text has been used in links to the page.

At this stage only the first 50 backlinks as returned from Yahoo are shown. Please also be aware of rate limitations.

Please note that the percentages of the anchor texts is already cumulated, that is a 50% besides “widget” means that “widget” was used as anchor text in 50% of all links.

What can you learn from this backlink analyzer?

• You can very easily see what phrases a page might rank for or is optimized for in regards to backlinks.
• You can see how a page gets its rank for a given keyword.
  E.g. I just analyzed a low profile phrase with a youtube video as #1. Looking at all the backlinks revealed that only a very tiny percentage actually had the phrase in the anchor text. So this page was mostly ranking by merits of on-page factors (the big fat h1 and the title tag) and the “general linking juice” of youtube. This made it pretty clear how it’s treated by the ranking algorithm and therefore which category it is. Which in turn proved that it’s probably a very low profile term traffic wise.

Please feel free to give feedback via the comment section below.

Compatibility

I developed and tested it on Mac OS X 10.5 (Leopard). I honestly don’t know much about compatibility with 10.4 or older versions. I didn’t use any apparent 10.5 only features such as GC or properties but I might have stumbled into some hidden traps here so please let me know.

Download
Backlink Analyzer.app.zip

But here comes the shocking truth, and it’s getting more true every day:

You can’t really manipulate SE rankings with links either!

Modern SEs use very sophisticated algorithms. They are not fooled anymore by reciprocal link dumps. They are not fooled by blog comment spam. Nearly all the black- und white-hat pure SEO techniques fail. Yes there are still some black-hat techniques that just work but they come with a cost and I won’t talk about them here and they will only work for a limited time.

But what does really matter?

Yes you’ve heard that quite a few times but I’ll say it again cause it’s more relevant than ever: High quality content people will want to link! That, and marketing your content, is all you have to do to be successful, and it’s the only thing you can do.

You can’t emulate thousands of quality backlinks from thousands of different class-C IP addresses on pages belonging to unique sites. It ain’t gonna happen.

Today, SEO is more than ever Internet Marketing in its purest form. Producing excellent content and then marketing it, to show your content to as many people as possible. And search engines will follow.

And here the circle closes and we are back to on-page factors. They are more important than ever. Because good content is reflected in content structure and good meta tags. Someone who produces good content will take care of a good title tag and well-defined structure (reflected by carefully chosen hx tags). Oh, and the author who cares about what she writes will know what to put in the meta description. And know the keywords this content is about.

# (c) 2007 uberdose.com# This program is free software; you can redistribute it and/or modify# it under the terms of the GNU General Public License as published by# the Free Software Foundation; either version 3 of the License, or# (at your option) any later version.# This program is distributed in the hope that it will be useful,# but WITHOUT ANY WARRANTY; without even the implied warranty of# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the# GNU General Public License for more details.# You should have received a copy of the GNU General Public License# along with this program.  If not, see .READLINE=5.2RUBY_BASE=1.8RUBY=1.8.6RUBY_GEMS=0.9.2SVN=1.4.3MYSQL_INSTALLATION=/usr/localFAST_MYSQL_BASE=2.7curl -O ftp://ftp.gnu.org/gnu/readline/readline-$READLINE.tar.gztar xzvf readline-$READLINE.tar.gzcd readline-$READLINE./configure –prefix=/usr/localmakesudo make installcd ..curl -O ftp://ftp.ruby-lang.org/pub/ruby/$RUBY_BASE/ruby-$RUBY.tar.gztar xzvf ruby-$RUBY.tar.gzcd ruby-$RUBY./configure –prefix=/usr/local –enable-pthread –with-readline-dir=/usr/local –enable-sharedmakesudo make installsudo make install-doccd ..curl -O http://files.rubyforge.mmmultiworks.com/rubygems/rubygems-$RUBY_GEMS.tgztar xzvf rubygems-$RUBY_GEMS.tgzcd rubygems-$RUBY_GEMSsudo /usr/local/bin/ruby setup.rbcd ..sudo gem install rails –include-dependenciessudo gem install mongrel –include-dependenciessudo gem install capistrano –include-dependenciessudo gem install termios –include-dependenciessudo gem install mysql — –with-mysql-dir=$MYSQL_INSTALLATION/mysqlsudo install_name_tool -change $MYSQL_INSTALLATION/mysql/lib/mysql/libmysqlclient.15.dylib /usr/local/mysql/lib/libmysqlclient.15.dylib /usr/local/lib/ruby/gems/1.8/gems/mysql-2.7/lib/mysql.bundle# comment in if you want svn#curl -O http://subversion.tigris.org/downloads/subversion-$SVN.tar.gz#curl -O http://subversion.tigris.org/downloads/subversion-deps-$SVN.tar.gz#tar xzvf subversion-$SVN.tar.gz#tar xzvf subversion-deps-$SVN.tar.gz#cd subversion-$SVN#./configure –prefix=/usr/local –with-openssl –with-ssl –with-zlib#make#sudo make install#cd ..

• Simply extract it to your wp-plugins folder
• Activate it
• Visit Options - Auto Social and enter your delicio.us account details
• The default submission interval is 30 minutes, you can change that in the options panel

How it worksEverytime you save a post (initial publish or a later save) it gets put into a queue. There is a cron job awakening every x minutes (see Options) that looks into this queue. If there is something in this queue this post is submitted. On successful submit the post is removed from the queue.What you needI’m using some stuff that requres PHP with curl compiled in, and I need something like PHP 4.4.2 for the authentification. You also need a host that allows SSL connections to the outside (I think many Godaddy plans don’t allow this).Downloadauto-social 0.1It took me several weeks to write this plugin. One time I had an applet to do that, then I threw this code away and asked “Why not a Wordpress plugin?”. If you know any worthwhile social bookmarking sites with an API please let me know, I will implement it.

This is the first version of a Backlink Check as applet. There are some problems with the (Yahoo) API it’s using, so results are limited to the first 100.

Update: I took it offline. It doesn’t make much sense as long Yahoo doesn’t fix their API.

Update: Apparently they aren’t even interested in improving:

In this case, your message was automatically rejected because the
moderator didn’t approve it within 14 days. We do this to provide a
high quality of service for our users.

rotfl

The audiobook is read by Gerard Doyle, who makes this excellent story even more shining. He gives his best to mimick the different tongues of all the characters. This would probably fun even with a lousy story …

So I encourage you to click through and download it! It’s unabridged of course, I wouldn’t bother you with anything else.

Important: Due to frequent updates and features translations can be out-of-date very fast. Please contact the translator about updates.

• Chinese Simplified (originally by Liang, later updated by Leo).
  Latest Update by Felixqu.
• Chinese Traditional by Neil
• Hebrew by Hannit
• Bulgarian by Iliyan Darganov
• Turkish by Baris Unver
• Norwegian Bokmål by Einar
• Ukrainian by Lyncis
• Italian by Lucacicca
• Danish by Martin
• French by arnWald
• Spanish by The-RockeR
• Polish by Kuba zyski Dirska
• German by Steini
• Hungarian by Cenzi
• Russian by Yellow Blog
• Japanese by Yoichi
• Brazilian Portuguese by Alexandre
• Dutch by Remkus

Downloads:
aerosol-0.1.zip

As of this writing the nightly build is being built and the change is mainstream. You need the nightly (1.2.0) update site: http://update.phpeclipse.net/update/nightly
Thanks to ajt and ed_mann for making this possible!

I’ve been using eclipse and phpeclipse for some time now for my PHP related developments. One of the biggest productivity killers for me was that the browser preview always tries to preview your just edited PHP file, which in a model view controller application is utter nonsense. Just because I’m just editing controller.php doesn’t mean I want to preview http://localhost/project/controller.php. Instead this usually means I’d like to view http://localhost or http://localhost/mypage. This forced me to switch to firefox after every modification and reload the page there. What I would really like to see here is the automatic reloading, in firefox or if this is not possible in the internal preview (I think I have recently read somewhere that phpeclipse doesn’t support a preview on external browsers anyway).

I already made a feature request for this. You should be able to choose your own URL since the default behavior is nonsense for MVC apps (which I would hope most people do). Somehow I had the feeling that this will take a while, if it gets done at all. If the majority of phpeclipse users is satisfied with the way it is, it will never get mainstream.

So I sat down and tried it on my own. I’m totally new to eclipse plugin development but somehow I managed to find the relevant code in phpeclipse (which btw. is a huge codebase!) and after some more thinking I figured something out that wouldn’t force me to introduce an option (which would be a pain for me since I’m really totally new to PDE). So I implemented an educated guess: If you haven’t previewed anything before, the behavior is as always. With an MVC app this first preview will be nonsense. But after a URL has been loaded in the preview, on every save in every file it will just reload that page. So you can just edit the URL in the preview to point to whatever is interesting to you at this point, edit any file in your project and have it reloaded. You can change this URL any time.

Installation

• See top of the post how to get this patch!
• Backup your ECLIPSE_HOME/plugins/net.sourceforge.phpeclipse.webbrowser_* folder.
• Download net.sourceforge.phpeclipse.webbrowser_0.0.0.jar and put it in ECLIPSE_HOME/plugins.
• Restart eclipse.
• Done!

If you are interested in the code patch (it’s only a couple of lines) leave a comment and I will send it to you or publish it here.

Have fun!

This is very useful for posts with huge numbers of comments. Only the latest comments get shown initially which makes the post load much faster.

You can see it in action here on my SEO plugin post.

Download!

• Having the latest Wordpress? Always? Up-to-date?
• Using any plugin, the latest version of it, anything you want?
• Having the permalinks *you* want, not what your hosting can offer you?

I know many of you are relying on installation scripts provided by your hosting company. It’s easy. But when a wordpress update comes along you have to wait for your hosting company. And most of them are slow adapters. What was that new vulnerability found in WP 2.1 again?Sooner or later you won’t come around hosting wordpress yourself. If you wantto maximize your blogging success there are some plugins you just have to use. And every new Wordpress version brings truck-loads of new features and eliminates pain and risk. Just imagine the tags that will come with 2.3.Do-it-yourself hosting of your blog is inexpensive, and everyone can do it. I’ve been using GoDaddy for years (Update: Not anymore, please see below). I can completely move any site from any provider to godaddy within 24h, including DNS and everything. They have the cheapest reliable hosting I’ve ever seen without compromises. Yes, you should invest a few bucks per month in a dedicated IP. Their economy plan, their cheapest hosting, has everything you’ll ever need for your wordpress blog. You can cancel anytime and switch to somewhere else or upgrade your package if your traffic requires it.There are other hosters in the world, and you’re free to choose. Ask other bloggers what they’re using.But you’re lacking the skill to setup your blog?I know just the guy for you who can setup your blog on any host. Just ask for it.Update: GoDaddy recently gave me a hard time with my dedicated server. It was offline a couple of days and nobody even cared to tell me the reason. I removed all affiliate links to GoDaddy from this post since I can’t recommend them any longer (though I never had problems on ordinary hosting plans).I’m now hosted with hostingrails.com since I’m experimenting with ruby on rails every now and then, and they have a very nice uptime guarantee which was just what I need. I might write more about it when I see fit.

Download!

I stripped everything unnecessary off, the result is very lean and very optimized for search engines.While designing I listened to Rammstein in an endless loop:

• Das Alte Leid
• Sehnsucht
• Heirate Mich
• Du Riechst So Gut

• 1.4.6.8
  vendor independent support for internationalization
  only update if your internationalization plugin doesn’t work
• 1.4.6.7
  fixed bug with whitespaces that caused strange unicode characters to appear (thanks Jeff!)
  changed wording of “additional meta tag options”
  changed POT file for new/changed translation strings
  fixed strange quotes in POT file
  Bulgarian language update
  Simplified Chinese update
• 1.4.6.6
  made title bar in edit post/page screens non-clickable so you can expand by clicking
  changed actions for both page and post edit screens b/c dbx_post_advanced disappeared, different behavior now in 2.3.x vs. 2.5.x
  The above means that you can now edit AIOSP specific things on pages again!
• 1.4.6.5
  all references to ob_list_handlers are now guarded for older PHP versions
  Dutch translation renamed so it has a chance to actually work
  translation update Chinese Traditional
  celebrating WP 2.5!
• 1.4.6.4
  Design fixes for 2.5.x
  Japanese translation update
  Portuguese Brazil (new translation)
  Dutch (new translation)
  German translation update
• 1.4.6.1
  changed download URL for one click upgrade, this should work now again
• 1.4.6
  Japanese update for 1.4.5.9
  Home page meta (copied as they are into your homepage, thanks to Liang)
• 1.4.5.9
  support for author information in post and page title macros
• 1.4.5.8
  Important: patch for preventing XSS (cross side scripting) on some pages
• 1.4.5.7
  on “synthetic” pages (like the ones generated by falbum) no keywords get generated
• 1.4.5.6
  modified home title, description and keyword generation for setups with static pages as homepage
  Hope I didn’t change anything for existing (working) static page setups! Please test if you use a static page as your homepage!
• 1.4.5.5
  support for paged tag titles with WP 2.2 and Simple Tagging 1.7
• 1.4.5.4
  support for simple tagging 1.7 on WP 2.2 for tag titles
• 1.4.5.3
  fixed a problem with polyglot on static homepages (title wasn’t translated in that case)
• 1.4.5.2
  page/post edit options now moved to the end of advanced options, look and feel like other advanced options
  internal whitespace trim for descriptions (long whitespaces get shortened)
• 1.4.5.1
  fallback to blogname if no explicit home title is given
• 1.4.5
  fixed critical problem in 1.4.4 with many PHP versions that were confused by a commented-out line
• 1.4.4
  The title is now removed from the debug comment in order to prevent malformed html with certain titles
• 1.4.3.9
  fixed bug that prevented the “disable on this post” to work properly (thanks to Aleem)
• 1.4.3.8
  support for polyglot plugin
  Chinese simplified update
• 1.4.3.7
  Polish translation update
  “disable on this post” now only shown to admins
• 1.4.3.6
  options only for admins
• 1.4.3.5
  UTW tags are now guarded by is_array()
• 1.4.3.4
  log info on ob conflicts with other plugins
• 1.4.3.3
  no paged format default
  logging for paged format
• 1.4.3.2
  keywords and tags in meta keywords are now lowercases
  fixed bug with internal keywords
  now the keyword list is unique
• 1.4.3.1
  removed comments from top of the file which broke 1.4.3
• 1.4.3
  broken!
  paged title format as option
  archives, tags and categories have paged titles now
• 1.4.2
  better support for paged home index pages
  added missing string in POT
• 1.4.1
  Polish translation update
  Dead code removal
• 1.4
  Updated Bulgarian Translation
  Fixed bug where additional meta tags where output twice
• 1.3.9
  extended debug info
• 1.3.8.9
  option for debug logging
  temp.zip is not unlinked on update (as before)
• 1.3.8.8
  w3c compatibility on meta tags and br’s
  German translation update
• 1.3.8.7
  you can now disable it on posts and pages for compatibility with other plugins
  German translation update
• 1.3.8.6
  Turkish translation update
  some initialization moved into constructor for installatione that don’t call init correctly
• 1.3.8.5
  internationalized error messages for one-click-upgrade
• 1.3.8.4
  improved error handling on upgrade
• 1.3.8.3
  plugin directory not checked for writability anymore, but there will be an error message if upgrade could not write
• 1.3.8.2
  Chinese Simplified update
  Polish update
  Compatibility with PHP < 4.3.0 (I hope)
• 1.3.8.1
  Russian translation
  Turkish translation update
  Problems with POT fixed
• 1.3.8
  More details for download errors with one-click-upgrade.
• 1.3.7.9
  Turkish and Bulgarian updates
  removed additional individual meta tags
• 1.3.7.8
  Latest extraction error on upgrade is now shown. Please upgrade manually to this version if one-click-upgrade has problems!
• 1.3.7.7
  additional meta for posts and pages (whatever you want)
  small fix in translatable string
• 1.3.7.6
  German translation update, some language domains added for translated text, some more translation strings added
• 1.3.7.5
  One-Click Upgrade!
• 1.3.7.4
  get_original_title() now tries to return wp_title() if possible
  %title% renamed to %wp_title% in description format
• 1.3.7.3
  fixed %title% macro for blogs where rewrite_title occurs after wp_head
  no keywords in 404 anymore
• 1.3.7.2
  Some additions to language switcher support (based on David’s feedback).
• 1.3.7.1
  More support for language switcher (tag and category names).
• 1.3.7
  More internationalization with language switcher, German and Bulgarian translation update.
• 1.3.6.9
  Updated Polish translation, META description for categories will now be output independently from any noindex options for categories.
• 1.3.6.7
  Hungarian translation.
• 1.3.6.6
  German translation.
• 1.3.6.5
  Turkish translation update, removal of old DB stuff, updated POT.
• 1.3.6.4
  Some layout changes, Help link removed (it’s inline), free-form meta fields for posts and pages.
• 1.3.6.3
  Bulgarian translation update.
• 1.3.6.2
  No limit on descriptions anymore, you can enter as many chars as you want. The counter simply counts them, starting at 0 (not the chars left). Changed POT file.
• 1.3.6.1
  Bulgarian translation update.
• 1.3.6
  Polish translation.
• 1.3.5.9
  Rudimentary support for language switcher to enable testing, without using “the_title”.
• 1.3.5.8
  Updated Turkish translation, new Spanish translation, max-width of help-texts is now 500px, pot file is included in distribution.
• 1.3.5.7
  Filter “the_title” is now applied to the title just before it is replaced.
• 1.3.5.6
  Chinese Simplified update.
• 1.3.5.5
  Fixed missing text-domain for help strings.
• 1.3.5.4
  Tweaked default option values so new users with WP 2.3 don’t have to do anything and it’s fairly optimized out-of-the-box.
• 1.3.5.3
  Support for 404 titles. Totally remade options panel with easily accessible and translatable help.
• 1.3.5.2
  Updated Chinese simplified and turkish translations.
• 1.3.5.1
  Support for description formats. Your meta description can now contain pre-defined content around your description, like a sentence or your blog title etc.
  Yes, I know I skipped 1.3.5 …
• 1.3.4
  Updated Chinese Traditional translation.
• 1.3.3
  Changed order of keywords from different sources (tags, categories etc.) so it makes more sense.
• 1.3.2
  Updated Chinese Simplified translation.
• 1.3.1
  Added missing textdomain for “Options updated” message.
• 1.3
  Ok, I screwed up the versioning completely 1.3 is the newest, comes after 1.2.9.9 and has all fixes from the erroneous 1.2.3 and 1.2.3.1.
• 1.2.3.1
  Compatibility with WPG2’s gallery sitemaps. This time it works
• 1.2.3
  Compatibility with WPG2’s gallery sitemaps. This will break themes without titles, but so far I’ve never encountered one.
• 1.2.9.9
  160 char limit in descriptions is now visibly enforced.
• 1.2.9.8
  Removed .po files from distribution.
• 1.2.9.7
  Added missing textdomain for translated string.
• 1.2.9.6
  French translation.
• 1.2.9.5
  Danish translation.
• 1.2.9.4
  Italian translation.
• 1.2.9.3
  Ukrainian translation.
• 1.2.9.2
  %category_title% as alias for %category% in post titles, all titles are now stripped of tags.
• 1.2.9.1
  Trailing comma in keywords removed (was caused by the recent addition of autometa support).
• 1.2.9
  Tags in meta descriptions are now stripped. This tackles the situation where paragraphs appear in category descriptions.
• 1.2.8.9
  Norwegian Bokmål translation.
• 1.2.8.8
  Traditional Chinese translation.
• 1.2.8.7
  Updated Chinese Simplified translation.
• 1.2.8.6
  Removed bogus upgrade-functions.php that was in db_install (for a possible category title feature) and made the Wordpress Upgrade Preflight plugin complain about it.
• 1.2.8.5
  Support for AutoMeta. Keywords generated by it will be used.
• 1.2.8.4
  Inner optimizations for translations.
• 1.2.8.3
  Title rewriting fix for PHP installs that use lowercase classnames in ob_list_handlers().
• 1.2.8.2
  Turkish translation (thanks to Baris Unver)
• 1.2.8.1
  More debug info when there is obviously another output handler.
• 1.2.8
  Fix for the Bulgarian translation.
• 1.2.7.9
  Bulgarian translation (thanks to Iliyan Darganov)
• 1.2.7.8
  Fixed keywords bug in WP 2.3 which used ALL tags from your installation as keywords
• 1.2.7.7
  Removed extraneous debug statement
• 1.2.7.6
  get_meta_keywords() returns all meta keywords entered through SEO pack
• 1.2.7.5
  %blog_description% now available in all title formats
• 1.2.7.4
  Quotes in keywords are now removed.
• 1.2.7.3
  First version for Wordpress 1.5 compatibility.
• 1.2.7.2
  %category_description% in category title formats
• 1.2.7.1
  %category% in post title formats
• 1.2.7
  Removed the debug info complete with the option. All necessary info is now inserted into the version comment without any overhead. Also other plugins with ob_start() get detected.
• 1.2.6.9
  Even more debug info for title rewriting. Don’t forget to disable it after you have sent me the report!
• 1.2.6.8
  Debug option for some remote debugging on title rewrite.
• 1.2.6.7
  The option “number of words in auto-generated descriptions” is now completely gone, instead there’s an internal default of 160 chars (!) which reflects the current way most SEs handle text snippets (and will of course be updated when this changes). On description input boxes this is now reflected with a message.
  TODO: Some JavaScript that counts the number of chars entered.
• 1.2.6.6
  Backwards-Compatibility with SEO Title Tag. If you didn’t set an extra title with All in One SEO it looks for the SEO Title Tag title and uses it if found.
  Support for search title formats. Tweak the titles of your search pages.
• 1.2.6.5
  (internal) This version never got published, search title formats were added and published in 1.2.6.6.
• 1.2.6.4
  Support for tag title formats. Tweak the titles of your tag pages.
• 1.2.6.3
  Enhanced support for static page as front page. Don’t upgrade unless you’re using this and found it counter-intuitive the way All in One SEO handled it.
• 1.2.6.2
  Support for archive title formats (you can now tweak the titles of your archive pages).
• 1.2.6.1
  Switched from stripos to strpos since the former is only available in PHP 5.
• 1.2.6
  Wordpress 2.3 ready! On WP > 2.3 Tags are used as keywords.
• 1.2.5.9
  Another refactoring of the title rewrite code to make it K2 Rolling Archive compatible. On themes that don’t have any title element one should get inserted.
• 1.2.5.8
  Added htmlspecialchars() to post and page edit forms. This means that input is now much more resilient to quotes and other chars.
• 1.2.5.7
  Categories now have their own title format and get capitalized.
• 1.2.5.6
  Problem fixed with ImageManager 2.4.1
• 1.2.5.5
  If you’re using UTW for tagging, tag pages now get the tag name as title automatically. Some database code for category meta tags is contained but doesn’t get executed until all is finished.
• 1.2.5.4
  (internal)
  Added some infrastructure for category meta tags.
• 1.2.5.3
  Home page title now rewritten again (if set in options).
• 1.2.5.2
  Upcoming changes for the feature of having meta tags for categories. Everything is commented out, so there should be no apparent difference to 1.2.5.1. Had to commit before fixing something else.
• 1.2.5.1
  There is no a tab index (taborder) in the page edit screen. Once you’re at the SEO pack title, you can tab through the other input fields as well.
• 1.2.5
  You can now change the page title format, separate from the post title format.
• 1.2.4
  Fixed bug where page titles got ignored when they contained single quotes.
• 1.2.3.9
  Added a guard in the code in case wp_query doesn’t exist. No remedy for the problem with some 2.0.5 installations, but at least pages get produced.
• 1.2.3.8
  Fixed the problem with title tags spread on several lines (yes, some themes do this).
• 1.2.3.7
  More consistent option “rewrite titles”. If switched off, no title gets rewritten if you specified an individual title for a post or page. If switched on, even individually set titles adhere to the corresponding title format. This is different from the behavior before, where an individual post title was not processed with the title format, e.g. if you got your blog title appended in your title format, this was not done for those posts with individual titles.
• 1.2.3.6
  Compatibility with wp-cache (again)
• 1.2.3.5
  (Hopefully) fixed the bug where all posts get the same title.
• 1.2.3.4
  Due to a eclipse bug, this contains the changes from 1.2.3.4 that weren’t committed in 1.2.3.3.
• 1.2.3.3
  Fixed typo in is_feed, otherwise the bug in 1.2.3.2 would not have been remedied.
• 1.2.3.2
  Fixed: Bug with titles on category feeds.
• 1.2.3.1
  Fixed: Pages were not showing set meta title, instead the page title always was used as meta title.
• 1.2.3
  Complete rewrite of rewrite_title().
  Removed the option for using category descriptions as title, this is implicit at the moment.
  This rewrite was necessary to make room for the expansion I’m planning where you can edit templates for each type of title.
• 1.2.2
  (internal)
  Upgraded to GPL v3
• 1.2.1.4
  Important Update for UTW users
  typo: both aiosp_tags_noindex and aiosp_tag_noindex existed
• 1.2.1.3
  Version and a link to this release history now appears in the Options for All in One SEO pack
• 1.2.1.2
  (internal)
  changed aiosp_title_format into aiosp_post_title_format in preparation for a complete rewrite of rewrite_title
• 1.2.1.1
  Fixed bug in 1.2.1 which broke your site when UTW wasn’t installed
• 1.2.1
  noindex for tag pages (with Ultimate Tag Warrior)
• 1.1
  Compatibility with Anarchy Media Player
• 1.0