Relatively new to the WordPress scene, so I may have overlooked something fundamental to WordPress.
Symptom:
Can’t edit the contents of a SiteOrigin Editor widget after the content is ‘published’. When ‘edit’ is pushed, the editor window opens up, and a spinning “loading” circle spins where the content should appear.
The Pattern:
it appears that whenever Linux Terminal commands are written and published into the widget the symptoms are exhibited.
Ex. sudo apt-get update
The Workaround:
Copy all the content from a page preview, create a new Editor widget, and paste the content.
Tests:
Copying the widget itself does NOT work, resulting in the same symptoms.
Copying the content into a new page with no SiteOrigin widgets (so far) does NOT produce the same symptoms.
Copying the content into a new widget and removing the Linux commands (then publishing) does NOT produce the symptoms.
Any advice would be appreciated. Thanks.
Hi Nathan,
I’m not actually able to replicate this. I think the issue might be caused by an overzealous security module misinterpreting the json we store the page builder data in for each page. Can you please try replicating this on siteorigin.net instance?
Alex,
So I ran through a series of test on the siteorigin.net site.
Site URL: http://ow0i9q.siteorigin.net/
I created a new page called “Test Lockout”.
After running through some initial tests, I copied my page from my site directly and the editor locked me out. I narrowed down the instigating line to “sudo nano /usr/share/alsa/alsa.conf”. I didn’t narrow it down any further than that. Any editor with that line included became no longer editable. Everything else was fine.
I will have to take another look tomorrow, but right now I lean toward the file directory being the problem and not the commands i.e. sudo and nano.
So it appears that when the line “sudo nano /usr/share/alsa/alsa.conf” is broken out into separate elements the lockout doesn’t occur.
I tried all of the following in separate widgets, each not causing any issues:
/usr/share/alsa/alsa.conf
sudo nano
sudo nano /test/test.config
But, as soon as I put the entire line into a widget (this time typed it out instead of copying) the lockout symptom returned.
Hi Nathan,
Thanks for that. The issue is caused by Mod_Security. Basically, it’s flagging the string, and likely due to json being used. This filter in general doesn’t sound like a bad one so I would look to work around the issue rather than trying to get it disabled.
Ok. Thanks Alex.
For reference, here is another string that triggers the problem:
CREATE DATABASE IF NOT EXIST dejavu;