Viewing 6 replies - 16 through 21 (of 21 total)
  • Thread Starter webpart

    (@webpart)

    I need answers.
    Frankly, as IT professionals who also support customers, we are very annoyed by your support.
    We have to make decisions about continuing to use the Elementor plugin, which makes us sad because the plugin is magnificent but the support is awful.

    Plugin Support Richard from Elementor

    (@richardk23)

    Hello!

    Thank you for reaching out. I wanted to let you know that due to the regulations of the WordPress support forum, we can only offer support here for the Elementor Core (free) plugin and not for commercial licenses. This limits our support scope to comply with these guidelines.

    Unfortunately, we aren’t able to provide support for third-party themes or plugins.

    If you decide to upgrade to our Pro subscription, you’ll gain access to our dedicated support team who will be more than happy to assist you with any issues or questions you might have.

    If there’s anything else I can help you with, please feel free to let me know!

    Best regards,

    Thread Starter webpart

    (@webpart)

    That’s exactly what we’ve been trying to do for several months: That you provide support for a bug in the Elementor Free Plugin.

    Once again, the problem is as follows:
    The pages are not using the site settings or the theme settings, namely the line height.
    In Site settings – Typography, if the height of the line is not filled in you should, as was the case until a few months ago, use the theme settings.
    If I changed the height of the lines H1 … H6 (they weren’t filled in) and saved it, nothing changes.
    The problem persists after purging the minify cache and purging the cache of all pages.
    It also persists after uninstalling the plugin used for these caches (WP-Optimize).
    It also persists after uninstalling all plugins except Elementor.
    Finally, it persists when changing the Astra theme to another theme, namely Hello.

    Are you finally going to acknowledge the bug and fix it? Or not?

    Thread Starter webpart

    (@webpart)

    You’re not going to close the ticket again without resolution, are you?

    Thread Starter webpart

    (@webpart)

    You’re not going to close the ticket again without resolution, are you?

    Thread Starter webpart

    (@webpart)

    You’re not going to close the ticket again without resolution, are you?

    Aren’t you ashamed to have a problem that was reported several months ago unresolved and with no information provided to those who reported it?

Viewing 6 replies - 16 through 21 (of 21 total)
  • You must be logged in to reply to this topic.