Support » Theme: Sydney » Another customizer error 2.05

  • Hi there,
    I found out that with the newest 2.04 and 2.05 Update there is another customizer error (apart from the Warning: array_merge()..

    When you use a header slider and use it “full width” instead of responsive, on the customizer on the tablet and mobile version you get a very stretched picture. This just occurs with the switch from 2.03 to 2.04 or 2.05 (I checked it on some test pages without plugins)

    This is connected to the error message because if it’s displayed, the picture of the header-slider in the customizer is too big on mobile and tablet.
    If I deactivate those error messages, it’s displayed normally.

    Warning: array_merge(): Expected parameter 1 to be an array, null given in C:\xampp\htdocs\backuptest\wp-content\themes\sydney\inc\customizer\options\upsell.php on line 42

    Warning: Creating default object from empty value in C:\xampp\htdocs\backuptest\wp-content\themes\sydney\inc\customizer\options\upsell.php on line 42

    • This topic was modified 1 month, 2 weeks ago by thalakus.
    • This topic was modified 1 month, 2 weeks ago by thalakus.
    • This topic was modified 1 month, 2 weeks ago by thalakus.
Viewing 3 replies - 1 through 3 (of 3 total)
  • @thalakus I wrote you a reply already on your other thread. Please avoid raising redundant question in the future.

    Thread Starter thalakus

    (@thalakus)

    @kharisblank thanks for your reply!
    In fact it’s an additional minor bug maybe, because the error message makes, that the Slider-Image is stretched in the customizer view if the error-messages can be shown. On my live-environment the error messages aren’t displayed on the top-section of the page and thus everything is shown normally 🙂

    Just for you to info, if there’s something needed to adapt 🙂

    Hi @thalakus,

    Thank you for additional information. And, really sorry for the trouble.

    Our development team confirmed that they can’t replicate the issue. Perhaps it is due to different environment. But, they can update the code to wipe out the PHP warnings. You’ll get it fixed itself once you update the theme in the future.

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