Forum Discussion

TerriWeisser1's avatar
TerriWeisser1
Community Member
11 years ago

Force Commit during Publish in Storyline (v1) and Presenter ('13)

Our company has discovered a problem when content is published to AICC (through either Storyline 1 or Presenter '13). There is a setting within the configuation.js and lms.js files that force a comm...
Presenter 360
Studio 360
StevenStark's avatar
StevenStark
Community Member
9 years ago

Hey Deborah, 

I know this post is a little old, but did you ever find a solution to your problem? 

For my purposes I just changed the time in the lms.js and Configuration.js files to a very large number and that made it do what I needed it t do.  This was in Presenter '13 and QM '13. 

However, now that we switched over to Studio 360, the problem is back.  Changing the time in the lms.js and Configuration.js files is not preventing commits from happening every 1 minute.  We tried altering some code in the html5/lib/scripts/app.min.js file that we thought might be causing the commits to take place, but it didn't help. 

Just curious if you ever figured out a solution.  My guess is that Articulate was not very helpful.  And something like this is generally beyond what the Articulate Community is capable of handling.  

Thanks, 

Steven 

JulieHamilton-4's avatar
JulieHamilton-4
Community Member
5 years ago

Hey Steven, now I'm the one replying to an old post - Did you ever figure out a solution for this issue in 360?

We just switched over as well, and now nothing works to stop it from eating up the attempts. We had done the same thing previously, setting the force commit to 28800000 to keep it from going off.

Thank you, 

Julie