|
Comus has an extremely flexible backend that can be configured to generate pages anyway you want including linking directly to the pages, but it's really overkill for this app. Basically the only thing that you would need to do in order to make that happen would be to modify the templates so that the link generation part of the template (it's only about one line in most instances) points directly to the link without going through Comus. However, everyone is correct in that you will lose all the protective features that Comus brings to the party when you do that.
Realistically, your best bet would be to make a few homebrew scripts (they can be written in php if you want to go that route) that use a db to store the links (mysql or postgres) and that when executed will dump out the results in whatever style template that you conjured up in your script. That's probably something like really only between 1 and 3 files. Not a lot of pain if you're looking for something that's going to be easy to maintain.
The other added benefits of using a db to store the links is that you can write a script to check for dead links as well as do nightly builds via a cron job.
Now, if you wanted to add some sort of cheat protection to this scheme though it's going to be a bastard. You're probably looking at cobbling together some sort of home written program that sits and watches transparently until someone starts screwing with something and then it just appears to ruin their day (one that might simply just watches the access_log file and update the .htaccess file based on a predefined rule set). Possible, but that type of coding is essentially re-inventing the wheel in terms of what Comus and TTT already do not to mention somewhat painful (proxy checking, etc.).
|