This question about Using an extension: Answered
NatEditPlugin stopped to work properly
I have following settings:
Set SKIN = natedit, topicinteraction, metacomment, pattern
After upgrading plugins,
NatEditPlugin stopped to work properly.
I removed it, restarted Apache and install it again.
However problem persist:
--
MateuszKDzior - 09 Oct 2015
I noticed that I'm also receiving an error when I try to upload file: "can't parse json response from backend"
--
MateuszKDzior - 09 Oct 2015
I also noticed that "EditChapter" is unable to work properly as well:
--
MateuszKDzior - 09 Oct 2015
It seems that I have current JSON: sudo cpanm JSON
JSON is up to date. (2.90)
--
MateuszKDzior - 09 Oct 2015
Something went badly wrong in your upgrade process. I've just tested upgrading all extensions on both a 2.0.0 system and a 2.0.1 system.
NatEdit is still working. I don't have the other optional extensions installed. Not sure what could have gone wrong. See my response on
Question1697 too.
--
GeorgeClark - 09 Oct 2015
The editor is not initialized correctly. Something is blocking
jquery.natedit.js
from being loaded or it is not loaded. Could you check the page source and search for
jquery.natedit.js
? Any javascript error on the console?
--
MichaelDaum - 09 Oct 2015
Uncaught TypeError: Cannot read property 'FarbtasticEnabled' of null$.NatEditor.initGui @ jquery.natedit.js?version=4.01:1$.NatEditor @ jquery.natedit.js?version=4.01:1(anonymous function) @ jquery.natedit.js?version=4.01:2jQuery.extend.each @ jquery-2.1.3.js:1jQuery.fn.jQuery.each @ jquery-2.1.3.js:1$.fn.natedit @ jquery.natedit.js?version=4.01:2(anonymous function) @ jquery.natedit.js?version=4.01:2jQuery.extend.each @ jquery-2.1.3.js:1jQuery.fn.jQuery.each @ jquery-2.1.3.js:1$jQlq.run @ jquery.livequery.js?version=1.3.1:1$.extend.livequery @ jquery.livequery.js?version=1.3.1:1(anonymous function) @ jquery.natedit.js?version=4.01:2jQuery.Callbacks.fire @ jquery-2.1.3.js:2jQuery.Callbacks.self.fireWith @ jquery-2.1.3.js:2jQuery.extend.ready @ jquery-2.1.3.js:2completed @ jquery-2.1.3.js:2
--
MateuszKDzior - 09 Oct 2015
I have Farbtastic in {JQueryPlugin}{DefaultPlugins}.
Moreover, I have {JQueryPlugin}{Plugins}{Farbtastic}{Enabled} set to 1.
Seems very strange for me.
--
MateuszKDzior - 09 Oct 2015
In console I typed: foswiki.preferences
Object {PUBURLPATH: null, WEB: null, TOPIC: null, SYSTEMWEB: null, SCRIPTURL: null…}NatEditPlugin: nullPUBURL: nullPUBURLPATH: nullSCRIPTURL: nullSERVERTIME: nullSYSTEMWEB: nullTOPIC: nullWEB: nullWIKIUSERNAME: nullundefined: null__proto__: Object
--
MateuszKDzior - 09 Oct 2015
Okay. Please remove
topicinteraction, metacomment
from
SKIN
and try again. If the error still persists, then force-update
JQueryPlugin and
NatEditPlugin.
--
MichaelDaum - 10 Oct 2015
I'm not sure what do you mean by "force-update", but when I selected
JQueryPlugin in "review installed extensions", click on Upgrade button, save configuration and restarted Apache, my wiki started to work properly again. Thanks!
Should I always start with
JQueryPlugin re-installation again in such problems?
--
MateuszKDzior - 11 Oct 2015
So upgrading
JQueryPlugin fixed it. Good.
Yes,
JQueryPlugin is at the very heart of our javascript framework. So making sure it is up to date is important.
The recent updates to it are directly related to the strange
foswiki.preferences
object that you reported above: initializing it was achieved using insecure inline javascript before and now is done differently. All plugins, such as
NatEditPlugin or
SolrPlugin need updates. This is part of the work to establish a more restrictive Content Security Policy which will forbid any inline javascript and css.
--
MichaelDaum - 11 Oct 2015