Please provide a brief description.
Please make a selection.
Please make a selection.
Please provide a description.
@jcarpenter1986
Account
Account
Allowing Amazon AWS S3 to communicate with Cluelabs
Hi guys, I have a course all up and running and the analytics widget works totally fine when I just use Articulate Review, but now that the course is up on it's hosting (Amazon s3) Cluelabs is no longer collecting data even though the S3 Bucket is set to public and to not block anything...can you guys help me out? I'd love to analytics be tracked and also be hosted on Amazon
Reply
Posted on 7/19/2024
@support
Hello. There doesn't seem to be a reason why it won't work on AWS S3. We can check what's happening there, please share the link to your course on S3 either here or through the custom development ticket.
Reply
Posted on 7/19/2024
@jcarpenter1986
Of course!!
Here's the link to the s3 course:
[URL]
and this is the widget that is embedded into the course masterslides:
[URL]
This course is also hosted on Wordpress with similar issues of not communicating with Cluelabs
Here's the link to the s3 course:
[URL]
and this is the widget that is embedded into the course masterslides:
[URL]
This course is also hosted on Wordpress with similar issues of not communicating with Cluelabs
Reply
Posted on 7/20/2024
@support
Hello,
The issue you are having is not related to AWS or Wordpress.
Storyline stores all javascript triggers in a single file, so an error in any one of them breaks the rest of the javascript triggers. In your case, the trigger containing the text "Send the data to the Google Apps Script Web App" is what's breaking everything. The URL needs to be in quotes and that line needs to end with a semicolon.
Once you fix that, the rest of the triggers should then work as well (provided there are no other mistakes elsewhere in the code).
The issue you are having is not related to AWS or Wordpress.
Storyline stores all javascript triggers in a single file, so an error in any one of them breaks the rest of the javascript triggers. In your case, the trigger containing the text "Send the data to the Google Apps Script Web App" is what's breaking everything. The URL needs to be in quotes and that line needs to end with a semicolon.
Once you fix that, the rest of the triggers should then work as well (provided there are no other mistakes elsewhere in the code).
Reply
Posted on 7/20/2024