Forum Replies Created

Viewing 15 replies - 1 through 15 (of 300 total)
  • Plugin Support olektidio

    (@olektidio)

    Thank you for the update. Would you mind sending the screenshot of the error to our support for further assistance? Also, you can try to reinstall the app in the meantime, thank you!

    Plugin Support olektidio

    (@olektidio)

    Hello, I’m sorry to hear this! Please share the screenshot of the error and the exact device you’re using, brand and model.

    It may help us verify the case. Thank you for the cooperation!

    Plugin Support olektidio

    (@olektidio)

    Hi there!

    I’m sorry to hear for the inconvenience you faced. It can be that you are logged in to the different project than the one installed on your website.

    Please reach out to our Support at [email protected] with your website URL and the Public Key of the project you can see this error for, it can be found here: https://www.tidio.com/panel/settings/developer/developerData

    We’ll be happy to help!

    Plugin Support olektidio

    (@olektidio)

    Thank you so much for the 5-star review!

    Plugin Support olektidio

    (@olektidio)

    Hi there,

    We’re really sorry to hear about your experience.

    What you described is highly unusual. Tidio loads asynchronously, meaning it runs independently from the rest of your website’s core elements specifically to avoid disruptions or site crashes.

    We’ve reached out to you a couple of times to better understand what happened, but we haven’t heard back yet. Please check your inbox (and spam folder just in case), or feel free to contact us directly at [email protected].

    We’d truly appreciate the opportunity to investigate this properly and help you get the best out of Tidio.

    We’re here to help.

    Plugin Support olektidio

    (@olektidio)

    Hi Ben!

    Thank you so much for your kind words and for taking the time to share your experience! We’re truly delighted to hear that the integration process was smooth and successful for you.

    We’re grateful for your recommendation and for the opportunity to work with you. If there’s ever anything more we can do, don’t hesitate to reach out. Here’s to more seamless collaborations ahead!

    Plugin Support olektidio

    (@olektidio)

    Hi Ben!

    Thanks for your response.

    Glad we could help! Do let us know if you have any other questions.

    PS.

    We would really appreciate it if you could rate our app or your experience with our Support Team. Here is a direct link: click here

    It should take you just a minute, but it really helps us in development! Thank you for your time.

    Plugin Support olektidio

    (@olektidio)

    Hi Ben,

    Just a quick update – the change has landed in version 7.0.0, which is available now.

    We’ve:

    – Replaced PHP_INT_MAX with a default priority of 1000
    – Added a tidio_widget_footer_priority filter so the priority can be customized if needed

    This should allow your buffering system (and other consent/caching tools) to properly intercept and rewrite the script.

    Please let us know if everything works as expected on your side.

    Best regards

    Plugin Support olektidio

    (@olektidio)

    Hi Ben,

    Thanks for the detailed clarification.

    We’re planning to change the priority from PHP_INT_MAX to 1000 for consistency with our sync loading approach. Additionally, we’ll expose a filter so users can adjust the priority if needed:

    $priority = apply_filters(‘tidio_widget_footer_priority’, 1000);
    add_action(‘wp_footer’, [$this, ‘enqueueScriptsAsync’], $priority);

    This way, the default behavior becomes compatible with output buffering, while edge-case users can restore the old behavior if necessary.

    Does 1000 work for your buffering system, or would you recommend a lower value? Also, if there’s a priority range that consent/caching plugins typically hook at, we’d like to stay below that threshold.

    Looking forward to your feedback.

    Best regards,

    Plugin Support olektidio

    (@olektidio)

    Hi,

    Thanks for reaching out.

    The PHP_INT_MAX priority is intentional. Our script is injected at the very end of the footer to avoid unintended interactions with other plugins and to ensure it does not impact the loading sequence of earlier assets. In practice, this has helped us prevent race conditions and conflicts in complex environments.

    That said, we definitely want to ensure compatibility with consent management tools.

    To better understand the issue, could you clarify:

    1. Are you attempting to modify the script via the script_loader_tag filter?
    2. Is the problem specifically with Borlabs Cookie, or does it affect other consent tools as well?
    3. Are you trying to block execution until consent is granted, or only to rewrite the <script> tag?
    4. Are you relying on WordPress’ script enqueue system, or expecting interception of a raw <script> tag?
    5. Would hooking earlier in wp_footer (e.g., priority 20 or 100) resolve your issue, or do you require full control over the tag output?

    Depending on the exact integration requirement, we may be able to expose a filter or adjust our loading strategy without compromising the stability guarantees we currently rely on.

    Looking forward to your clarification.

    Best regards,

      Plugin Support olektidio

      (@olektidio)

      Hi there!

      While Turkish is on the list of Lyro supported languages, it will not work for product recommendations. For now they’re avaialable only in English. We hope to extend the list of languages supported soon!

      Plugin Support olektidio

      (@olektidio)

      Hello there!

      I’m sorry to hear about the issue you’re experiencing. Please note I don’t see a plugin installation or the JavaScript code for Tidio on your website. Confirm the method you chose, as this may help us verify the case .

      Plugin Support olektidio

      (@olektidio)

      Hi there!

      When you have an active project already, you may add knowledge to Lyro from the knowledge base section in the panel. You can provide it from URL, via file, manullay or with Zendesk article.

      Make sure to click on the blue activation button in the top right corner of this section.

      In case of any issues or errors, please reach out at [email protected]. The Team will be there to help!

      Plugin Support olektidio

      (@olektidio)

      Hi again!

      No worries, we’re here to help. Please add the “disable text input” after the trigger. This way, as long as this scenario doesn’t end, your visitors won’t be able to send a chat message.

      If you need assistance with the setup, please reach out to us at [email protected], the Team will be able to provide you with some guidance!

      Plugin Support olektidio

      (@olektidio)

      Hello there!

      While there is no option to disable the chat feature itself, you may add the disable text input node to your flow, straight after the trigger. Please make sure to create a loop within the scenario, as the input is allowed back once the scenario ends.

      Here you can read more about that workaround: https://help.tidio.com/hc/en-us/articles/5465426393756-Disable-Text-Input

    Viewing 15 replies - 1 through 15 (of 300 total)