Thank you for providing the updated information. I have also experienced the same. I have just reported this issue to the relevant Dev Team. I will update you as soon as I hear back.
I just got a detailed reply from Dev Team and copying below as-it-is, since it explains the issue and resolution in very much detail. Please consider followings:
There is an incompatibility, but it is not in our side. We can not solve this.
Let me share some debug info, so the client can request support from that other plugin author.
Basically, the problem is that both Views and that plugin are using a different version of CodeMirror (a script used for syntax highlighting). Views is using version 4.8.0 and that plugin is using version 3.19 (quite old). As a side-note, I feel that this plugin is not compliant with the CodeMirror license (it is not including the license declaration files, for example).
Some details:
- PageLines DMS Hooker plugin is en-queuing the CodeMirror script on every admin page although it is only using it on a single admin page, while Views is only en-queuing it on the pages it is using it.
- Views registers and en-queues the CodeMirror script with an appropriate handler name, while this plugin is using a “test?? name for it. It is also using the same “test?? handler for the CodeMirror style sheet.
In my opinion, the client should contact that plugin author and ask him to:
* Rename the CodeMirror script and style sheet handlers to something less generic than “test??, which sounds pretty bad IMHO.
* Make sure that he is only registering and en-queuing those assets on the admin page that uses them.
