Code cleanliness issues

  • Resolved Volkmar Kantor

    (@volkmar-kantor)


    4 months, 3 weeks ago

    I noticed you have the following statement in your location-weather-pro\includes\Blocks\build\index.css

    .components-panel__body.block-editor-block-inspector__advanced{display:none}

    This is very bad as it hiddes the visibility of the advanced settings on EVERY block.
    Can you please fix this fast.

    Also you are loading a lot of CSS and JS on every page, even if your blocks or shortcodes are not present on the page, which is a huge issue if one try to optimize the page for performance – could you optimize that?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Pulak Ahmed

    (@pulak00)

    4 months, 3 weeks ago

    Hi @volkmar-kantor,

    Thank you for bringing this to our attention.

    We sincerely apologize for the inconvenience caused. You are absolutely right — the CSS rule in location-weather-pro/includes/Blocks/build/index.css unintentionally affects the visibility of advanced settings for all Gutenberg blocks. We’ve identified the issue and will correct it in the next update so that it only targets our block’s settings panel.

    Regarding the loading of CSS and JS files, we completely understand your concern about performance optimization. We’re currently reviewing and improving our asset-loading process to ensure that scripts and styles are only enqueued when our block or shortcode is actually used on a page. This enhancement will be included in an upcoming release.

    We truly appreciate your valuable feedback. It helps us make the plugin more efficient and user-friendly.

    Thanks!

    morewebwork

    (@morewebwork)

    4 months ago

    Same issue here. When will there be an update?
    Its urgent! Thanks.

    Plugin Support Pulak Ahmed

    (@pulak00)

    4 months ago

    Hello @morewebwork,

    Hope you are doing great today!

    You would be happy to know that the issue has been addressed. We are very close to releasing the next plugin update, and the next update will resolve the issue.

    In the meantime, if you are interested in testing the beta version of the next plugin update, we suggest you open a support ticket here.

    Thank you.

    Plugin Support Pulak Ahmed

    (@pulak00)

    3 months, 3 weeks ago

    Hello @volkmar-kantor and @morewebwork,

    We have released a new version of the plugin that includes the necessary fix. We recommend updating to the latest version, and we hope this will resolve the issue permanently.

    Thank you.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.