Skip to main content
Inspiring
July 2, 2018
Answered

Captivate 9 - jQuery Version

  • July 2, 2018
  • 2 replies
  • 435 views

Hello,

Recently I've upgraded to a new computer, and had to re-install captivate 9. I am working on an older project, and noticed that the jQuery version is different from what I am seeing now. On my previous computer Captivate was publishing out jquery-1.11.3.min, and now its putting out jquery-1.6.1.min. Does anyone know how I would go about changing this setting back to 1.11.3 for all future published files?

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer victoriak23188594

My current version of captivate 9 is using an older version of jQuery than it was previously publishing out as. This caused some issues with some buttons that are created outside of captivate, using JavaScript. It's no matter now though, I was able to pull the project into 2017 and it is now publishing out with the jQuery version I require.

I'm thinking perhaps I found an older version of 9, before it was updated, when I re-installed Captivate a few weeks ago. Moving the project into 2017 resolved my issue.

2 replies

RodWard
Community Expert
Community Expert
July 3, 2018

There is no setting inside Captivate to change the version of JQuery used.

The most likely reason Captivate is using a more recent version would be that it has resolved some bugs or has added functionality.

Why would you want it to revert back to an earlier version? 

victoriak23188594AuthorCorrect answer
Inspiring
July 3, 2018

My current version of captivate 9 is using an older version of jQuery than it was previously publishing out as. This caused some issues with some buttons that are created outside of captivate, using JavaScript. It's no matter now though, I was able to pull the project into 2017 and it is now publishing out with the jQuery version I require.

I'm thinking perhaps I found an older version of 9, before it was updated, when I re-installed Captivate a few weeks ago. Moving the project into 2017 resolved my issue.