Skip to main content
Murdoch83
Participant
July 17, 2020
Answered

Syntax Error, project won't load

  • July 17, 2020
  • 2 replies
  • 522 views

My team has been working on a project in Captivate 2019 (11.5.1.499)

We have been testing the project (HTML publish) locally on our machines and everything works fine, but when we try to upload to the web, we get a weird syntax error in the CPXHRLoader.js and a reference error in the index.html "cp is not defined", and the project won't load.  I confirmed that the CPM.js is in the proper folder. It's just weird that it works locally but not online. (I also tried on multiple computers/browsers to make sure it wasn't a firewall/network/browser issue) Has anyone encountered this?  

    This topic has been closed for replies.
    Correct answer Murdoch83

    Solved: It turns out that there were extra blank lines at the end of some of the captioning text fields in the slide notes panel. Once I deleted those, the project ran fine. Also, before I found the fix, I discovered that the error was only happening on one webserver. When uploaded to a different server, it ran fine. Still not sure why this would be an issue. 

    2 replies

    Murdoch83
    Murdoch83AuthorCorrect answer
    Participant
    July 27, 2020

    Solved: It turns out that there were extra blank lines at the end of some of the captioning text fields in the slide notes panel. Once I deleted those, the project ran fine. Also, before I found the fix, I discovered that the error was only happening on one webserver. When uploaded to a different server, it ran fine. Still not sure why this would be an issue. 

    RodWard
    Community Expert
    Community Expert
    July 27, 2020

    One of the servers may have been a Windows IIS server and the others may have been Apache/Linux servers.  They tend to handle some things differently.

    Lilybiri
    Legend
    July 17, 2020

    Does the webserver support JSON?

    Murdoch83
    Murdoch83Author
    Participant
    July 17, 2020

    Yes, it does. I also discovered earlier builds did load properly.