We didn't really use the file scheduling feature so didn't work with
it much, but I just tried it on our site which uses this module and
it worked (or at least produced no errors, since I don't have a
"front page" for it to actually show up on).
This site is based on OpenACS 3.2.2, and is running AOLserver
3.1+ad9, using nsd8x. The major difference is the OpenACS
version and I expect that's where the trouble lies, though that's
only a guess.
I agree that passing that much content in the URL is A Bad
Thing, but our goal with the port was to make only porting-related
changes.
I'll see if Paul has time to install this with OpenACS 3.2.4 and
post here if he has to make any changes to get it to work.
