What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 133 Stack Exchange communities.

On Drupal Answers, I renamed a tag from field-validation to form-field-validation, to avoid ambiguities between form fields, and entity fields, which are two different things. I have then noticed the tag was already used for both form field validation, and entity field validation, and I tried to rename back the module. What I get is that form-field-validation is being removed, but field-validation is not being added.

screenshot

I was allowed to change from field-validation to form-field-validation, but apparently, I am not allowed to do vice versa.

share|improve this question
    
I am seeing 8 and 8; are you still seeing 0? –  balpha Jun 22 '12 at 10:22
    
Yes, I am still seeing 0. I don't know if this could make any difference, but when I write field-validation in "New Tag Name," it gets auto-completed in form-field-validation, and I press the escape key to avoid accepting it. –  kiamlaluno Jun 22 '12 at 10:27
    
Okay, try now, please. –  balpha Jun 22 '12 at 10:38

1 Answer 1

up vote 7 down vote accepted

Most of the stuff in that merge preview gets its data directly from the database (it's not like this is a millisecond performance-crictical section of the site); the only thing that is instead coming from a cache (our famous tag engine of doom) is getting the database ids of the tags you're merging. Since your previous merge changed the ids, the cached value and the database values were out of sync.

And since the tag merge is a silent operation (doesn't create revisions), the tag engine didn't notice it had to refresh the cache, which is why you still saw the old values even after an hour (I saw the correct ones because I hit a different server than you, where the cache was up-to-date; once I reloaded the cache for the server you were hitting, you saw the correct numbers as well).

One change I'll make is pull those ids from the database as well; the data we're using here should be up-to-date (note that this was only an issue in the preview; the actual tag merge always used current data). But we should also look to ensure that the tag engine is aware of the merge after it has happened.

Some of the above (regarding the tag engine) is guesswork, by the way; I'm anything but an expert on this part of our code*, so Marc may chime in and say "this is all wrong, stupid continental European".

* to be precise, I have no clue about its inner workings

share|improve this answer
1  
Handy chart for Marc Gravell communication reference i.stack.imgur.com/B6uTn.png –  Jeff Atwood Jun 22 '12 at 18:49

You must log in to answer this question.

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