Hey Illu, your code should work, sometimes things are weird, anyways I don't think it is really necessary to see what build the pages are in line with. If you have time to update to a certain build, why wouldn't you just update to the most recent? Often changes will break or modify functions that in the old builds were possible but in the new ones they are not, so if it comes to updating pages shouldn't you always orientate on the CURRENT build? I am not sure what the info of the build it is in line with helps an editor ... except if its the current one.--Wyeth 07:32, 23 November 2011 (UTC)
- I was for example thinking of the following scenario: The next build (204) gets released. We update the current build number and try to update as many pages as possible but shortly after another build (205) gets released. And another (206). And another (207)...and so on.
Now we have some pages which are line with build 204, some which are in line with 205, etc. But we also might have a few pages which are still in line with the build 203 since we couldn't update the pages in time / the changes were to complex etc.
If we now know with which build a page is in line with we only need to check the changes between that build and the current one. With a message like "This page is/might not be up-to-date." we have to read all of it extensively and check if everything fits to the current build.
You get me now?--Illu 16:39, 23 November 2011 (UTC)
- I do get what you mean, but optimal we shouldn't fall behind like that (and update the pages slowly over time asap). I just don't think its necessary, I see where you are comming from and its not like it hurts anyone, but I wouldn't bother with it... feel free to do as you please though, also get on IRC when you got time :D --Wyeth 17:09, 23 November 2011 (UTC)
Came here to congrats you on a workaround on build changing. Raron 03:49, 2 April 2012 (EDT)