Page Builder 
Widgets Bundle 
SiteOrigin CSS 
Installer Origami and Page Builder – Page Builder widgets not editable
Hi Greg and Andrew,
(working on my dev site which is up line), I’m getting empty input fields in widgets built with PB, when I go to edit them. I cannot edit the text or image widgets within the PB edit interface – and often, the updating of a post or page will return it to the text editor, not the PB editor.
Setting my wp-config to —> define(‘WP_DEBUG’, true);, I get this error, presumably repeated down the page the same number of times that there are widgets on that page (it’s an extremely widget-heavy page – the only way I could figure out how to display Karen’s paintings in their full aspect ratio):
Notice: Undefined index: info in /data/…[[[identifying numbers and stuff]]]…/htdocs/html/dev/wp-content/themes/origami/extras/widgets/widgets.php on line 21
This issue is not just on the “Paintings” page, but on any post or page which I’d used the PB editor instead of just going with the text editor.
Prior to this, I’d been updating theme and plugins as they became available, however at this time, I’ve rolled back to a prior version of WP, and (I think,) a prior version of PB.
I see your answer oftentimes for people is to deactivate all other plugins and slowly reactivate them to see where a problem lies. This seems like such an objectionable practice since those plugins, deactivated, will render the site very differently than the original intent. I have a very hard time grasping this concept. Might as well just rebuild the entire site, and try not to use any plugins at all?
I hope you can help,
Thank you,
Mitch
This is our free support forum. Replies can take several days.
Need fast email support? Get SiteOrigin Premium
Replies
70This is a private message.
With WordPress 4.3, the constructor method for WP_Widget has been deprecated, and I don’t understand well enough to make any changes to (perhaps) …extras/widgets.php, and perhaps other files as well; or even if this may be the underlying issue.
I know I mentioned that I rolled back to prior themes, but (again,) I’m trying various things and I’m not even sure where I am now. I tried updating to WP 4.3 again and updating the PB plugin to try things out.
Thank you, looking forward to some assistance here,
Mitch
Opps! I meant to paste the link to this information here:
http://queryloop.com/get-your-widgets-ready-for-wp-4-3/
Hi Mitch
Thanks for the wait.
Our standard troubleshooting process is as follows:
1. Run all pending updates.
2. De-activate all plugins not made by SiteOrigin.
3. Point 2 only helps if at this point the issue is resolved. If the issue is resolved you then re-activate plugins one by one, each time checking the issue, in order to find the conflicting plugin.
Have you perhaps had a chance to run through a process like this?
This is a private message.
Thanks Mitch. Is everything working ok after you de-activate all non-SiteOrigin plugins? If so, the key step here is to one by one, re-activate your non-SiteOrigin plugins so we can figure out which one is causing the conflict.
(The error you originally posted is a notice. Not usually a problem, comes from an older version of Page Builder).
The other error you ran into:
the constructor method for WP_Widget has been deprecated
Has been resolved in a recent update of the Widgets Bundle. Running all pending updates from Dashboard > Updates should resolve that.
If you’d like, make a quick content backup from Tools > Export before proceeding. Never hurts.
This is a private message.
Thanks for the update. Are there pending updates at Dashboard > Updates?
Apologies for the ongoing hassle. I think if we could jump in and take a quick look around, that would be best. We’re off for the evening (GMT+2) but will be back tomorrow. Keen to get this fixed up!
Instructions to follow.
Would it be possible for you to create a temporary admin account for us so we can log in and take a look? You can create the account with the following email address:
[email protected]
Just navigate to Users > Add New in your WordPress admin. Enter siteorigin for the username and [email protected] for the email address. Make sure you’ve selected Administrator for the role and enabled the “Send Password” field so we receive the details.
Once we’re finished taking a look, you can delete this account. We’ll let you know when to do that.
This is a private message.
Oh dear, ok, there goes all of our easy options.
Thanks, I’ll jump in tomorrow and consult with Greg as I go.
Thanks for the huge effort you’ve made, it’s most appreciated. I’m sure we can get you back up and running tomorrow.
This is a private message.
This is a private message.
This is a private message.
Apologies for the delay. Are there perhaps a timeout on these new account creation links? This goes to 403.
This is a private message.
Please. Standing by.
This is a private message.
Sorry, didn’t arrive. Please, send the details them manually using the Private Reply checkbox bottom right.
This is a private message.
This is a private message.
This is a private message.
This is a private message.
This is a private message.
I’m struggling to get to the login form. Straight to 403. Do you have a security plugin installed? Is it geo-blocking?
This is a private message.
This is a private message.
This is a private message.
Sorry, I’m not sure. I haven’t worked much with WordFence. Yes, possible that IP limits are set there.
This is a private message.
This is a private message.
This is a private message.
This is a private message.
Totally. No need to remove. Mmm can you try de-activating WordFence and see if that helps?
I’ll try proxy in from the US and see if that matters.
This is a private message.
This is a private message.
This is a private message.
Cool, that’s fine. Let’s try with WordFence off.
Using Hola to proxy in from the US didn’t change the 403. Perhaps my IP is blocked.
Both Greg and myself get the same 403 page. To confirm, there is an index.php file present in the WordPress root of this site?
This is a private message.
This is a private message.
Any chance you’re using a plugin called: BulletProof Security ?
On a hosting level you could also try the suggestion the 403 page issues:
In your Account Manager, under Hosting Tools, click to .Reset File Permissions..
index.php is correct.
Are you hosted with Media Temple? If so, possible ideas:
https://mediatemple.net/community/products/dv/204644980/why-am-i-seeing-a-403-forbidden-error-message
This is a private message.
This is a private message.
This is a private message.
This is a private message.
NP.
Do you have an example page for the original issue?
“(working on my dev site which is up line), I’m getting empty input fields in widgets built with PB, when I go to edit them. I cannot edit the text or image widgets within the PB edit interface – and often, the updating of a post or page will return it to the text editor, not the PB editor.”
Working a bit late so please forgive me asking stuff you’ve painstakingly put into video.
This is a private message.
Checking. thanks
Ok so right now I can update your Page Builder test page. This is all about updating the live site without losing content so I’m a bit late to the party.
Is there any way we can roll the dev site back to before the issue? I need to work through the update to make sure I have a process of updating that doesn’t result in content shifting out of PB.
I can’t restore Paintings. Revisions go two months back. Seems it happened within that period?
So to confirm, for me, everything seems ok right now. But, there isn’t a way that I know of to restore the Paintings page without rolling the site/db back.
This is a private message.
When we upgrade the main site we’d still get one more shot at this. If it failed then yes, roll back and try again or re-build. What I’d try is to de-activate all non-SiteOrigin plugins before upgrading anything and then upgrade WordPress and Page Builder one after the other. There was a very crucial upgrade period around WP 3.9 – 4.0.
If we roll back dev I can test to see if my idea will matter/help.
It worked that I could edit it, however, a “nn” appears bot in editing mode, and when I preview it.
That would be something I’d recommend re-testing with all other plugins off. Let me know how that test goes. If it’s successful and the issue doesn’t happen again with all other plugins off then re-activating one by one should let you know where the issue is.
Thanks :)
This is a private message.
This is a private message.
Around the WordPress 4.0 period it was important that both WordPress and PB be upgraded together. It’s possible that was the problem here. I’ll take a look tomorrow at the version numbers you’re using on the main site and try figure out if that was the case.
Is the main site running the WordPress and plugin version numbers that the dev site was before the issue?
This is a private message.
This is a private message.
This is a private message.
Thanks. I’ve got the issue narrowed down to something in your child theme. If you switch back to the parent as I have now the problem resolves.
Hopefully you can troubleshoot from there. If you want to jump in manually you could pull everything out of the child theme except the style.css file, test and add files back one by one, testing each time.
This is a private message.
I got all the updates made to the live site, disabled that “magic quotes” function in the functions.php, and I was able to edit the Paintings page to remove the first two large paintings Karen wanted removed, and when I updated after my edit, the PB widgets all came back as they should, as opposed to leaving me at the text editing interface with a broken page.
In other words, I think the live site works now, all updated, and I can confidently let Karen help me with editing and not worry about things breaking.
Thanks again for all your help
P.S. for the benefit of others, I’ll publicly post this and presume the solution was an errant function in my child theme’s functions.php file.
Thanks for the update. Really glad to hear you were able to resolve and update everything.
All the best :)
Replies on this thread are closed.
Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.