4

Normally, when a question is tagged it means the question is for Drupal 7, and not Drupal 6; nothing is said about the validity of the answers for Drupal 8. So, a question about DBTNG is valid for Drupal 7, and Drupal 8 (and possibly for Drupal 9), but a question about the Dashboard module introduced in Drupal 7 doesn't apply for Drupal 8, as that module has been removed in Drupal 8.

The only way I can think to disambiguate between questions that are only valid for a Drupal version, and questions that are valid since a Drupal version is leaving a comment about that. I don't mean we should hunt for any of those questions, and add a comment when the question is not anymore valid for any version past the one for which the question has been tagged, though.

Using multiple version tags is probably more difficult; it would mean to add a tag for every new Drupal version, and a question that is valid since Drupal 6 would get tagged as , , , , , and so on. A question that is valid for at least 5 Drupal versions would easily reach the limit for the number of tags allowed for a question, considering that normally there is at least another tag that is not the version tag.

Is there any other way to disambiguate such questions that we could adopt, in the case it is really necessary doing so? I would think it is helpful for who reads any of the questions asked on Drupal Answers.

1

I do not think this is really a problem.

Relatively few questions are version specific. If there is not room for all applicable version tags, I see little harm in omitting the oldest version tags, as these will point to obsolete version that few people use. Having the question tagged with the most recent versions is what will help most people searching for an answer by tag. If necessary, additional details about versions can be in spelled out in the text of answers: "This works in Drupal 7 and Drupal 6, but not in Drupal 5".

But the majority of questions seems to be rather broad, being about the general Drupal architecture or the community. Hence, version specific questions can be tagged with the most recent version that is applicable, while the majority should be without a version tag. Tagging with one or more versions should only be done if the answer really is version specific (and in those case, I suspect that only a single version tag will be applicable).

Also see these discussions:

(However, if somebody is able to demonstrate that there is a real need to tag a question with multiple version numbers, I think the best solution is to expand the number of allowed tags to six or seven (whatever is necessary), so that people will be able to tag questions , , , , , , , etc. I think that alternatives to this, such as creating new tags (e.g. ) to indicate multiple versions will be search-unfriendly.)

  • It is not yet a problem because, so far, we are getting questions about Drupal 6, and Drupal 7. There are just 14 questions tagged 5; even if there are questions about Drupal 5 that are not tagged, those are still a minority. The problem is, eventually, (if effectively there is a problem) when Drupal 8 will have its first public version, and it will be used from enough developers to cause them to ask questions. The number of tags is hard-coded; I am not sure TPTB will even increase the number of tags available for a single site. – kiamlaluno Dec 31 '12 at 15:38
  • An alternative would be to create a "version number" field that takes values that correspond to major Drupal releases. Not sure if this is feasible, but it sounds like if increasing the number of tags is being looked at as a solution, it should be mentioned. – beth Jan 4 '13 at 21:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .