Forum Discussion
Access Denied error in Rise code blocks (Review 360)
Rise code blocks are throwing an Access Denied error in Review 360 on one of my courses. Here's what I've found through troubleshooting:
- It only happens in Review 360. Totally fine in web and SCORM output.
- It's only happening in an existing course when we've pulled in a working code block template in from our block library.
- When I build a new course from scratch, the code block breaks when I try to copy in a lesson from the problem course (even if that lesson does not contain any code blocks).
- The issue persists even when I scrub any external HTTP links from the code, so I think it's an issue with Review 360 not a true permissions issue.
One solution I'm considering would be to rebuild that course from scratch, pulling in block templates back one at a time, but that would be pretty tedious.
Anyone else running into this issue?
6 Replies
Hello sstone1,
I see that you've opened a support case and that you are working with my colleague, Janina. You're in excellent hands! We'll continue the conversation there, so everything is in one spot!
Thanks LucianaPiazza - yes, Janina's been helping me!
In case anyone else runs into this issue, when we copied the course to Janina's account, it published without access errors. My team is exploring whether there might be a conflict with our Mighty extension.Did you ever figure out if this is an error with the Mighty extension? I am getting this too!
Yes - unfortunately it was a Mighty issue. I had to uninstall it from my browser to resolve it.
Just seeing this now and happy to share my insights. This is a specific bug with Review360 when using Mighty as they don't support the Rise Code review path with how we publish to Review. That being said, you can just flip to the Mighty Interactive HTML Block which is the Mighty version of Code block. Just make the switch and everything will work as expected.
Again, just an issue within Review360 when publishing with Mighty but has a 10 second work around 💥
Hi all! I just wanted to pop in with a bit of additional context for anyone following along. What you’re seeing here isn’t a bug in Review 360, but something that can come up depending on how embedded content is handled. Different tools approach this a bit differently, including third-party options like Mighty.
Review 360 supports Rise 360’s native Code Block as expected. Hope that helps, and really appreciate everyone sharing insights here!
