Limited availability during the holidays

Another busy year is coming to its end, and an exciting year lies ahead. In order to get ready for a fresh new start, our team will spend a few days' rest during the winter holidays. Over the holiday break, we will have reduced staffing from December 20th, 2024, to January 5th, 2025, so please be patient if you do not receive a response as quickly as you normally would.

We send our warmest wishes for happiness, health, and success throughout the coming year. Thank you for your continued support, and may you have a peaceful and blessed Happy Holidays!

Okay
  Public Ticket #2281316
date and time of publishing
Closed

Comments

  • janfloor started the conversation

    I can't use the date and time of publishing.
    See attached

  • [deleted] replied

    Hello Janfloor,

    Thank you for getting in touch with us. My name is Attila and I'm happy to assist you today. I appreciate your patience while we've been working towards your ticket.

    Could you please set up a temporary WP login for us, so we can check on this? As I can see you have the latest release isntalled, so there is likely something interfering. But we will be able to tell more once we take a look at it. 

    You can leave the credentials here as a private reply. Thank you.

  •   janfloor replied privately
  • [deleted] replied

    Thank you. My colleagues and I will look into this to see what we can find, and get back to you shortly.

  • [deleted] replied

    Thank you for your patience.

    We've looked into this and it seems like there is another datepicker loaded there, instead of the default one.

    Most likely, another plugin uses a similar feature, and it's loading this datepicker everywhere. Its developersdid not make sure to only load it where it's needed, so it's applying itself everywhere, including LayerSlider's interface.

    Unfortunately, this can only be fixed if they make sure to not load it globally everywhere, but restrict it. Or if you keep that plugin disabled.

    You can find what item is causing this exactly by temporarily disabling plugins (and switching to a default theme if it's a theme method), and then enabling them back one by one.