Prefixes for vB Programming Articles

[RS_Jelle]

In the past there were seperate programming articles forums for each vB version. Now it's a bit a mess, it's very hard to see if it's a tutorial for vB 3.0, 3.5, 3.6, ...

Maybe you can add the prefix system to the vB Programming Articles?

[Princeton]

I don't believe we will ever do that (most articles are general and tend to "fit" across the board) ... The best option would be for the article to have a descriptive title.

I do agree that it is a bit difficult especially when article submissions are not "moderated".

FYI: In the past, there haven't been any "moderation" when submitting an article; but, this will change in the near future.

[Gio~Logist]

I honestly think he has a point. Some articles will not work for certain versions, this will prevent the users from having to read and follow through a whole article before realizing it's not for their vbulletin. I don't see why this can't be done.

[Paul M]

I honestly think he has a point. Some articles will not work for certain versions, this will prevent the users from having to read and follow through a whole article before realizing it's not for their vbulletin. I don't see why this can't be done.Joe already explained why. If an article happens to be for a specific version then that can simply be put in the title - e.g. "Creating threads in vb 3.5".

[Gio~Logist]

Joe already explained why. If an article happens to be for a specific version then that can simply be put in the title - e.g. "Creating threads in vb 3.5".

Right, but then we run into an organization problem.

1) They may forget
2) Longer title
3) Having it as a prefix is more organized, and can be filtered and used better.

Anyone can include any prefix in a thread, but if everyone thought like that then the prefix hack would never have been made :p

[Marco van Herwaarden]

Actually i think it is a good idea to make it clear (either by prefixing, or by seperate forums) to seperate articles discussing versions that use different underlying technical structure.

So no split between 3.5 & 3.6, but split 2.x, 3.0 and 3.5/3.6.

The way articles are submitted will also change in the near future, like already mentioned, so we might implement a solution for the different versions also.