Installation

Unable to enlarge image after upgrading to 2.17

Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -
Number of replies: 12
Upgraded webwork to 2.17.
Then while trying to enlarge an image as part of an existing question in a course nothing happens.
While inspecting the webpage received this error

Uncaught TypeError: Illegal invocation

    at Object.findOne (selector-engine.js:24:44)

    at Hi._showElement (modal.js:217:38)

    at modal.js:143:35

    at _ (index.js:251:5)

    at backdrop.js:54:7

    at _ (index.js:251:5)

    at b (index.js:257:5)

    at bi._emulateAnimation (backdrop.js:126:5)

    at bi.show (backdrop.js:53:10)

    at Hi._showBackdrop (modal.js:309:20)


Any suggestions?

In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Danny Glin -
Did you run `npm ci` in both /opt/webwork/webwork2/htdocs and /opt/webwork/pg/htdocs and then restart apache?
In reply to Danny Glin

Re: Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -

Yes it ran with no issues 

In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Danny Glin -

Does this happen with all images, or is it specific to one image?  If it only applies to certain images can you provide an example of where it happens?

In reply to Danny Glin

Re: Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -

We are only using graphs and they cannot be enlarged but any graphical representation in question or solution could not be enlarged

In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Glenn Rice -
Are these problems from the OPL (added via the Library Browser)?  If so which problems are they?

If these are local problems, please provide the source for one of these problems.

In reply to Glenn Rice

Re: Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -

This file is part of the local folder.

Attached is the sample pg file

In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -

Clarifiction on the above issue

The issue happens for all images including the ones in library

After clicking the whole page  becomes gray and the page is stuck and the only way to return is by pressing back button.

Attached is a screenshot from a library file

Attachment pic.png
In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Glenn Rice -

The problem you posted doesn't seem to cause any issues.  I recommend that you check that you have run "npm ci" in both the /opt/webwork/webwork2/htdocs and /opt/webwork/pg/htdocs location, and then restart apache2.  Then try again.

If that still doesn't work, then we will need more information.  Like what browser are you testing this on?  The console log error that you posted doesn't give any real information, and does not seem to be complete.  Does it tell you what file the error is coming from or give a backtrace?

Also what does running "git status" report when executed in both the /opt/webwork/webwork2 and /opt/webwork/pg locations?

In reply to Glenn Rice

Re: Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -

Yes i have run npm ci without any issues and even after restart the issue still exists.

The browser im using is chrome.

This is the entire webpage error im getting. This is the only entry in apache log when clicking on the image.

98.210.0.167 - - [08/Aug/2023:20:55:28 -0700] "POST /webwork2/instructorXMLHandler HTTP/1.1" 200 384 "https://webwork2.asu.edu/webwork2/Tracogna_TEST2_Spring_2023/Undefined_Set/1/?sourceFilePath=Local/270/setLimitsRates1_5Graphs/ur_lr_1-5_1.pg&effectiveUser=ajayavel&editMode=savedFile&ticket=ST-1379126-S5t3XAV9W-ZLMe-BR6RknHJ3aKY-sso-cas-77d5dd55fd-p4dkq" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"

::1 - - [08/Aug/2023:20:55:36 -0700] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 mod_apreq2-20090110/2.8.0 mod_perl/2.0.12 Perl/v5.34.0 (internal dummy connection)"

98.36.163.209 - - [08/Aug/2023:20:56:27 -0700] "-" 408 6598 "-" "-"

174.195.116.44 - - [08/Aug/2023:20:56:49 -0700] "-" 408 6598 "-" "-"

46.161.194.168 - - [08/Aug/2023:21:01:44 -0700] "GET / HTTP/1.1" 302 482 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"

 

In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Glenn Rice -

The apache log isn't really useful for this.  This is a javascript issue.  So what I need is the browser console log and possible debugging information.  That is what you included in your first post, but as I said, what you included in your first post is not complete.  The files referenced are all bootstrap files (selector-engine.js, modal.js, etc.).  None of the files are webwork2 files.  So the log is not showing the webwork2 file in which the issue is originating.  I expect to see something about imageview.js.

At this point I still don't have anything useful to diagnose what is causing the problem for you.

In reply to Glenn Rice

Re: Unable to enlarge image after upgrading to 2.17

by Aakash Jayavel -
Im unable to trace any source document.
Attached are the source file of the page.
Is any folder missing?
Attachment Htdocs.PNG
In reply to Aakash Jayavel

Re: Unable to enlarge image after upgrading to 2.17

by Glenn Rice -

The files look like they are all there.

Could you try another browser or use the same browser but with a clean profile?  I suspect that you have some browser add on that is causing an issue.