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].
Hi
I was updating some content on my web site and all of a sudden I notices that all mu Sydney Theme Widges were missing, all i got was click on this link
Or Find the Missing Widgets!!!
Anyone have a clue to whats happened?
Help Pleae
Toby963
Hi
I was updating some content on my web site Homepage and all of a sudden I notices that all mu Sydney
Theme Widgets were missing, all i got was click on this link Or Find the Missing Widgets!!! Anyone have a clue to whats happened?
Help Please Toby963
Hi Toby
This is because of an incompatibility between Sydney and Page Builder 2.5. There’s a fairly simple fix for the issue. You can read more here – Thread: Sydney Theme all widgets have gone missing??
Hi Greg
Managed to find out about the problem last night and got it fixed, but now I have two Widgets asking me to update them, any idea when a fix will be released.
Thanks
Toby963
As far as I'm aware, aThemes fixed Sydney, so this shouldn't be an issue anymore. Are those 2 widgets part of Sydney? Then it might be best to get hold of aThemes to find out.
Hi Greg
I was in aThemes and found this “Found a temporary solution. The problem seems to be with the new version of SiteOrigin. Download WP Rollback and rollback to the previous version. This is now displaying the Sydney Widgets for me. Hopefully a permanent fix comes soon.”
So I did a RollBack of the
Page Builder By SiteOrigin
Siteorigin Widget Bundle
and everything came back up, so I thought that this was the problem.
However since then I have been looking what widgets I was using from the widget bundle and I received an email
from aThemes:
“Currently we’re having an issue with the latest Page Builder by Siteorigin update. Please do not update the plugin at this time or if you already did, use this plugin to go back to the previous version. We’ll have a solution shortly.”.
My apologies in thinking that it was SiteOrigin that was causing the problem, so I will now go back and see what is what
and hope that this never happens again late in the evening as it had my site in a mess and I spent hours getting it back to what it was.
Toby963