Nice feedback. We’ll put this into our development list. We really need to get this puppy on to GitHub to track these issues. Thanks for your rating!
maybe a .httpacess solution would be better…. ie, rewriting the .httpacess instead of managing all via wp.
what’s .httpaccess? Do you mean .htacess file in apache? What about the folks using ngnix or other servers setups?
yes I meant it…. 🙂 well I did’t thought about it…. you could check what kinda of httpd deamon they are using and use 2 different way 😉
is just an idea… the problem is that we are used to use a plugin for about everything.. 95% of times it run fast but sometimes easier solutions could be more performing.
Hmm interesting. I totally get what you’re saying. This plugin is more for the users who don’t have the expertise to write complex redirects. We still need to ensure it doesn’t butt heads with the bugs you pointed out though..
I think the most important thing is the load. The 1st one could be easly turned around deleting the tag, the 3rd rebuilding the permalink structure (once you know it)… the real problem is the 2nd one…. that, for us, makes the plugin unusefull. About my idea you could think to do an “do you want to try to do it via .htacess?” button. For exemple the fastest cache plugin….do it….rewrite totally the file…adding what needed and deleting it once the plugin is disabled.
btw: I’ve found on some blogs the plugin was disabled by default…yesterday… seem like wordpress was not able to do all and desided to disable it. I’m sure it was enabled sicne I’ve added it to all 100 blogs.
Hey sorry I haven’t had the time yet to give this a closer look and probably won’t for a few more weeks (getting married). Are you a developer? If you interested in contributing we’d be more than happy to accept code contributions and improvements from the community.
