Malphas wrote:I think a lot of [what I would consider to be anyway] faults with phpBB could be avoided by having some officialy supported MODS. I think PunBB is going this route. One of the biggest problems with MODS is not just having to manually install them, but usually being unable to test them out prior to installation, and being unsure of the quality. Taking the most common installed MODs and subjecting them to some sort of verification and QA procedure would alleviate this.
As Paul pointed out, and I’ll reiterate, MODs released in the MOD Database go through a line-by-line validation process before being released, call it verification and QA procedure, that’s basically what it is.
Malphas wrote:It's personal opinion ultimately, but I do think there phpBB 3.0 is still missing a few quite fundamental features whilst including ones which are almost frivolous.
Okay, step back for a moment and take a look at this quote... it’s what was discussed just two posts before. What you consider to be fundamental features others might consider to be frivolous features, and what you consider to be frivolous features others might consider to be fundamental features.
I know you said personal opinion, but it sounds really silly.
... think about this: 5 years ago, most of these features were not considered fundamental, but now, 5 years later, all the sudden they are fundamental. Has the internet really changed that much?
Malphas wrote:But are they checked to be compatible with each other, and other styles, etc.? Also, I recall installing a few MODs for 2.0 from the database about six months ago which causes my forum to fail WC3 verification.
It’s impossible to test for every single circumstance. That said, all MODs are tested on the default theme (prosilver) and most MODs include both prosilver and subSilver2 styles.
It would be IMPOSSIBLE
to test MODs on every custom style and every other custom MOD. If we even tried, not a single MOD would be approved to the MOD Database after about the first 25-50 MODs were approved.
To consider this is just short-sighted. -- Hundreds of MODs are submitted to the MOD Database, only a few make it through at a time because of the approval process they go through.
The standards are much higher and a lot different with 3.0 as well... in 3.0, the way the core was built means that more MODs can take advantage of the functions that have been put in place so that they don’t conflict with other MODs. We also work with MOD Authors on better coding practices that decrease the chance that conflicts will happen. But we would be utterly stupid to think we would be able to consider every situation.
All MODs go through an XHTML validation as well, for prosilver, they must be XHTML 1.0 strict valid and for subsilver2 they must be XHTML 1.0 Transitional.
Malphas wrote:Yup, that's why I specifically mentioned it being a core set of the most used MODs. Simply checking an individual MOD is bug free when installed in a clean board is next to useless if you're using a different style and installing multiple MODs really. I mean, it's still a good thing of course, but that's not what I meant by my previous post suggesting the idea of an "officially supported" set of common modifications.
And then every person will want their own MOD included in the package, this is not any better of a solution. We already addressed earlier why even *popular* MODs are best left OUT of the core. -- see the last few pages of this topic to see extended explanations why, so I don’t have to repeat myself.
There are a set of "officially supported" MODs, and those are the MODs released in the MOD Database.