OK here's whats happening. I publish to review 360, but then make a change (Rise360) then republish. Normally I would get two options, publish to review a new one or publish over an existing one. Now though even though I have already saved once, I dont get the option to resave the new version, so I end up with two....In this attachment you can see it has happened TWICE lately. What's going on here?
Thank you for those details. It sounds like you're hitting a snag with Rise 360 and Storyline 360 when publishing to Review 360. Is this correct?
Here's what it looks like when I publish a course to Review 360:
Would you mind sharing what it looks like on your end when publishing your Rise 360 course to Review 360?
Secondly, I see that you have multiple Storyline courses in Review 360. Are you seeing that Storyline publishes two versions? If so, I'd suggest first clearing your cache. Here's how to do that.
Please keep us updated! We want to make sure you're up and running as soon as possible!
Forget Rise. It’s actually Storyline 360 that has this problem. (I will be putting the storyline blocks into Rise 360 later though) But that’s not the problem. The problem is when I publish Storyline 360 content to Review, I cannot over save a previously published course, because (even though it IS there), Review does not recognise that I have saved it before.
I have cleared my browser caches and it made no difference.
Thanks - It seems that I have a synch issue with version. Diagnostics routine confirms this. I am checking updates but none are available, so something is wrong....
I can see an update button but it doesnt do anything, and the previous version histroy show Storyline 360 hasnt been updated since 7th April 2020 (hence version 3.38
13 Replies
Hi Brian,
Thank you for reaching out! Let's see if we can get to the bottom of this!
A couple of questions for you as we dive in:
I'm the owner of the content. It seems to be doing this for all storyline 360 courses that I publish to review.
Hi Brian!
Thank you for those details. It sounds like you're hitting a snag with Rise 360 and Storyline 360 when publishing to Review 360. Is this correct?
Here's what it looks like when I publish a course to Review 360:
Would you mind sharing what it looks like on your end when publishing your Rise 360 course to Review 360?
Secondly, I see that you have multiple Storyline courses in Review 360. Are you seeing that Storyline publishes two versions? If so, I'd suggest first clearing your cache. Here's how to do that.
Please keep us updated! We want to make sure you're up and running as soon as possible!
Here’s what happens.
https://360.articulate.com/review/content/bf1615b9-7770-45d1-977a-5b8acfe79160/review
Forget Rise. It’s actually Storyline 360 that has this problem. (I will be putting the storyline blocks into Rise 360 later though) But that’s not the problem. The problem is when I publish Storyline 360 content to Review, I cannot over save a previously published course, because (even though it IS there), Review does not recognise that I have saved it before.
I have cleared my browser caches and it made no difference.
Which version of SL are you running Brian?
Articulate 360 full team package
Storyline 360 v 3.38.21861.0 up to date
Latest version of SL360 is v3.39.22088.0. I just tested with one slide project and it's working as expected.
Here is link to version history
Thanks - It seems that I have a synch issue with version. Diagnostics routine confirms this. I am checking updates but none are available, so something is wrong....
Diagnostics:
Hi Brian
so from Articulate 360 desktop you don't see Update or the versions available?
See this peek video
You might need to log a case with Articulate Support and get them to take a look at what's happening.
I can see an update button but it doesnt do anything, and the previous version histroy show Storyline 360 hasnt been updated since 7th April 2020 (hence version 3.38
Maybe try a repair of Storyline Brian
Thank you - I have now submitted a case to support.
This discussion is closed. You can start a new discussion or contact Articulate Support.