Hi alanh,
yes same here. I testet a phrases’ course just now. Behaviour seems to be back to normal (typing required even with long sentences). Hope it stays that way.
3 Likes
I just compared their code again, and they made exactly one change; they removed the check that disabled typing answers longer than 15 characters.
4 Likes
Sounds like a conscious decision to put things back as they were, then. As Foorgol says, “hope it stays that way” now!
2 Likes
This is amazing! Thanks so much in taking the time to fix this. It is such a great help on your behalf.
Many many thanks for your kindness and generosity!
2 Likes
I wonder what may of prompted them to make the change to begin with? Perhaps they were getting feedback from users about getting answers wrong with a simple typo like hitting s instead of d because they are right next to each other on the keyboard etc… It can’t be that hard to write an algorithm that detects a range of typos and ignores it rather than fine tuning every sentence in the creation options.
Yes, it was definitely a conscious decision, because changes don’t just “arise” in the code by themselves, contrary to what they would have us believe. They obviously have a plan, had meetings about it, and then sent out instructions to the developers and coders to implement their plan.
Why they’ve chosen to backtrack on this change, and once again not to be forthcoming with us, is a question that remains to be answered. But I don’t think that they’ve abandoned their plans altogether, but rather made a temporary tactical retreat.
such an algorithm is probably impossible, because it would need to be able to decide whether it was a typo or a grammatical error. Often it is intended to be precise with the order of two letters or the accent, because it can change the meaning totally. And that’s true for every language. And to decide if it was just a typo that needs to be auto corrected or if the user just got it wrong is impossible for an algorithm. Only the user itself can know that.
So it is not just about making the mistake correct, it is about finding out if the user also knows what would have been correct.
But on-topic: Let’s hope it stays this way and it wasn’t just a first test that will be repeated or worse even implemented for some reason.
Thanks so much!
For me, typing tests for more than 15-16 characters is currently back to normal. Without any extra script.
Hope that it stays that way!
2 Likes
Everything back to normal here too, and nobody has been complaining that they still have the problem - so I guess we can conclude that it’s been fixed. Great! 
1 Like
The easy solution to the typo problem is to add a button allowing a user to select “this was a typo” after a wrong answer rather than any algorithm.
3 Likes
Actually what I’d like is that if you only get 1 or 2 letters wrong that you get a chance to retype it.
You shouldn’t get as many points etc. but you shouldn’t get marked wrong either.
Ideally there’d even be a “no I really did get this wrong” button too.
Back to normal. Great! My only grumble is that it would have been nice to have had prompt word from the Memrise team, but I’m very glad to have normal service resumed.
Still not working for me. I did update @cooljingl’s ‘All Typing’ script yesterday and that worked perfect. Most was typing just some multiple choices. But today, I am back to about 95% multiple choice and hardly any typing. Multiple choice is not working for me. I need to type the word(s) to remember them.
Thank you for the script update. It was working. But I think memrise changed something again.
It’s still working for me …
so weird…
Ha … I think I found the problem. I left the 2 functions for Learning’ and ‘Mistakes-Review’ to ‘false’. Now that I changed it it’s working like a charm. After you @Ziutek mentioned that it’s still working for you I took a closer look at the script. 
@MemriseMatty, there are several current threads now running about the recent return of the bug which is preventing typing tests on phrases in some courses. I have posted on this one because it contains the history.
My experience while reviewing today is that the ‘bug’ was present in my Memrise-created/supported Spanish courses but not in A1 Spanish (which is no longer supported by Memrise), where I was presented with typing tests for phrases.
Can you please let us have an explanation of what has caused this bug to reappear and an estimate of when we can expect it to be removed. As many of us have said before, tapping tests and multiple choice tests have limited value. Typing tests are a key element of the learning process.
Thanks!
9 Likes