Forum Discussion
Batch publish mode?
I wish. WISH WISH, there was a batch publish ability in SL360. I work on 10+ projects at any one time and when they're finished it's normally a case of Friday afternoon, setting aside everything to simply publish.
Has there been any word on something of this ilk? I personally don't care if it's macro-clunky based, rather than polished. It will always get better :)
Many thanks
random bits of text or objects from one course will start appearing in the other one!
My exact fear, also, but you look too young to have had enough bad experiences to distrust computers to that extent :).
Computer Corollary: - Murphy was irresponsibly optimistic.
Ha ha! I trust my computer but I've been using Storyline since release and I've seen it do some really weird stuff on occasion.
any update on this? I remember Articulate trying to come up with some sort of batch publishing when Chrome updated their policy on media playing automatically that forced users to republish everything. I wonder what happened with that.
Hey Calvin,
Sounds like you are referring to the Articulate Updater. This is something our team is working on updating, but I do not have a timeframe to share.
the autoupdater only changes the js on the published files. i'm thinking of a proper batch publisher where you can publish multiple files. isn't that what's being planned?
Ah, sorry about that Calvin. Your description made me think the updater, but it looks like you'd like to see a similar function that Lawrence originally shared here.
I'd love to understand your thoughts and use-case on a batch publisher as well and you can even share those thoughts directly with our team here.
Here's what I sent over as feature request. Pretty sure somebody sent something like it already.
Basically, select which files you want to publish and the SCORM format. Have an option to zip them up automatically after publishing as well.
When new updates come in, we usually need to re-publish our old projects to apply the fix from that Storyline update. Right now, we have 131 .story files and growing. And if Storyline is going to update every couple of months, we need to do this huge publish very often. It's a huge time sink to do it one by one.
Calvin,
There is a way to change your workflow, and save tons of time. If there is something about your course that isn't working, don't publish it until you have a work-around, or until Aritculate updates SL. If it is working, and you publish it, new updates to SL won't break published output, even if the update makes things that were working before stop working. SL can only change the .story file, not published versions.
It's not that a course is not working, but sometimes storyline updates have some fixes or enhancements that we want applied. to give you an idea, here are a few updates recently that were critical for us:
- audio not playing automatically on chrome 66 (fixed may 8)
- audio continued to play in HTML5 output when switching to another browser tab, causing animations to become unsynchronized (fixed march 6)
- upgrading projects to Storyline 3 produced blank slides, and flickering in html5 (fixed march 6)
- JAWS not reading text in notes at times (fixed Sep 11)
Hi Raphael,
No updates yet, but I appreciate you chiming in and I'll be sure to add you to the report! If you were curious, here's a bit more about how we work to prioritize feature requests.
Are there any updates on publishing courses in bulk? Would be a huge time saver for us.
Hi Dominik,
No updates yet, but I added you to the feature request report!
Here's a bit more about how we work to prioritize feature requests.
Hi, all.
Is there any news on this request?It's been now several years since this request (and others like it) has been made, I wonder if there is any real commitment on Articulate's part to find a solution to this problem that seems to affect several users...
Is there a way for the users to have a look at the feature request report? You should made it public so that people could be aware of existing request and also upvote those they think could be useful.
Thank you.
Hi Raphael.
I understand how such a feature could come in handy, especially for organizations that have a high volume of courses that need to be republished. While this feature hasn't made it to our feature roadmap yet, this discussion is connected to the report, so we'll be sure to notify you when we have news to share.
You can keep an eye on the upcoming features through the link below:
