I’ve tried to update a couple pages on my blog, including the landing page. When I “Update” and “View Page” none of the edits have stuck. Do you have a solution for this problem?
Edits to text are not being saved
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Kelly
Thanks for reaching out.
Please, send a link to a page concerned and let us know which test should be showing differently. We’ll inspect the page and page source and go from there.
Hi Andrew,
Thanks for your response. I’m trying to add text to my blog page, https://rememberingjanet.com/memories/, but every time I make the changes and press “Update” the page reverts to the pre-edited version. I’ve had my host provider help me search for an explanation and we’ve disabled and re-enabled all my plugins. The error seems to be coming from my Site Origin plugins, of which I utilize Page Builder, Widgets Bundle, and Ultimate Add-ons. I’ve gone so far as to disable those plugins, edit/add text to my page, and then try to save that version. Despite my not liking the loss of features to the page, even that version does not show on the front end.
If the above link to my page isn’t what you were asking to see, please let me know. I apologize now for my inexperience with the inner workings of technology. I always gravitate toward user-friendly plugins because I am not tech savvy…but appreciate people who are.
Thanks again,
Kelly
Hi Kelly, thanks for all of the feedback. Please, could you take a screenshot of the page as you’re editing it and upload it to imgur.com or Drive/Dropbox and send us the link.
Could you also confirm, is the page in question your assigned Blog/Posts page at Settings > Reading or not?
Hi Andrew.
The page is not the assigned page at Settings>Reading. But it also is not the only page I’m unable to get edits to work on. Based upon two pages I tried to edit, I’m thinking this is a problem throughout all the pages.
I’ve included many screen shots at the link below for your review. The “text” editing view was quite large. The last photo is of the “Visual” edit mode.
https://www.dropbox.com/sh/ckh7ob92hio0ha5/AAB4bZ7tPKV_i5SudrpyuC1-a?dl=0
Please let me know if there’s anything else you need.
Thanks so much,
Kelly
Hi Kelly
Thanks. It looks like there is a JavaScript error present that’s breaking other plugins that rely on JavaScript, like Page Builder. Please, try to establish a working baseline. Temporarily deactivate all plugins not authored by SiteOrigin. Does Page Builder load normally in that state? I’ve included the full test below.
—
This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Hello again, Andrew.
Page Builder is the plugin I’m having trouble with. I just found an article about the May breech that was addressed by Wordfence. At this point, I’m pretty certain this is my issue. Can you please advise as to how to proceed? I’m feeling like my site is compromised but I don’t know the extent of risk.
Thank you,
Kelly
Hi Kelly
Page Builder uses JavaScript. If your theme or another plugin produces a JavaScript error, any other plugins using JavaScript will be unable to function normally. Running a plugin conflict test as directed above is a normal and safe troubleshooting process. Temporarily deactivate all plugins except for those authored by SiteOrigin, does the issue resolve in that state? If not, also switch your theme to a default theme like Twenty-Twenty. The goal is to find a working baseline. Once you have, you can add your theme and other plugins back into the picture, checking for the issue after each activation. Please, refer back to my previous message for the full steps, this is a summary.
Wordfence found a security-related vulnerability in Page Builder, not a breach. The issue was immediately resolved by SiteOrigin.
Alternatively, if you’d prefer to diagnose the errors on the page directly, here is how https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis.
Thanks.
Thanks for the instructions, Andrew. I’m learning but still don’t understand the difference between a breach and a vulnerability. From my point of view, a hacker is uploading spam comments to my site, so I see that as a breach. I’m working with my host provider and will continue to troubleshoot. Will let you know how it goes.
There are no known cases of the security vulnerability in question being used in a hack. For the vulnerability in question to have been used, you would have to be logged in as the administrator and then click a malicious link sent to you by a hacker, presumably via email or a social media channel messaging platform.
Page Builder most likely isn’t loading on your page due to a JavaScript error. You can quickly confirm my suggestions by either checking the browser console for errors or running a plugin conflict test. The initial phase of a plugin conflict test can be completed in under two minutes. The initial phase is checking for a working baseline. Does Page Builder work normally when all non-SiteOrigin plugins are temporarily deactivated?
Plugin conflict test
In a previous message you let us know:
I’ve had my host provider help me search for an explanation and we’ve disabled and re-enabled all my plugins.
To confirm, the plugin conflict test is to seek a working baseline so the page must be tested with all non-SiteOrigin plugins deactivated. Deactivating and reactivating plugins on its own isn’t likely to change anything.
The error seems to be coming from my Site Origin plugins, of which I utilize Page Builder, Widgets Bundle, and Ultimate Add-ons.
Ultimate Addons is not authored by SiteOrigin. Only Page Builder by SiteOrigin and the Widgets Bundle must be enabled for the test.
Console
Alternatively, edit the page that’s showing the issue, open the console as seen here https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. If errors are present in red text, take a screenshot and send us the link.
Spam
Your comment forms are public. If spam comments aren’t getting picked up by Akismet you can perhaps check that Akismet is activated and that your Akismet key is inserted and saved correctly. It’s also possible that some spam will beat Akismet.
Thanks for continuing to help me, Andrew.
Here’s the link to what I found when peeking at the console:
https://1drv.ms/u/s!AlFxTy1mtNcrgcF4RpCIEJjiyw7ZAA?e=gHDW7n
With that, I learned that a plugin, Magee Shortcodes (MS), is causing the conflict with PageBuilder. After deactivating MS, I can edit again, but my site is moving in slow-mo. I’m trying to figure out how to correct that and also if I can do without MS all together.
The other info on the screenshot is of what I think may be the code that was put in by the spammers to try to get me to click on their comments. Fortunately, I moderate all comments and was careful not to click on the suspicious ones.
I am really glad for your help and appreciate any further advise.
Kelly
Hi Kelly
Glad to hear you’re making progress on both fronts.
The plugin in question is calling a JavaScript function that was removed from WordPress in version 5.5. You can use the plugin jQuery Migrate Helper to resolve the issue in the short term. If you have a moment, you could also try opening a support thread with the author of MS, send them a link to the console error screenshot, and ask if they can kindly resolve that when able.