• The new update has broken the Customiser and messed up Site Origin Pagebuilder – this reverts to code on the backend. Fortunately the front end is fine. But Customiser gone is not good at all. I have temporarily rolled back to 5.5.3
    I believe the problem is possibly a compatibility issue with Rev Slider.

    Please can you check this out.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Hi! Rev Slider is a paid plugin, possibly you need to update it with the theme, or address it author to solve this.
    There are mentioned temporary solutions which should help to run the site meanwhile and also to understand what exactly the problem is:
    https://github.com/wpmarketingteam/WP5.6Marcomms/blob/master/Questions%20and%20Answers/6_jquery.md
    Scripts related errors you can find in a console in your browser:

    Using Your Browser to Diagnose JavaScript Errors

    Thread Starter bloohair

    (@bloohair)

    Both Rev slider, the theme and absolutely everything else is 100% up to date.

    I will of course, get onto Rev Slider – however, it may not be the problem!

    But I will look at the Javascript in my Browser to see if that will highlight the issue.
    Thanks for your help.

    Hello!
    I was just coming to report the same issue. I do not have Rev Slider, however, I do have Site Origin Page Builder installed.

    I will now test by disabling Site Origin Page Builder and see if this works.

    What I will say though is the issue with customizer is the items are there, but, the inline css is set to display: none.

    Update: from my personal tests, Page Builder by Site Origin does not appear to be at fault.

    Update #2: further testing revealed that by entering the troubleshooting mode (which disables all themes and plugins), the issue is fixed, and testing it with my theme enabled (whilst all plugins remained disabled) the issue is also fixed. Therefore, I can only assume it is one of the plugins … I’m still troubleshooting though.

    Update #3: for me, the issue was with the plugin gs testimonials lite.

    • This reply was modified 3 years, 11 months ago by kathrynmpu. Reason: updated with results of test
    • This reply was modified 3 years, 11 months ago by kathrynmpu.
    • This reply was modified 3 years, 11 months ago by kathrynmpu.
    Thread Starter bloohair

    (@bloohair)

    For me there are no customiser elements. Just the Widget elements with nothing inside.
    Could be Site Origin Pagebuilder, I’ve yet to disable plugins.

    Did you try to see a source of the problem in a browser’s console?
    It there is a script related issue, you can find and solve it with a plugin, read out more about:
    https://github.com/wpmarketingteam/WP5.6Marcomms/blob/master/Questions%20and%20Answers/6_jquery.md
    and then address a particular plugin author to make changes which are necessary for compatibility with WordPress 5.6.

    Thread Starter bloohair

    (@bloohair)

    Not yet, I have been tied up with other work that is more urgent. However, I have just had notice from Rev Slider and ESS Grid with an update to their plugins.
    Also SO Pagebuilder, so I’m thinking the problem may well get resolved now.

    Thread Starter bloohair

    (@bloohair)

    OK, I have now had a chance to update the plugins and then updated WP Core to 5.6.
    The problem is still there. I have checked console and there is a list of JQuery errors, example:-
    Uncaught TypeError: s.widget is not a function
    at wp-pointer.min.js:2
    at wp-pointer.min.js:2

    I am not using GS Testimonials lite like Kathryn above – so this looks like the latest WP update is affecting a few plugins – rather too many I’d say.

    I have a large number of websites to look after, I simply don’t have time to spend hours on end going through each site and identifying Plugins that this version of WordPress has messed up. I’ve never had this problem before – usually the updates go swimmingly. But I don’t see why I should be fixing someone else’s problems!

    That’s why I ask the question first.

    I don’t know which plugin is being flagged up by the console either… this is not good WordPress.

    Thread Starter bloohair

    (@bloohair)

    Ok, I did a guess and found the next offending plugin. Pagebuilder Premium. I have deactivated that and Customiser is fine and the page backends now resolve to Pagebuilder layouts. So I will get onto Site Origin.

    Doesn’t WordPress send out a notice to Plugin Developers to alert them of what they are about to do?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I have a large number of websites to look after, I simply don’t have time to spend hours on end going through each site and identifying Plugins that this version of WordPress has messed up. I’ve never had this problem before – usually the updates go swimmingly. But I don’t see why I should be fixing someone else’s problems!

    I hate to say this but … that’s the job of a web admin ?? Most of the time, the updates are just fine. But any time they’re not, we spend hours debugging things that we all feel devs should have gotten on sooner as it’s not like they aren’t aware updates are coming along.

    Doesn’t WordPress send out a notice to Plugin Developers to alert them of what they are about to do?

    We absolutely do. All plugin devs were emailed before Thanksgiving about this.

    Thread Starter bloohair

    (@bloohair)

    Ipstenu, I totally get that. And agree – most of the time the updates are just fine and I’m glad you do a lot of debugging. This is the first time I’ve had a WP Update that has caused problems. I just thought I’d let you guys know what’s been happening.
    I make the point of using the best plugins and keeping them up to date, but occasionally there will be a plugin that starts to get ‘un-cared for’ and it needs identifying. There seems to be quite a few this time, that’s all.

    Thread Starter bloohair

    (@bloohair)

    The interesting thing about this update is that whatever plugin that happens to be at fault – it’s the Customiser that gets broken.
    Is there anything you can do to make the Customiser more robust?

    Possibly your theme or some plugin has something to do with Customiser — like additional tabs etc and this is why it gets broken. All system is the ability to add new things by developers to extend default functionality, so, it looks like it’s no way to make it more robust and keep this flexibility at the same time.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘WordPress 5.6 Update Breaks Customiser’ is closed to new replies.