I saw elsewhere in the forum where a user couldn’t edit at all in PB and was advised to do the plugin-conflict dance. I hate that dance. I have one widget w/Editor — and of course it’s the one whose content I absolutely need to edit — that goes to tiny spinning donut and won’t bring up content. Every other editor in every other widget on the very same post works perfectly. I can’t think this is a plugin issue and I haven’t installed one lately anyway. Can someone help me with this? I have been advised by my lawyer that this particular content needs to be changed! (Wouldn’t you know, anything associated with lawyers is always twice as much trouble!)
Can’t edit the content in one particular PageBuilder widget containing So Editor
Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Jhoughton1,
Sadly said dance rules out 99% of all issues. :(
Do you currently have Wordfence installed?
If you do:
This is likely a WordFence issue. The issue is that it’s initially very strict so things like the Learning Mode do definitely help in resolving issues like this one. However, if you want to “skip” the learning process and just use your widgets you can do so pretty easily. Go to the affected widget and open it up, don’t get “blocked” yet. Instead, open up another tab on WP AdminWordFenceLive Traffic and filter it by blocked traffic. Then make an adjustment to your button widget and you’ll get blocked. Go back to the Wordfence tab and press the whitelist param from FireWall button. This is 100% safe as the contents of the field are not at all close to what would be required for an XSS attack. (it’s really quite odd it would even suggest such a thing…).
Let me know if this helps.
If you don’t:
Would it be possible for you to create a temporary admin account for us so we can log in and take a look?
This is a private message.
This is a private message.
This is a private message.
Hi Jhoughton1,
Ah okay. To clarify, did you ensure to tick the “send user notification” checkbox? We haven’t received the email yet – you’ll know when. :(
BTW, Alex — I can remedy this situation by copying the text out of the post, pasting it into a new SO Editor widget in that same row, then deleting the one that won't edit. I've tried this and it works. I didn't update, though, because it would be interesting to know what the problem is and whether there's a solution should it arise again. If you're too busy to wrestle it to the ground, let me know and I'll do the quick fix and hope that this has been an anomaly, one of those things that just happens.
Hi Jhoughton1,
Sorry for the delay.
I’m very glad you didn’t link your site as you mistakenly posted that password publicly. Could you please change it and then reply back privately (emails are not private) with the password and a URL to your website?
This is a private message.
Hi Jhoughton1,
Thanks mate. Sadly that password isn’t working for me though. :( Can you please check it?
Dude, I'm so sorry. I failed to "update user" because the phone rang. Duh.
Sorry. It should work now.
Hi Jhoughton1,
ModSecurity is rejecting it for some reason with a 406 Not acceptable error code, which means it violated a rule.
This is a private message.
I don't fully understand the language you're using — remember, I'm a total civilian. Not sure what makes a community group, this is just a WP theme with minimum modifications as I understand it. I've seen my share of 404's,
but never a 406.
I deleted the whole row, then updated. I re-pasted the text, took out all formatting and links (in "text" mode, *nothing *showing but plain text) and updated. Uneditable.
When I "preview changes" I can come back and edit; it's only when I update that the widget editor becomes uneditable. What could be in there that's tripping things up?
Currently, I have re-pasted my text into the new row, done the edits that I needed, and updated. The post now looks like I want it to look, but that one widget editor is still malfunctioning. It's infuriating and let's face it, if it happens once, it can happen again, so I'd love to resolve the issue.
The only thing I didn't do is re-key the whole "Hidden Origins of
AngelFest" segment of the post that resides in the malfunctioning widget.
Given that a pure-text version, in a new row, still got stuck, I can't see the value in going through that step. But I'm a fast typist — if you think there is something to be learned from rewriting those paragraphs from scratch, I'll do it in the interests of science.
Thank you some more…
Hi Jhoughton1,
Yeah, you’re right; I wasn’t very clear.
A 406 error (in this case) means that ModSecurity has rejected something based on it violating a firewall rule. In my follow up post I stated that removing this text resolved the issue for me:
> Select groups from the community
That text is a part of the problematic SiteOrigin editor, when it was removed I was able to edit the widget without issue. To clarify, the rest of the sentence (to the first comma) is:
> Select groups from the community were individually introduced to the plan beginning in October of 2015
—
To clarify, this is more or less an issue with ModSecurity. For reference, ModSecurity is a “Web Application Firewall”. Something comparable would be Wordfence, although ModSecurity is run at the system level rather than as a plugin. I personally haven’t experienced any issues with it so I suspect your host has added a custom rule that is causing this issue.
Hopefully this makes more sense.
It does, thanks…somewhat.
Okay, you're saying that my hosting service has, in its infinite wisdom,
decided that the phrase "Select groups from the community" is toxic? That it shouldn't be allowed? That it means I'm a terrorist or something? Can I take this firewall down? I don't need anyone protecting me from saying certain things. What/where did you see indications that that particular phrase was the problem? And BTW, how were you able to get in and edit out that phrase, since lack of editability is the problem in the first place??
BTW, I don't ask "how'd you do that?" out of simple curiosity. Obviously,
should this happen again, I'd like to find the offending phrase — there's always another way to say something in our wonderful language, and it's probably easier just to rephrase than to do battle with my host over it.
Right?
I changed that sentence to begin, "Carefully selected groups from the stakeholder community were individually introduced…" and everything works fine. I'd still like to know how to locate the offending string.
Hi Jhoughton1,
No, no no no! Don’t take that way! It has nothing to do with the wording, and was likely an awful filter that was incorrectly introduced that flagged it for reasons unknown but I can assure you it’s not based on the contents of the actual sentence. If it was, it would have flagged something that made more sense.
You might be able to disable ModSecurity, I’m not sure. I would recommend contacting your host for advice. Please don’t attack them or suggest they’re censoring you, they’re not.
I made a copy of the exact markup of the post, removed each line until it got through, then I removed lines starting from the bottom until only that line was left over.
Okay, I thought you had a magic "bug finder" that revealed the source of the problem. I feel badly that you had to go through such a clunky process to find it. And no, I won't accuse anyone of censoring me. I see people in forums discussing the wisdom of turning off modsecurity and I will talk to my host about it (couldn't see any way on the cpanel to do so, besides I want to know what I'm giving up).
Alex, you have gone the extra mile for me…again. Thank you. If I'm ever
Down Under (and I'd like to visit some day) I'll look you up and buy you a beer or two!
Hi Jhoughton1,
Happy to help mate! :)
Good luck trying putting a proper end to that music festival! I read the article and the whole situation was handled very deceitfully. :(