• It seems the default CSS loaded when having HTMega enabled is messing with the layout of tables. Reason is located in paragraph “Blog Post CSS”. The usage of generic names for classes result in padding for the first row of each table on your site to be changed.

    .row-1 > [class*=”col”] {
    padding-left: 1px;
    padding-right: 1px; }

    The specific path to the CSS: wp-content/plugins/ht-mega-for-elementor/assets/css/htmega-widgets.css?ver=2.4.3

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Tarek Aziz

    (@tarekht)

    Hi there,

    Thanks for reaching out to us 🙂

    I have carefully reviewed your message and I am sorry for the inconvenience caused. It’s so kind of you to describe the issue in such a detailed manner.

    Rest assured, our plugin development team will investigate the plugin and address the issue as quickly as possible.

    During this period, I would kindly request your patience and cooperation.

    Wishing you a fantastic day ahead!

    Best regards,
    Tarek Aziz

    Thread Starter greatpages

    (@greatpages)

    Hello Tarek,

    appreciate your reply.
    A little detail I forgot to mention in my previous post:
    This issue only occurs when you disable the first line of the table to be the header, otherwise you probably wouldn’t notice.

    Best regards,
    Björn

    Plugin Contributor Tarek Aziz

    (@tarekht)

    Hello Björn,

    It was the least I could do 🙂

    Thanks for giving me the update as to when the issue exactly occurs.

    Our development team has already released an update by adding a bit of CSS code that should resolve the issue you are facing.

    Could you please try updating the plugin to its most recent version?

    If the issue persists after that, I kindly request that you open a ticket via our dedicated support website: https://wphtmega.com/contact/

    This will help us investigate the issue further and offer you an effective solution.

    Have a wonderful day!

    Kind regards,
    Tarek Aziz

    Thread Starter greatpages

    (@greatpages)

    No worries and no pressure.
    Issue on my side/site was already resolved with a little bit of CSS.
    Saw the update yesterday and also updated to the recent version. To be able to provide you with the correct feedback I commented out my code and rolled back to the previous state.
    And what can I say? It seems the issue is resolved. 🙂
    I’m really impressed with the effort you and the team put into this. Really appreciated! Please make sure to let them know and pass on my thanks to each of them.

    Feel free to close the ticket.
    Wish you all the best,

    -Björn

    Plugin Contributor Tarek Aziz

    (@tarekht)

    Hey Björn,

    I trust you are doing great!

    I am delighted to hear that you already resolved the issue using a bit of CSS.

    Thank you very much for taking the time to share your valuable feedback.

    We always strive to take every issue, feature request, and feedback seriously, and the issue you encountered was considered a top priority. Our team took immediate action to address the issue as quickly as possible 🙂

    All your kind words are truly appreciated and I will make sure to pass on your comment to the developer who worked diligently on this. It will undoubtedly encourage him a lot.

    Wishing you a fantastic weekend ahead! 👍

    All the best,
    Tarek Aziz

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