Cannot read property 'processSectionDelay' of undefined

Cannot read property 'processSectionDelay' of undefined

Sekar Govindaraj-mit -
Antal besvarelser: 5

Display the popup message Cannot read property 'processSectionDelay' of undefined. 

Please guide me how to solve the issues.

Gennemsnitsbedømmelse: -
I svar til Sekar Govindaraj

Re: Cannot read property 'processSectionDelay' of undefined

Leon Stringer-mit -
Core developers-ip assinga Particularly helpful Moodlers-ip assinga

What version of Moodle is this?

This problem may be caused by something affecting Moodle's JavaScript, e.g. an additional theme or plugin, code in Additional HTML, or files from an old Moodle version left behind after upgrade.

Enable debugging (Debug messages: DEVELOPER and Display debug messages: Yes, or set these in config.php) this should show more details with the error.

What theme are you using? If it's not Boost, try switching to Boost and see if the problem still occurs.

I svar til Leon Stringer

Re: Cannot read property 'processSectionDelay' of undefined

Sekar Govindaraj-mit -
We are using Moodle 3.9.1 version
Theme Lambda 3.9.
Additional HTML paste below the script
I svar til Sekar Govindaraj

Re: Cannot read property 'processSectionDelay' of undefined

Leon Stringer-mit -
Core developers-ip assinga Particularly helpful Moodlers-ip assinga

Try removing the Additional HTML (first take a copy of the setting as a backup) and see if this fixes the problem.

Try switching to Boost and see if this fixes the problem. If there is a problem with Lambda you will need to contact the vendor, there is little or no support for Lambda on these forums due to restrictions on its availability.

I svar til Sekar Govindaraj

Re: Cannot read property 'processSectionDelay' of undefined

Susana L.-mit -
I got this error after submitting a new path to filter_mathjaxloader on MathJax settings page.
I svar til Susana L.

Re: Cannot read property 'processSectionDelay' of undefined

Susana L.-mit -
More precisely after entering a path to MathJax v3.
Using a MathJax v2 (v2.7.8) path solved the issue...