Hot answers tagged

6

I can think of cases where both database and jdatabase would be appropriate. If a question is about a more general database question (maybe "how to join content data with data from my custom table"), that should be tagged just database. If you are specifically asking about working with the JDatabase or JDatabaseQuery classes, then tagging those ...


5

I will try to form an answer that we could use in the help page... Suggested version tags cms-1.0 cms-1.5 cms-1.6 cms-1.7 cms-2.5 cms-3.x cms-3.1 cms-3.2 cms-3.3 cms-3.4 cms-3.5 fw-1.0 For mysql and compatible sql servers like mariaDB or Percona Server - mysql-5.0 - mysql-5.1 - ... postgres-9.0 postgres-9.1 ... mssql- ... For Apache - apache-2.2 - ...


4

We shouldn't forget that tags can have synonyms too. While not directly applicable to the orginal database vs. jdatabase example, it might be appropriate for database to be a synonym for mysql or postgres.


3

IMO the number of tags shouldn't be too big to start with. We won't reach StackOverflow proportions any time soon and having many closely related but distinct tags makes it much harder to follow the questions I care about. Given the example in the question, I think database should be used for any question related to accessing databases trough Joomla. Tags ...


3

Actually I don't think we will have questions regarding JEvent anytime soon. I have renamed the tag jevent => jevents and added a proper description so that we know what is it for.


2

In the blog post The 7 Essential Meta Questions of Every Beta the following describe the situation the best. Proper tagging is very much a lead-by-example activity. The sooner you get the “community standards” for tagging ironed out, the less chance you’ll have to face the drudgery of cleaning them up later. So tag your questions as best as you can. ...


2

In my opinion, there are three types of version changes for Joomla: Joomla 1.5 to 2.5 or 3 This could be called a migration, because a new installation of Joomla is required, and all content, users, extensions etc. has to be migrated or moved to the new site. Joomla 2.5 to 3 Going from one major version to another (i.e. 2.5 to 3.x) is usually called an ...


2

Bit of a tricky one this is. Too many words to describe 2 different thing. Personally I think we should stick with one of the following options: To make life extremely simply, keep 1 tag (upgrade) to define everything. This can be used for question regarding upgrading in general, for example: Joomla 1.5 to 2.5 or 3.x Joomla 3.2 to 3.3.x For the second ...


1

I don't think I have ever seen any questions for this. If people want to add a specific tag to a question, they can simply do so by typing it manually in the tag section when creating a new question. Only those extensions that are very popular such as K2 and Community Builder should have their own dedicate tags with descriptions. If we start creating them ...


1

I'm a little cautious of these types of questions. Extensions recommendations can be a nice, simple and quick question to answer, however it's considered "Primarily Opinion based" which as you know is one of the reasons when flagging to close a question. A lot of the time people may answer the question with simple a mega list of extensions to choose from ...


1

Off-topic, but the tags mentioned are already created on meta. You should be able to add / propose a new tag if you feel like it (not sure about permissions), so I don't think it's enforced to use one of the tags, you just need to use one, whatever. Regarding the website, I would prefer to have tags instead of mentions of the Joomla version in the post. ...


1

The problem with tagging a class name is trying to follow all those tags. "Database" is ok because that should be about general database problems. However, I'd rather see "JDatabase" or "JInput" tagged as "joomla-platform" and things like the DI package tagged as "joomla-framework" rather than the package or class name (or at the very least, include them as ...


1

It should really be whatever makes it easiest to search. I think it can be somewhat organic at first, and then add suggested tags. Not 100% on that though.


Only top voted, non community-wiki answers of a minimum length are eligible