I made changes to my course and tried to publish to review but I keep getting
"Something went wrong: There was an error publishing your course. Please try again."
I've published this course for review previously, and its been fine.
If I duplicate the course I still cant publish it to review. if I duplicate older courses I cant publish them to review.
I cant Publish to LMS either.
Does this mean there is an issue with the course its self? if I delete all the lesson pages I can publish the course, is there a size limit I've reached? how can I check this?
I've used some jpegs with _NOPROCESS_ at the end but also a lot of .svg files.
I also have this exact same problem. A small course with half the content won't publish - but the longer courses with the same content, will publish. The only difference is a few embedded google forms - clearly this is a bug affecting more than one person if the above comments are anything to go by?
I'm having the same issue. I published my course for Review on Monday, made a few client edits and tried to publish last night and got the message "Something went wrong: There was an error publishing your course. Please try again." I tried again this morning.
My colleague just had this same problem. She found out that some of the new features (images as backgrounds and so on) were causing this on her new courses. She removed those, and it worked again.
All those were working yesterday just fine, so this might something that will get fixed soon back to normal.
I'm not sure if this limited to those newer features, or if there are more elements that are currently broken.
And my colleagues problems just returned, but she was able to get one review published.
I have not come across with some of my old content, so it might be some spesific elements that are currently broken. And perhaps the "what is currently broken" keeps changing on us as we speak.
This was taken from a historic post similar to our problem - maybe it's helpful for some of you?
"We have an issue with exporting courses that contain an asset with the % symbol in the file name. That could include an image, a PDF, or another piece of media. We're working on a fix, and I'll let you know when it's out!"
I won't be making any wholesale changes to my content at the minute. I'm gonna ride this one out and trust the techies to come up with a fix...
This message may contain confidential information. If you are not the intended recipient please:
i) inform the sender that you have received the message in error before deleting it; and
ii) do not disclose, copy or distribute information in this e-mail or take any action in relation to its content (to do so is strictly prohibited and may be unlawful).
Thank you for your co-operation.
NHSmail is the secure email, collaboration and directory service available for all NHS staff in England. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.
For more information and to find out how you can switch visit Joining NHSmail - NHSmail Support
This message may contain confidential information. If you are not the intended recipient please:
i) inform the sender that you have received the message in error before deleting it; and
ii) do not disclose, copy or distribute information in this e-mail or take any action in relation to its content (to do so is strictly prohibited and may be unlawful).
Thank you for your co-operation.
NHSmail is the secure email, collaboration and directory service available for all NHS staff in England. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.
For more information and to find out how you can switch visit Joining NHSmail – NHSmail Support
We were also unable to publish our course on Review. So we found the buggy element: We made a copy of the course for testing purposes, deleted one chapter at a time and tried to upload the course after each deleted chapter. When the error message finally disappeared the first time, we knew we had found the buggy chapter. In our case, it was the third one.
After that we did the same with all the elements of that chapter: delete one block - try to publish - error still there? Delete the next block - try to publish ... Until publishing is possible.
This way we found out that there was a block with an attachment, but the attachment was empty. After we deleted this empty block, publishing was possible.
We replaced this block in the original course and now everything works fine!
As mine was a 'test' course, I'd put some block 'place holders' in without any content (in my case it was to access a downloaded file). Once this was remedied, the publishing worked a treat. Thanks!
I had an empty placeholder for a document attachment. I uploaded something to it and was then able to publish. But this only recently became a problem - I'd been publishing for weeks with the placeholder there.
Empty file attachment blocks in my course were preventing SCORM publishing, so once deleted, or when files are added it was possible to publish successfully.
I heard back from the Articulate Rise techie and he told me it was because my course had an empty attachment block. I learned something new today. I didn't know we couldn't have empty blocks if we want to publish for Review. I had it there as a placeholder to remind the client that I need that document from them. After I removed the empty attachment block, it published! So, I think a few of you should be hired as Articulate techies :-)
35 Replies
I have the exact same problem... Is it a bug or is there something wrong with the course ?
I also have this exact same problem. A small course with half the content won't publish - but the longer courses with the same content, will publish. The only difference is a few embedded google forms - clearly this is a bug affecting more than one person if the above comments are anything to go by?
I'm trying to publish to web, and also publish to LMS - neither are working
I'm having the same issue. I published my course for Review on Monday, made a few client edits and tried to publish last night and got the message "Something went wrong: There was an error publishing your course. Please try again." I tried again this morning.
My colleague just had this same problem. She found out that some of the new features (images as backgrounds and so on) were causing this on her new courses. She removed those, and it worked again.
All those were working yesterday just fine, so this might something that will get fixed soon back to normal.
I'm not sure if this limited to those newer features, or if there are more elements that are currently broken.
I just tried publishing a course I haven't touched in months and have published previously - same problem....
I tried this with 2 courses. One was published to Review OK, the other got the same error you guys are reporting...
And my colleagues problems just returned, but she was able to get one review published.
I have not come across with some of my old content, so it might be some spesific elements that are currently broken. And perhaps the "what is currently broken" keeps changing on us as we speak.
Same for me, I tried with old projects and I am unable to publish them to review anymore. They don't use any of the new features.
This was taken from a historic post similar to our problem - maybe it's helpful for some of you?
"We have an issue with exporting courses that contain an asset with the % symbol in the file name. That could include an image, a PDF, or another piece of media. We're working on a fix, and I'll let you know when it's out!"
I won't be making any wholesale changes to my content at the minute. I'm gonna ride this one out and trust the techies to come up with a fix...
Thanks everyone! I'll wait for the Articulate Rise techies to respond too. Hopefully they'll let us know soon that it's fixed.
I just submitted a case because we haven't heard back from an Articulate person yet.
Between yesterday afternoon and this morning, I successfully published close to 40 Rise recently edited courses and microlearnings.
Published to LMS, PDF, and Review 360.
Any update on this?!
I can't publish a Review Course either - or a duplicate. Most annoying - it's supposed to go to the SMEs today
I successfully published 2 and failed on the third.
Issue is still not fully fixed............
************************************************************************************** ******************************
This message may contain confidential information. If you are not the intended recipient please:
i) inform the sender that you have received the message in error before deleting it; and
ii) do not disclose, copy or distribute information in this e-mail or take any action in relation to its content (to do so is strictly prohibited and may be unlawful).
Thank you for your co-operation.
NHSmail is the secure email, collaboration and directory service available for all NHS staff in England. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.
For more information and to find out how you can switch visit Joining NHSmail - NHSmail Support
Thanks Lorraine 🙂!
************************************************************************************** ******************************
This message may contain confidential information. If you are not the intended recipient please:
i) inform the sender that you have received the message in error before deleting it; and
ii) do not disclose, copy or distribute information in this e-mail or take any action in relation to its content (to do so is strictly prohibited and may be unlawful).
Thank you for your co-operation.
NHSmail is the secure email, collaboration and directory service available for all NHS staff in England. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.
For more information and to find out how you can switch visit Joining NHSmail – NHSmail Support
We were also unable to publish our course on Review. So we found the buggy element: We made a copy of the course for testing purposes, deleted one chapter at a time and tried to upload the course after each deleted chapter. When the error message finally disappeared the first time, we knew we had found the buggy chapter. In our case, it was the third one.
After that we did the same with all the elements of that chapter: delete one block - try to publish - error still there? Delete the next block - try to publish ... Until publishing is possible.
This way we found out that there was a block with an attachment, but the attachment was empty. After we deleted this empty block, publishing was possible.
We replaced this block in the original course and now everything works fine!
That seems the fix the buggy courses in our end too.
Thank you very much of troubleshooting! I though of doing that very same thing, but could not find the time for it yet.
Of course there might be other buggy elements at the moment, but that is the only one that we have encountered so far.
As mine was a 'test' course, I'd put some block 'place holders' in without any content (in my case it was to access a downloaded file). Once this was remedied, the publishing worked a treat. Thanks!
I had an empty placeholder for a document attachment. I uploaded something to it and was then able to publish. But this only recently became a problem - I'd been publishing for weeks with the placeholder there.
This post was removed by the author
Empty file attachment blocks in my course were preventing SCORM publishing, so once deleted, or when files are added it was possible to publish successfully.
My engineer mentioned to me that MS is identifying some of the files as Malware
I heard back from the Articulate Rise techie and he told me it was because my course had an empty attachment block. I learned something new today. I didn't know we couldn't have empty blocks if we want to publish for Review. I had it there as a placeholder to remind the client that I need that document from them. After I removed the empty attachment block, it published! So, I think a few of you should be hired as Articulate techies :-)