293649
Here's another thing that occurred to me re: passing the objects to themes. Perhaps there's already such a document (I apologize if I missed it somewhere), but it might be nice to have theme guidelines that require you to test for the existence of a property before using it.
Here's an example problem: Theme 1 uses $story->title, $story->morelink, etc., which are all standard. Theme 2 uses the field I added to the table as $story->storyurl. At this point, only those people who had my modified code could use my theme. If they used my theme with their unhacked Xoops, my theme would barf when it tries to access $story->storyurl and couldn't find it.
But if I wrote the theme with that in mind (and according to the suggested guidelines), the code would test for the existence of $story->storyurl before trying to use it. That would (or should) make my theme compatible with unhacked versions of Xoops.
Obviously, my example is about hacked versions, but this same principle would apply to prior and future official versions.