I tried editing a question with that tag, and I got an error about that tag not being allowed. I will check what happened, but it seems the software running Stack Exchange doesn't allow that tag in the questions. I have a vague idea of why this happens; I just need to verify it.
As per Are tags with a name made of just numbers still allowed? this has been ...
Sorry about this; this was my bad. It was impacting an API. I verified that we didn't have pure numeric tags on some number of sites, but I obviously failed and didn't thoroughly check all of them, which is my error. I will find another approach for the problem that I was trying to fix. The code has already been reverted. Again, sorry.
Instead of making the two tags synonym, I have deleted them, since I agree with MPD.
I don't think we have users who answer questions about warning messages, and just to those questions. The fact then that some code is causing an warning message is not so relevant for answering to need its own tag.
As I mentioned in my comment, the edit was approved after the post was deleted, so it took a bit for the system to catch up. The system did notice that you were "owed" a 2-point rep reduction, but it simply hadn't taken effect yet.
I forced a rep recalc on your profile, so you should see the accurate rep display:
I have renamed migrate.module as migrate, and merged migrate-module with it. The reason I kept migrate.module (after renaming it) is that it had already a tag wiki.
The reason there was entity-module (which I renamed entity-api-module) is because the entity API is a part of Drupal, and there is a third-party module that is the Entity API module. There was ...
It's now possible to retract a raised flag. Once flagged a post, clicking on flag will show a dialog box similar to the following one.
Instead of the Flag Answer or Flag Question button, there is the Retract Flag button that allows to retract the raised flag, and eventually flag the post for another reason.
I second this. Yesterday, I posted comments asking somebody with a (IMHO) very confused question to improve specific points. This morning, the user had added some comments that did not improve things (they made the question even more confusing - again IMHO). So I flagged it as "low quality".
Then, I few hours later, the OP had cleaned up the question. ...
Totally agree with the disparity between dots and dashes...I've changed all questions tagged with migrate.module to migrate-module, which follows the standard tag naming 'strategy' more accurately.
With regard to the -module bit...I don't think there's an issue there to be honest.
entity-module is so-named because there's another tag (entity), which is a ...
The site's topic setting used in the off topic description was set to drupal. I now changed it to Drupal. The settings are cached, so the change will not be visible immediately. Thanks for reporting it.
I have fixed the tags. Now there are two tags:
Upgrading a module/site is different than updating it; the first is generally a more complex operation, and often the more problematic one.
Users who answer updates questions could not be prepared to answer upgrades questions; users who are checking if somebody had their same upgrading problem ...
Using the tag for the module is much better, IMO. It would be too broad, if it is used for any configuration question.
The tag is actually used from the following questions, which have very few in common:
How to choose between Bean, Boxes and Fieldable Panels Panes?
Parsing a multi-valued theme-setting into to two defaults results in theme-settings not ...
As far as I can see, the questions using mail are really referring to emails. I made them synonyms. mail is remapped to email.
updating post history, 51 rows affected
updating posts, 37 rows affected
updating PostTags associations, 28 rows affected
removing/renaming old tag, 0 rows affected
updating count for master tag, 1 rows affected
Confirmed on Chrome with Windows 7 Professional x64.
Seems to be related to the div.bulleten-item-type CSS rule:
Indeed, editing the width from 25px to 15px (shaving off 10px), fixes it:
as per se:
This seems to be a partial fix, however, since Chrome ignores width on the content:
I have removed relationships from the questions where the tag was referring to a generic relationship, and renamed it views-relationships. There could still be some questions using views-relationships that should not be using it because the question is not about a view relationship.
I also edited the tag wiki for that tag to the following text:
This tag ...