I am helping my mother with her church’s site. She has this problem weekly and has a lengthy (takes her 30-45 min) work around. There must be an answer.
When I activate the siteOrigin widget bundle my page content turns to white text and I lose buttons. I have googled and read through this forum. I see that it is a common problem. I believe I have tried every solution I’ve found. So far I have:
– cleared cache
– installed/updated tinyMCE
– added line to wp-config
– changed theme from WP theme to siteOrigin theme and back to a different WP theme – none of the changed produced a working result
If I deactivate the widget bundle my page looks normal – but of course I cannot edit any of the widgets. As soon as I active the widget bundle I go back to white text and no buttons.
Please help. Losing my mind.
Thanks!
Meagan
Hi Meagan,
I’m sorry to hear about the issue you’re facing. I can assure you this isn’t a common problem. To clarify, does this issue affect solely the frontend or does this issue occur on the backened also?
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.
Hi Alex, I’m creating the account now. You will find the broken page in Pages->Home Old. The current Home is working correctly for now. She uses the same page each week to update the church’s bulletin. She likes using the page builder widgets as she is not super tech savvy and she likes the ease of arranging her columns and content.
You will see the Home Old page has content (backend) – that is white. But the buttons and page options are not appearing correctly. As soon as I deactivate the siteorigin widgets bundle the page appears correctly – but of course is not editable. I do not have this page in the menu at this time – I only kept it so you could see it.
She did have not tinyMCE installed. I added it as I was trying to figure out what was causing all the drama. It is currently disabled.
She did show me that she is Updating after every edit to each widget. They live in a very rural part of Illinois and her internet service goes up and down. She says she updates often to protect her work. I thought wordrpess autosaved for her – but I haven’t looked into that yet.
This exact error happens to her on average once a month. So 1 week out of every 4 bulletins.
Thanks for your help.
Meagan
Hi Meagan,
Thanks. There’s a PHP error present in the editor when editing the Home Old page. Can you please enable WP_DEBUG? This will allow for the error message to appear. To enable this setting, you’ll need to edit wp-config.php. If you need assistance with making this edit, I would reach out to your hosting provider for assistance.
To clarify, has the new homepage ever experienced this issue? Or is solely the Old Home page? Please note that I mean the literal WordPress page rather than the contents of the page itself.
Good Morning! I am not certain. The current home page was originally a draft she saved a few months ago. It was just the best starting place she had for this week since her working page broke. This happens to every home page she makes in time. Sometimes she can make a new one and use it for 2-3 weeks – but they always have this error in the end – then she does her work around. Her work around includes saving a draft copy of the Home page at some point when it is working correctly – so she can jump to it and edit it when her current page breaks. Then she has to update her menu and static start page to reflect the new change/direction.
Working on your edit request now.
Meagan
wp_debug enabled.
Meagan
Hi Meagan,
Thanks. The error message on old home page is:
(*** means that the directory name was changed)
This error message means that the page has exceeded the memory limit for that page. 268MB is massive so I don’t think that’s the direct cause. Is it okay if I run some tests to work out what’s going on? This may result in the actual breakage of the page (just that one page), is that okay?
Alex, I think this makes sense to me. There is no way the page is that massive based on its content — except she hits update a million times. If the page has hundreds of updates – it must be writing to the db? Right? And remembering ALL of the updates every single time. Still seems quite massive for that one page – but I’d be willing to bet her current home page is up there in size too. The size limit makes sense as to why she can use the same page for a week or two and then it breaks.
Feel free to break the old page. She will start editing for the new week Thursday or Friday.
Thanks, Meagan
Hi Meagan,
I’ve run a few tests and wasn’t able to identify why it was running out of memory (even after clearing the post data). What you said, regarding revisions and the like, could quite well be the case as you do have a very large number of revisions. Can you please try clearing the revisions for that page to see if that helps?
The easiest method would be with a plugin (although I don’t have any specific recommendations) but I would personally recommend setting WP_POST_REVISIONS. This will allow you to specify a limit of revisions to maintain per post to prevent cases where you have 300+ revisions. To set this setting you’ll need edit wp-config.php. If you need help with editing that file, I would reach out to your hosting provider for assistance.
Okay! I’m hoping we’ve fixed it. I’m going to bank on it being her number of revisions and NOT even anything to do with siteOrigin. It just seems activating and deactivating that plugin was what was making the error visible to me. I’ve limited her revisions to 5. She isn’t using the revisions – but pressing update is her only options since it is a live page. So I don’t think it matters if it is set to 1 or 10 – she just needs the most recent version. We are going to try this for a couple weeks.
I installed a duplicate page/post plugin and made a draft copy of her working page.
Thank you SO VERY MUCH for your help through this. I was banging my head on my desk :) You have been too kind.
I will update in a couple weeks so that you know she is working fine and enjoying the ease of her siteOrigin plugins.
Thank you!
Meagan