Hot answers tagged

18

As we need a canonical answer to this question I'm going to provide my own matching the comments under the question and ready to receive votes. WP-CLI is on topic. It has its own landing page on wordpress.org providing a changelog and helpful link on where to get support and how to contribute to it. This landing page states: WP-CLI is the official ...


7

Questions involving a specific plugin are not necessarily off-topic. It always depends on the problem. Example: a plugin registers a post type, and the asker needs an extra column to the list table: perfectly on topic, because adding columns to any post type table is a generic problem. The solution can be applied to other code too. Now I think the tag ...


7

It irks me now and then, but it there is 25 characters limit for tag name. And plugin-acf seems a little too abbreviated. Any alternate suggestions?


6

I'll take <query-posts> and <pagination> (and any others related to custom query loops/pagination).


5

I have three objections: We do have already too many tags named after functions. Each time WordPress renames or deprecates a function, we get into trouble. If we start to name tags after function arguments now, we create a very bad precedent. More trouble will follow. The tag name is too vague. Like order, the context is missing. Priority of what? It could ...


5

I don't see any harm in doing so. Hopefully users will think twice when adding the tag. +1


5

A tag is serving two purposes: finding content and hiding content. And the latter is what prevents us from deleting or merging tags. Many users have blocked for example the tag woocommerce, because they are annoyed by those questions. If we remove the tag, their question list will suddenly get polluted with that again. Also note that it's not the tag what ...


4

I agree with the action being taken; however, I do not believe that the meta discussion constituted a mandate for that action. 99% of the discussion (and answer up-votes) related to the question of scope. While one question (with 2 net upvotes, compared to 10, 9, 8, and 3 net upvotes for the other more highly-voted questions) indicated support for the "...


4

I spend bugger-all time on this site, and when I do, I go looking for questions that the experts can't/won't answer because they're outside their specific domains of expertise -- such as Gravity Forms, WooCommerce, and WP e-Commerce -- or because they have a bias against them due to poor treatment from the vendors of those plugins. Right now, I can't easily ...


4

I'd suggest it should be very dependent on the nature of the tag and of the questions within. Simply throwing together all the plugin-related tags are going to make questions less browseable. As mentioned by @toscho, plugin-related questions will still be asked. Why not keep the system we already have to keep questions organized (more or less)? If there are ...


4

Tag is unnecessary I'm also voting to remove the best-practices tag as all answers should adhere to the WordPress Coding Standards and/or best practices in general. It's silly that some people still give bad advice and/or bad answers (with bad practices) like for example this debate: How to add crossorigin and integrity to wp_register_style? (Font Awesome ...


4

I'm new to Wordpress, and therefore new to this site, but there are plenty of other SE sites where a question asking for the best way to do something is closed as Primarily Opinion Based. While "Best practice" isn't exactly the same as "The best way", it is close enough. The best practice can depend on the goal. So, yes, drop the tag.


4

The tag exists for two reasons: Some wordpress.com questions are on-topic. Migration from there to a self-hosted installation is a common example. Some users have put that tag on their ignore list, and we don't want to break that. This is similar to other popular off-topic tags, like woocommerce. Moderators cannot delete a tag, but they can merge it into ...


3

Less is better. I like your first idea with just two tags. Most are not sure what tag to use, no matter what we try. Having less tags makes that easier. I can do that, but it'll be quite some work that needs to be handled very carefully. And more important, it needs the support of the active community members, so please raise your concerns now, or show ...


3

Upon further reflection, I think this tag synonym should be reverted, for two reasons: 1) It prevents the use of the WPSE ignore feature, since ignoring the woocommerce tag forces ignoring of the synonym tag, plugins 2) It is inconsistent. Other Plugins retain their tags, e.g.: plugin-gravity-forms, advanced-custom-fields, and similarly, genesis-theme-...


3

I think tags should be as specific as possible and as needed. custom-* is pointless on our site, because everything we do here is talking about "custom code", i.e. how to use the core for customization. The existing custom-* tags are errors from the past. There is no need to repeat them just because we have done this once. The prefix doesn't add any useful ...


3

TL;DR You're right. This tag should be deleted. Because it's off-topic now. See below a detailed explanation why. It's all about asking how, not what to use or to install You want to use a specific plugin so that you could add some functionality to your WordPress website, you know what you want to accomplish, you only need to formulate your question to ...


3

No, we shouldn't. When people come here with a question about a certain plugin, they already know what the plugin does. So, the excerpt really doesn't need to describe it. I'd say the most important role for the excerpt would be to manage user expectations. Given how often we are flagging things as off topic, I'd say the excerpt should make clear what the ...


3

I haven't been around here as long as others - which is to say perhaps take my opinion on this with a grain of salt - but I've noticed I've been flagging a lot of posts about plugins to say they're off-topic. This is particularly the case with WooCommerce, where often the question is clearly off-topic (asking about WooCommerce specific hooks, or how to add ...


3

I take wordpress.com and wordpress.org The tag wikis are still not good enough.


3

I like the idea but I don't know how you'd implement it effectively. There would need to be a way-- perhaps there already is-- to mark the unwanted tags in order to display them with some identifying formatting, and even then, unless there was a working blacklist user could, and I expect would, continue to use the tags. Something even more unfriendly like a ...


3

The problem here is that any user with a particular level of reputation can recreate the tags, so deleting them does not work. We've tried in the past, in particular with the WooCommerce tag, and it gets recreated. We've also tried updating the description of tags to state that the subject is offtopic. It's also possible to tag something but still be on ...


2

I'll handle custom-post-types.


2

I don’t know when it has been implemented, but it happened. Each tag has a link named top users, and here you get a nice list. Example from our over most used tag plugins:


2

There are a ton of tags that are off-topic tags most of which are plugin specific: almost anything [plugin-*] and woocommerce etc. Since Stack Exchange is a community based platform the community decides what tags may be relevant to their question - and any user greater than 300 rep can just create any tag they see fit. This doesn't mean questions ...


2

For me, out of the list of terms given, the ones that should not be there are translation, language, l10n, po and mo. translation is the process of producing text in different language which wordpress has nothing to do with, the rest are just not meaningful. textdomain is a technical term used as part of localization so it should stay, localization ...


2

I like the idea of two tags only, but I would opt for textdomain in stead of translation. The reason for this is that more serious developers, whom I see as our core users, will use textdomain to describe the development issue they are addressing. translation is a colloquial synonym, but not the correct WP term.


2

One week later, I have changed the tag info and started retagging. I will try not to pollute the front page with my edits, so this will take some time until it's finished.


2

I'm cool with that. But as always setting the rule will be easier than policing it.


1

Yes, I think we should. Users come here because they have a specific Wordpress issue (ok, many come because they are clueless, let's forget about them for a moment). They know WP before they know us. So, they think in WP terms, like it or not. To stay as close as possible to user experience, I feel we should stick with WP naming conventions. Also, using WP ...


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