When static caching is switched off, ezpublish's url system automatically forwards old urls onto their new equivalent as much as possible. For example if I create an article called /oldname and later rename that to /newname, pointing my browser to example.com/oldname redirects me to example.com/newname

This mechanism is broken for statically cached sites.

<b>Steps to reproduce:</b>

1. Setup correctly functioning static cached site
2. publish an article
3. edit that article to give it a different name, and republish

<b>Result:</b>

The old cache file is cleared correctly, but then two copies of the new cache file are generated in the static cache - under staticcachedir/oldname/index.html and staticcachedir/newname/index.html - the result is that pointing my browser to http://example.com/oldname I see the correctly updated content, but I am at the wrong URI.

<b>Expected result:</b>

Nothing should be generated under staticcachedir/oldname, this should be left empty in the static cache (or the directory removed completely) so that the rewrite rules fall through to index.php and the user is then redirected to http://example.com/newname and served staticcachedir/newname/index.html correctly.