Version 3.5.1.24 Incompatibility with Blocksy Theme Customizer

  • Hi,

    The latest Version (3.5.1.24) seems to have broken the Customiser on one of my websites

    After I updated Smart Slider 3 to 3.5.1.24 the customiser loaded a blank page (except for a visible \n pair of characters on the TLS of the page)

    Simply disabling the Smart Slider 3 plugin while carrying out theme customisations ( in a staging environment ) is a short term fix to the problem but is not a satisfactory long term solution.

    I’m using Version: 2.0.76 of the Blocksy Theme

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Laszlo

    (@laszloszalvak)

    Hi @mikepfive

    I installed the latest Blocksy theme and the Customizer loaded fine to me.

    Is it possible that you are a Smart Slider 3 Pro user? As there we had a bug earlier, that caused a similar issue, however on this forum we are not allowed to discuss topics about commercial products, as per the forum guidelines.

    So if that’s the case, then please get in touch with us directly over the ticket system:

    and we will help you resolving that issue there.

    Best regards,
    Laszlo.

    Thread Starter MikepFive

    (@mikepfive)

    Laszio,

    Thanks for your reply. Sorry not to get back to you sooner.

    I can confirm that the version installed on this site is the Free version – not the Pro version

    However, I can also report that following recent updates to the Blocksy Theme – along with updates to other plugins used by this website – I can no longer reproduce this problem !

    So the cause of the issue will remain a mystery I’m afraid.

    Sorry to waste your time

    Thanks – again – for your help

    Mike

    Plugin Support Laszlo

    (@laszloszalvak)

    Hi @mikepfive

    Thank you for your feedback.

    Meanwhile we managed to reproduce a similar problem that caused an error in the Customizer when certain plugins were installed, as those created a special condition that made us append our scripts to the wrong place.

    We found a possible solution, so if the problem returns feel free to contact us over the ticket system:

    refer to this ticket, and we will send you an updated installer. ( If anybody else also experienced such problems feel free to use the link above. )

    Note: we have just released a new version ( 3.5.1.25 ), but that doesn’t contain the fix as we needed to test the effects of this new modification, which would ultimately delay the release schedule. So this fix will be included only in the next release ( 3.5.1.26).

    Best regards,
    Laszlo.

    Thread Starter MikepFive

    (@mikepfive)

    Laszio,

    Many thanks for your speedy reply – and excellent support.

    It’s comforting to know that I wasn’t just imagining things !

    But – More Importantly! – it’s GREAT to have the assurance that if I see the problem again that I can get in touch via your support system. That’s simply Outstanding – and MUCH appriciated.

    I very much hope I don’t have any issues – but if I do, I’ll be in touch ?

    Best Regards

    Mike

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.