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].
My site lists SiteOrigin Widget Features Widget as missing even though in the plugins – SiteOrigin Widgets Bundle – Manage Widgets – Features is Active. How do I restore this widget? It will not save edits to the existing widget content.
Hi Erin
I’m not quite sure why that would be the case.
Are you able to insert a new SiteOrigin Features widget on a new page? Does the issue persist if you temporarily deactivate all plugins not authored by SiteOrigin?
It is not listed anymore in the Add Widget options so I can’t replace it with a new Features widget.
I deactivated each plugin and cleared the site’s cache. The widget is still called “Missing Widget”.
Thanks for the update.
Please, could you send us a screenshot of the Features widget enabled at PluginsSiteOrigin Widgets. You can upload it to imgur.com and send the link.
I uploaded 4 photos – 1 showing the plugin enabled, 1 with the Features Widget enabled, 1 with the Features Widget named “Missing Widget” on the page, and 1 with the options I have for adding a new widget that doesn’t have the Features Widget as an option.
https://imgur.com/a/yf29n16
What happens when you search for the Features widget? When adding a new widget there is a search form at the top left of the modal window.
Can you also confirm, when doing the plugin conflict test, did you deactivate all non-SiteOrigin plugins in one go?
When I search Features nothing pops up / the area it would be listed is blank.
Yes, I turned off all plugs except the SiteOrigin ones (Page Builder by SiteOrigin and SiteOrigin Widgets Bundle) and the cache plugin so that I could still cache the site. I don’t think the cache plugin would be what’s causing the issue because it wasn’t installed when the widget stopped working.
Please, try clearing your caching plugin and then deactivate it. That should be done before all non-SiteOrigin SiteOrigin plugins are deactivated. In general, I’d leave caching completely deactivated during troubleshooting.
With all non-SiteOrigin plugins deactivated, including your caching plugin, if the issue persists, try temporarily switching to Twenty Nineteen or any default WordPress theme.
If the above isn’t helpful, deactivate and delete the Widgets Bundle then re-install the Widgets Bundle from PluginsAdd New.
Okay, I cleared the cache and deactivated all the non-SiteOrigin plugins. The widget was still missing so I reactivated all plugins, deleted the Widgets Bundle, cleared the cache, installed it again, and Features is missing. I’m afraid of switching the theme so I did not do that step.
All plugins deactivated, except for the Widgets Bundle and a default theme activated would be the ultimate baseline we can easily achieve in testing. This is quite a common troubleshooting process.
You can try checking for JavaScript errors in the browser on the pages that the widgets show as missing. Here is how: https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis.
You can try checking for PHP errors, you could use Query Monitor to do that: https://wordpress.org/plugins/query-monitor/.
Please, send a link to a page concerned and we’ll take a look.
I tried to use the Javascript console but it doesn’t open with the suggested keyboard shortcut. I also installed that Query Monitor plugin and the PHP errors weren’t showing any related to the plugin or Features widget.
I would send the link but the page isn’t live yet. The issue is on the backend trying to edit the widget and getting the new content to save. My client is trying to edit it as it just has placeholder text in the Features widget right now.
You can open the developer console by right-clicking on your screen > Inspect or Inspect Element. The link I sent previously has instructions for all major browsers if you scroll down a little.
Please, temporarily publish the page so we can take a look. Or alternatively, publish with a password and send us the password, thanks.
https://www.wpbeginner.com/beginners-guide/how-to-password-protect-posts-in-wordpress/
URL: https://ua178.org/vision-for-the-future/
PW: SiteOrigin1
Thanks!
Thanks. Nothing jumps out at me. What theme is this theme based on?
I believe it is custom. It says it’s called UA178.
The other themes installed are Twenty Nineteen and Twenty Seventeen.
I take it you’ve tried deactivating and reactivating the Features widget at Plugins > SiteOrigin Widgets?
If that isn’t helpful. Please, check the page with the issue and check for console errors: https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. Scroll down and find the instructions for your browser or just right click > Inspect.
If that doesn’t help, I recommend taking a backup and then temporarily switching to Twenty Nineteen and seeing if the issue persists. It’ll be helpful to rule out the theme as being an issue. If you don’t have an existing method to make a backup you could use a plugin like Duplicator. There won’t be any issues switching themes though.
Nothing is working and when I inspect it from the front end, everything looks fine. I ended up building the Features widget using the Icon, Headline, and Editor widgets. It has nearly the same look and is working fine.
Thank you so much for all your help, Andrew! I appreciate all your suggestions and patience!
Sorry, we couldn’t resolve the issue, at least for the time being. I’m glad to hear you’ve found a workaround. I’ve asked the team about the problem you’re facing. We haven’t ever had this come up but if I can think of anything further to try, I’ll be sure to let you know.
That’s okay, it is a very weird issue. Thanks!
Really is, phew. Thanks for your understanding.
Hi Erin, I chatted with Alex here at SiteOrigin. We’ve seen this happen once before, in that case, the theme in question was intentionally removing the Features widget. If you ever want to come back to this, it’ll be worth doing the theme test we discussed earlier in the thread.