Title: JS errors opening composer Last modified: August 22, 2016 --- # JS errors opening composer * Resolved [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/) * Hi * Composer is not working, I go through the process of creating a step but nothing happens after a click the save button. It just continues to show the assembling 1s and 0s by hand. * I checked the js console and found errors * ``` Failed to load resource: the server responded with a status of 403 (Forbidden) 2http://assets.sidekick.pro//walkthrough-audio-placeholder.mp3 Failed to load resource: the server responded with a status of 403 (Forbidden) composer.sidekick.pro/tag/latest/sidekick-composer.js:14 [Composer]: Error DOMException: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://sitename.com.au" from accessing a cross-origin frame. composer.sidekick.pro/tag/latest/sidekick-composer.js:14 [Composer]: Error DOMException: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://sitename.com.au" from accessing a cross-origin frame. composer.sidekick.pro/tag/latest/sidekick-composer.js:14 [Composer]: Error DOMException: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://sitename.com.au" from accessing a cross-origin frame. composer.sidekick.pro/tag/latest/sidekick-composer.js:5 TypeError: Cannot read property 'points' of null at h.addPointFromStep (composer.sidekick.pro/tag/latest/sidekick-composer.js:12) at composer.sidekick.pro/tag/latest/sidekick-composer.js:12 at l.$get.l.$broadcast (composer.sidekick.pro/tag/latest/sidekick-composer.js:6) at composer.sidekick.pro/tag/latest/sidekick-composer.js:13 at l.$get.l.$broadcast (composer.sidekick.pro/tag/latest/sidekick-composer.js:6) at composer.sidekick.pro/tag/latest/sidekick-composer.js:13 at i (composer.sidekick.pro/tag/latest/sidekick-composer.js:5) at composer.sidekick.pro/tag/latest/sidekick-composer.js:5 at l.$get.l.$eval (composer.sidekick.pro/tag/latest/sidekick-composer.js:6) at l.$get.l.$digest (composer.sidekick.pro/tag/latest/sidekick-composer.js:5) composer.sidekick.pro/tag/latest/sidekick-composer.js:12 [Composer]: Entering player state shutting off (program):4 Template.Bucket_v2 Arguments[2] (program):4 Template.Bucket_v2 Arguments[2] composer.sidekick.pro/tag/latest/sidekick-composer.js:12 [Composer]: Already loaded, resuming composer.sidekick.pro/tag/latest/sidekick-composer.js:14 [Composer]: Error DOMException: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://sitename.com.au" from accessing a cross-origin frame. composer.sidekick.pro/tag/latest/sidekick-composer.js:14 [Composer]: Error DOMException: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://sitename.com.au" from accessing a cross-origin frame. composer.sidekick.pro/tag/latest/sidekick-composer.js:14 [Composer]: Error DOMException: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://sitename.com.au" from accessing a cross-origin frame. composer.sidekick.pro/tag/latest/sidekick-composer.js:5 TypeError: Cannot read property 'points' of null at h.addPointFromStep (composer.sidekick.pro/tag/latest/sidekick-composer.js:12) at composer.sidekick.pro/tag/latest/sidekick-composer.js:12 at l.$get.l.$broadcast (composer.sidekick.pro/tag/latest/sidekick-composer.js:6) at composer.sidekick.pro/tag/latest/sidekick-composer.js:13 at l.$get.l.$broadcast (composer.sidekick.pro/tag/latest/sidekick-composer.js:6) at composer.sidekick.pro/tag/latest/sidekick-composer.js:13 at i (composer.sidekick.pro/tag/latest/sidekick-composer.js:5) at composer.sidekick.pro/tag/latest/sidekick-composer.js:5 at l.$get.l.$eval (composer.sidekick.pro/tag/latest/sidekick-composer.js:6) at l.$get.l.$digest (composer.sidekick.pro/tag/latest/sidekick-composer.js:5) sidekick-composer.map:1 GET http://composer.sidekick.pro/tag/latest/sidekick-composer.map 403 (Forbidden) ``` * [https://wordpress.org/plugins/sidekick/](https://wordpress.org/plugins/sidekick/) Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/js-errors-opening-composer/page/2/?output_format=md) [→](https://wordpress.org/support/topic/js-errors-opening-composer/page/2/?output_format=md) * Plugin Author [Ben Fox](https://wordpress.org/support/users/benfox/) * (@benfox) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923617) * Thanks for letting us know and for the detailed error description. We’re on it. * Would you mind telling me which browser and OS you’re using? * Apologies for the inconvenience. * Ben * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923623) * Thanks for the quick response. * OS = Windows 8.1 Browser = Chrome v41 * Plugin Author [raptor235](https://wordpress.org/support/users/raptor235/) * (@raptor235) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923643) * Hi, we just ran a few tests on our end and things are looking ok. From the messages you’re seeing it might have been a MaxCDN issue. Would you mind giving it one more try and see if you’re still seeing the issue? * If you are then visit [http://debug.netdna-cdn.com/](http://debug.netdna-cdn.com/) and let us know which MaxCDN datacenter you’re being directed to. * Thanks so much. * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923654) * I’m not using a CDN * Plugin Author [raptor235](https://wordpress.org/support/users/raptor235/) * (@raptor235) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923703) * SIDEKICK uses a cdn to deliver the code. Did you get a chance to check again? * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923707) * Ah, I see. Just checked now still have the errors. * Plugin Author [raptor235](https://wordpress.org/support/users/raptor235/) * (@raptor235) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923708) * Thanks Eben, * Can you try that CDN link to tell us which datacenter you’re hitting and also if you paste in the following link what do you see -> [http://assets.sidekick.pro//walkthrough-audio-placeholder.mp3](http://assets.sidekick.pro//walkthrough-audio-placeholder.mp3). * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923712) * Virginia Datacenter. * When I first tried the link I saw an xml page with the error message. * Then I removed a `/` from the url so it was `http://assets.sidekick.pro/walkthrough- audio-placeholder.mp3` * Then a saw the mp3 file, now when I reload the wordpress admin the mp3 file is loading but I’m still getting a 403 on the `http://composer.sidekick.pro/tag/ latest/sidekick-composer.map`. * Plugin Author [raptor235](https://wordpress.org/support/users/raptor235/) * (@raptor235) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923715) * Great thank you this is all very helpful. Lastly just want to confirm you’re using the latest version of the plugin? * We’re releasing a new version of the plugin Monday so we’ll make sure this issue is taken care of. * Again thank you for taking the time to sort out what the issue was. * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923717) * Yep latest version of WordPress and Sidekick. Looking forward to Monday to see if it is fixed 🙂 * Plugin Author [raptor235](https://wordpress.org/support/users/raptor235/) * (@raptor235) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923830) * The latest version was released this morning give it a try when you can. * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923839) * Hey Bart * Unfortunately still the same issues plus after I updated the plugin it still shows that it needs updating and the current version has this “Version %%version%%”. * The update seemed to work properly. * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923840) * I deactivated the plugin and it now shows two copies in the plugins list. * One that says Version 2.2 and one that says Version %%version%%. * Plugin Author [raptor235](https://wordpress.org/support/users/raptor235/) * (@raptor235) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923841) * Hi the double listing of Sidekick has been fixed in a release hotfix release 5 minutes ago. The 403 error on the .map file is expected behaviour for Chrome it looks for it automatically but the default audio issue should have been fixed. * In your sourcecode of the page you’re seeing the issue on when you search for audioPlaceholderUrl can you send us the value for that property? * It should be showing * audioPlaceholderUrl: ‘//assets.sidekick.pro/walkthrough-audio-placeholder.mp3’, * Thanks again. * Thread Starter [haleeben](https://wordpress.org/support/users/haleeben/) * (@haleeben) * [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/#post-5923849) * Deleted the plugin and reinstalled seems to working now, looking forward to testing it out. * One quick question, does there have to be a audio track or can I just have the visual pointer instructions? It looks like I would still need to upload a blank audio track is that correct? * Thanks. Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/js-errors-opening-composer/page/2/?output_format=md) [→](https://wordpress.org/support/topic/js-errors-opening-composer/page/2/?output_format=md) The topic ‘JS errors opening composer’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/sidekick_e3967c.svg) * [Sidekick](https://wordpress.org/plugins/sidekick/) * [Frequently Asked Questions](https://wordpress.org/plugins/sidekick/#faq) * [Support Threads](https://wordpress.org/support/plugin/sidekick/) * [Active Topics](https://wordpress.org/support/plugin/sidekick/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/sidekick/unresolved/) * [Reviews](https://wordpress.org/support/plugin/sidekick/reviews/) * 17 replies * 3 participants * Last reply from: [raptor235](https://wordpress.org/support/users/raptor235/) * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/js-errors-opening-composer/page/2/#post-5923856) * Status: resolved