Still using $_POST for search?

You could release test 2 this month as promised and leave the final fixes for test 3. That way we'd be looking for bugs instead of you and you'd actually have more time for coding. And using bug reports you'd know exactly what to fix.

Still using $_POST for search?

Well, I mean no offense but test 1 is not exactly production ready, so I for one haven't begun working on it yet

That's the reason why I didn't want to rush out another test release without doing some testing and cleaning ups.

But considering that some time ago the roadmap was

At this point I didn't know how big this release was going to be. Contentteller 2.0 is a huge code base compared to the old 1.x series.

Still using $_POST for search?

Well, I mean no offense but test 1 is not exactly production ready, so I for one haven't begun working on it yet. But considering that some time ago the roadmap was

2.0 PHASE 1 (January 2006)
This release is an internal technical beta release to test the new code base in a real world environment.

2.0 PHASE 2 (February/March 2006)
This second beta will extend the beta test to external testers. This release is 90% code complete.

2.0 PHASE 3 (TBA)
The third and final beta is basically a code complete release candidate. The only difference between the final release and this beta are some bug fixes.

and now it's september 2007...

Still using $_POST for search?

The main problem is that there are many smaller template/database alterations in each build. It makes updates from one build to another more difficult.

I possibly can release a preview version of Test 2, but it would have at least three limitations:

1) More bugs and other issues after it is untested
2) No upgrade path form Test 1. You need to do a fresh install.
3) No official upgrade path to Test 2. An upgrade might work but I can’t guarantee it.

Still using $_POST for search?

Well, it's not really a showstopper. Just please release Test 2 already, we've been waiting for a long time and it's OK if it's not perfect. Little things like this can be fixed for the third release.

Still using $_POST for search?

I will look into it

Still using $_POST for search?

Hmm. But in this case there is no way to generate plugins for browsers.

For instance

 http://www.microsoft.com/windows/ie/searchguide/en-en/default.mspx

IE7 doesn't support POST for search providers. And besides from what I see, your search seems to generate a temporary randomly named file or something?
Searching in my test installation for "moore" gave three different URLs

http://www.file-portal.net/ess20/contentteller.php?ct=news&action=results&page=moore_b9ba.html
(the last part seems to change randomly every time). In this case there's no way to make a stable url for linking to a search, is there?

Still using $_POST for search?

Actually, it uses both. $_POST for the initial search query and $_GET for the searches itself.