What, exactly, is getting included where?[/b]
The current system is actually quite a kludge. Prior to the current site, I created a cryptogram program (C++), and posting them occasionally on the site as the mood struck me. People would then solve them (and other riddles) for points. When the CMS my site uses moved to the next version my riddle page broke. I also stopped adding cryptograms as often as I'd have liked, because of other things I needed to do. The fix to both of these was to build a page that could be droped into any CMS that was updated in a regular basis. Already having a working cryptogram program of my own making, I wrote a simple sctipt that runs on a con job and dumps HTML/PHP into a file which includes the text files with the encrypted and decrypted versions of the quotes. This way I can page break when I feel a page is getting too long by simply moving the current included file to another name, and adding the new link (I suppose I could also cron this to happen at regular intervals).
If it was my site, I'd write a php program which you could include as a URL like this: crypto.php?q=Original+plain+text that would generate the cryptogram on the fly, and output the HTML to present it and the answer in whatever mode you think appropriate at the time. That would take out a lot of work!
I thought about having it done all done in PHP, but I'd have to recreate the cryptogram program in PHP and then I'd be temped to tie it into the CMS, which means that it would break if I changed CMS or upgraded.
Having looked, now, at the site in question, I don't think my solution is going to work on your current page - it'd be miles long for non JS-users. Mind you, your policy of showing all current cryptograms on one page is already making a pretty long page after less than months - maybe you should consider presenting one cryptogram per page with a richer (though Javascript-dependent) interface?
I don't want to force JS down the throughts of my users, espceially some of the old unix geezers I get. I do agree the page is getting long, but one per page does seem like an awful waste of space. I'm consider croning the splitting of pages.
[plug=shameless]
[/plug]