Forum Discussion
Undo command glitchy for copy/paste in Articulate Rise
I've noticed more and more that undo (Command ⌘ + Z) is very glitchy. In the past it seemed to work fine, but recently (maybe last month or so) it doesn't function as expected.
For example, in the list feature I tried to undo a sentence I deleted and it reset the block to the placeholder text. And, it also modified a different block. In this same experience, while I was selecting the text box below the list, I hit undo and it modified the list block instead.
Redo hot keys are also glitchy. In the same example as above, redo doesn't affect the list block.
I'm sure there are more examples, especially in the "interactive" blocks; I've run into this many times over the past couple of weeks. This is just what prompted me to log this.
3 Replies
I had a screen recording but for some reason the forum wasn't letting me upload an mp4. Here is a gif version.
Oddly, like the review block bug I logged, I couldn't recreate the issue today. I didn't try very hard tbh, but maybe the issue was also resolved in the latest update?Hi KimberlyPeterso,
I’m happy to chime in here, thanks for the update! I’m glad to hear the undo function is working again on your end. I appreciate you sharing the screen recording.
If the issue happens again, I recommend clearing your browser cache and cookies and reaccessing the course. You can also try using Incognito mode to help rule out possible browser extensions that may be causing the problem.
Please let us know if it recurs. We’ll be happy to continue troubleshooting with you.
Hi KimberlyPeterso,
Thanks for reaching out!
I've been testing out the Command + Z keyboard shortcut to undo text, but I'm unable to replicate the behavior you've described. Here's a quick look at a sample course where I used the Command + Z shortcut to undo my latest action.
You mentioned this issue began in the last month. Is it consistent across courses or intermittent? Is it possible to share a screen recording of the issue, or a copy of your course? I'd like to dig a bit deeper into why this feature is behaving oddly for you!
