HuwR,

I would have to agree with you. Most of the MODs that I've installed, have not worked by just following the instructions. I do thank the people that make the MODs, because Lord knows I do not have that ability. But, we do need better instructions on installing them.<

Have to say, personally, apart from a minor few mods, the only problems I've ever had installing mods has been due to more than one mod requiring changes to the same section of code and, now that I'm familiar with the base code, it isn't really an issue any more. And the small number of mods that I have had problems following the instructions for have largely been due to the fact that the mod author's first language wasn't English.
One of the biggest gripes I have when it comes to mod authoring is when a mod adds a new function that does exactly the same thing as, or could easily be substituted with, an existing function in the base code or when the authors don't adhere to the overall design of Snitz and hardcode in their own styles, etc..
Having released a few, small mods myself and customised 2 Snitz forums to hell, I do appreciate the work that goes into these things and do not wish to appear ungrateful but, as Erick points out, some sort of standardisation would go a long way towards helping new mod authors and installers get started with Snitz. How about (and I think this may have been suggested before, a long time ago) a mod review panel, a team of members to review every mod posted in the Mod W/Code and write back to the author with recommendations/suggestions for changes to the mod to make it more compatible with Snitz or changes to the readme to make it easier to follow, etc.?
<

I think another problem is a majority of MOD writers have moved on from Snitz and they're not around to update or help out here with any problems.

Maybe it's time to consider adding mods to the base code to avoid these situations?

v5? <

Originally posted by sr_erick
Here's my rant..
Maybe it's time to consider adding mods to the base code to avoid these situations? People can only do so much when there is no standard way of doing things. I have yet to see a write up on the proper procedures for creating, submitting, and supporting a mod. There has to be some standardization for things to work.
Rant over...

There is a perfectly standard way of doing stuff, what I am talking about is sloppy code,missing instructions, database incompatability etc,not the fact that I may have to put the code on a different line, I wouldn't have wanted any of these mods in my own forums so wouldn't even consider them for addition to a base snitz<

I have to agree with the jist of this post. I tried to make a forum from scratch and i end up fixxing and tinkering more than setting up the form. I have not done this as much asping as some of you, in fact i have only ever made one mod and that was just at the request of a friend of mine and he and i are the only ones using it so i didn't really have to think about the read-me file that much. The more i learn about asp code, the more i understand it , so there are a few mods that i can look and see the problem and go in a tinker it out. But most of the time i end up emailing Huw, or someone with similar expeirience, for some help. I may be speaking out of turn here, but maybe it is time for someone with good asp knowledge to decifer some of these more popularly installed mods and go over it with the authors and re-release them with all the bugs fixed.
Thats just my two cents anyway. <