WPIntell

Source evidence

Code cleanliness issues

Location Weather – WordPress Weather Forecast, Air Quality & Weather Widget · support · 2025-10-17T12:38:00+00:00

complaintsentiment
mediumseverity
0.66relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 18 rows with source links

5.6% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

17 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Volkmar Kantor resolved
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? This topic was modified 7 months, 1 week ago by Volkmar Kantor . 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! Same issue here. When will there be an update? Its urgent! Thanks. 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. 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.

Comments

4 shown
Pulak Ahmed 2025-10-20T08:47:00+00:00

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 2025-11-06T13:02:00+00:00

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

Pulak Ahmed 2025-11-07T09:14:00+00:00

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.

Pulak Ahmed 2025-11-20T12:00:00+00:00

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.