Tool crashes during 'Processing'

[specsoft4283]

Hi! We stumbled across this tool and are excited to try and implement it, so thank you so much for creating this resource.

I am working on getting it working in our Canvas instance, but the tool crashes right after the 'Processing' pop-up with the gif shows. I can confirm...

• No pages are being created
• I have-double checked with BlackBoard that our Ally ID and keys are correct.
• I'm editing the action.php and js file within Brackets for Mac
• Adding the appropriate file locations of these files into the config section of the js file.
• Files are hosted on our web server, which does have PHP. Because the issue starts once it needs to use PHP to process the script, I surmise this might be it. I am investigating the possibility of a hosting error but at the moment will assume it works. (Updated: PHP issues resolved and left with code issue)

I've attached the code snippet appended to our Canvas JavaScript file, as well as a brief video of the error in question. Any help would be appreciated.

https://user-images.githubusercontent.com/121257531/209209172-dafebd0c-b3ee-49de-b68d-c49158a623de.mov

Code snippet:

$.getScript("https://my.uiw.edu/_dev/ally-api/js/convert.js", function () { console.log('convert.js loaded'); });

// Convert Ally PDF HTML to Canvas page $(window).on('load', function () { if (($.inArray('admin', ENV.current_user_roles) !== -1 || $.inArray('teacher', ENV.current_user_roles) !== -1) && document.location.href.indexOf('/files') > -1) { $.getScript("https://my.uiw.edu/_dev/ally-api/js/convert.js", function () { console.log('PDF to Canvas Page Ran'); }); } });

[specsoft4283]

Update: I have worked with our network team to fix some of the errors and view the logs, so now, the only error I receive is the one below.

[usu-access]

Thank you for reporting this issue - we will look into it, but it may take us a few weeks. I will report back if we can identity a solution.

[usu-access]

Our developer has reviewed the issue and he indicated that the issue was that for some reason the JavaScript was not finding the Dom element that we use titled "ef-item-row". I don't know why that would be working in our instance, but not in yours, but perhaps that is helpful in looking at it. At this point we have limited resources to do much work on this - but hope to revisit it and potentially spend some more time on it in the future. Sorry we can't be more helpful.