This is happening on the same JMS platform as in this ticket about Store Locator.

Site: Joomla 3.4.1, JMS 1.3.39.

I have just imported an existing site into JMS and now have some errors.

It looks like the symlinks may not be working properly.

Here are the errors I am getting when opening a module based on the Accordion Menu module from within the slave site admin area Module Manager.

This first group of errors are above the Menu Manager header bar, the second group are below the Save buttons.



How do I fix this?

(Note: Immediately after import, I needed to add the GD extension to my version of PHP.)

Your current JMS version 1.3.39 needs to be updated with latest JMS 1.3.47 to be compatible with the J3.4.1

Concerning the problem of links that is wrong, I suggest that you report that to the author of the accordeon extension.
In general this is due to the fact that the extension recompute the path of a file using the "realpath" function that return the physical path and not the relative path to the website "document root".
So the fix should be performed in the "accordeon" extension

Amazing that this thread is more than 4 years old! At any rate, I'm happy to report that I have an update to this topic. The issue came up again while upgrading my JMS from J3.6.5 to 3.9.10.

I contacted the developer of the Nextend Accordion extension and gave them access to the development version of my JMS and they did indeed find that a code modification was required to resolve the issue regarding the paths their extension was attempting to use to acccess their javascript/jquery libraries.

They said they've incorporated the the altered code and have just released a new version of the Nextend Accordion extension, version 9.3.15 which fixes the problem.

They thanked me for alerting them to the problem and giving them access to debug. Thanks for pointing out the issue, Edwin. I told them you had said that was the cause.

Glad to see that this forum that is a kind of knowledge base of the issues and potential solutions has helped fixing definitively this issue.
Thank you Azurelink for your contribution.