I just experienced a major bug while patrolling on my tablet. When I pushed rollback, it would look like the edit rolled back - but it didn’t! Yikes. Can other folks who have tablets quickly test this to see if this bug is happening to you. I’m hoping it was unique to my iPad and caused by me testing lots of new features. Here’s how to check if you have this bug: 1. From your tablet, go to RC patrol. (You can get there by clicking the “dashboard” button in the bottom navigation or any other way.) 2. Press “Rollback” on any edit 3. Check page history (you can get there from “advanced” on RC Patrol widget). If page history doesn’t show that you rolled back the page, it’s not rolled back! Let me know if the rollback worked or not. If you have a tablet can you quickly test this so I know if this bug is widespread and need of emergency work.
the old way works Jack.(exceptioning a bug i think i told the community about) However, the app doesnt save the revert on my ipod touch 4th gen with newest iOS 6.1.3.
The screen flickers as if its about to save, then the yellow bar clears off, and the message saying the revert was done doesnt show. I checked my contributions and its not there. I checked page history, and its not there either.)
system
4
Hey Jack! I am using tablets but mine is fine. I used both iPad and iPhone.
system
5
Are you using Safari? If so, try clearing the cache/history. I use Chrome on my iPad, and I’ve never had an issue. I also feel it’s a better browser.
system
6
Still perfect for me even if I use safari.
I think I briefly told you, Jack, about this a while ago, but never knew it was a bug. I tried it on my iPad with Safari and you’re right, it didnt work. Same results with my iPod touch. I noticed this bug a long time ago on my iPod (which is why I never patrol there), but this is the first time I’ve seen it on a tablet.
I forgot to mention that I was patrolling on Safari. I feel Chrome for iPod touch to be a bit buggy and in need of several critical ideas that would make it better, and plus, I do like using something that was already there to begin with.
system
9
@Byankno1
Which generation iPod touch is it? One thought is that different generations of iOS devices may be running different versions of iOS, so an older device could possibly be running an older, un-updated version of Safari that might not support some newer web technologies. Anyone have any thoughts on this? So it might be helpful for folks to post which edition of the iPod or iPad, as well as what iOS version. Mine is a 3rd gen. iPad running iOS 6.1.3.
system
10
I think the devices are just smart enough to know you need to take a day off and enjoy a break, all of the unpatrolled edits are not going anywhere, in fact, there will be lots more tomorrow!
system
11
I created a poll to try to make sense of this problem. If you use a tablet or phone on wikiHow for RC patrol, take a moment and answer these 4 questions. Feel free to submit multiple responses if you use multiple devices or browsers. https://docs.google.com/forms/d/1xFl21C7wTW28eY7pjhV8l9Iy_uhzdun4JZ1JSGssMBE/viewform
@isorhythmic
see my earlier discussion to find iOS version number.
@isorhythmic
I sent my response
wikiHaus engineer Jordan, whipped up a quick fix over the weekend. We *hope* we have solved this issue. Can anyone please test there phones or tablets now (ideally using Safari) and let me know if they are encountering this problem?
It won’t met me roll back at all on my Kindle Fire
system
17
If you’d still like to help out with patrolling while we get this bug fixed, try the “traditional” patrolling interface: http://www.wikihow.com/Patrol-Recent-Changes-on-wikiHow-(Traditional)
The “rollback” button is still working on mobile for me when I use that (but double check to make sure on your device!).
system
18
I just pushed another potential fix for this issue. It would be great If folks can test it out on their tablets and let me know if it is working. One note: The fix requires you close RC patrol and reopen in order for it to work. Please do this before testing. Thanks!
I hope this fixes the bug. @Rosejuice
and @Byanko1
and others who were experiencing this bug. After you close RC and re-open it, are you still finding this bug?
No. The bug appears to be gone. Thanks!
