Source evidence

No Data Displayed

wp-forecast · support · 2024-02-25T10:51:00+00:00

wp-forecast plugin evidence original source source API

mixedsentiment

mediumseverity

0.85relevance

7replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

4 / 27 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

23 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

retrojimmy resolved

Plugin installed, activated and version 9.2 running on WP 6.4.3 No errors when doing API tests and all fields populated correctly. No data shown and just placeholder images along with field names. Please advise as I am not getting any error codes or messages from the plugin. View post on imgur.com Hello Jimmy, can you please post the settings you used, so I can try to find out what the problem is. Thanks. I just saw you were unsatisfied with my time of response to your message. I am sorry, I have to work during the week and only can look after this when I have sparetime. Hi Tuxlog, i have same problem. No data shown and just placeholder images along with field names. Even after dissable all plugins and keep wp-forecast activ. Also not possible to change to fsokopen, strem, curl. Message if i open by widget: Fehlermeldung des Wetterproviders: No OpenWeathermap data available. Thanks alex Hello Alex, can you post your config please (of course not the API key, if you use one), so I can try to rebuild the problem. Thanks. Hi, i send you all Details, Config, Urls and PHP to your email. Alex Thanks, I just sent you an email, it seems you have an invalid location code. Please select the location again and save it. It turns out that the wrong location code was the problem. By selecting a correct location using the small magnifying class the problem was solved.

Commercial Context

Opportunity

agency visual QA and update safety

Widget visual QA and update safety for preventing client-site regressions before updates or edits go live

Buyer: site builders and agencies

Wedge: detect widget layout regressions, widget breakage, and client-visible update issues

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: No Data Displayed: users show bugs, compatibility, missing feature pain that may indicate a product gap.

Evidence quote: No Data Displayed Plugin installed, activated and version 9.2 running on WP 6.4.3 No errors when doing API tests and all fields populated correctly.

Affected feature: email

bugs compatibility missing feature support

Plugin

API

wp-forecast

5.0K active installs · 434.6K downloads · rating 82.0

forecast open-meteo openweathermap weather widget

Comments

7 shown

tuxlog 2024-03-02T06:42:00+00:00

Hello Jimmy, can you please post the settings you used, so I can try to find out what the problem is. Thanks.

tuxlog 2024-03-02T06:47:00+00:00

I just saw you were unsatisfied with my time of response to your message. I am sorry, I have to work during the week and only can look after this when I have sparetime.

johnny1885 2024-03-07T13:03:00+00:00

Hi Tuxlog, i have same problem. No data shown and just placeholder images along with field names. Even after dissable all plugins and keep wp-forecast activ. Also not possible to change to fsokopen, strem, curl. Message if i open by widget: Fehlermeldung des Wetterproviders: No OpenWeathermap data available. Thanks alex

tuxlog 2024-03-07T14:06:00+00:00

Hello Alex, can you post your config please (of course not the API key, if you use one), so I can try to rebuild the problem. Thanks.

johnny1885 2024-03-07T15:09:00+00:00

Hi, i send you all Details, Config, Urls and PHP to your email. Alex

tuxlog 2024-03-07T16:39:00+00:00

Thanks, I just sent you an email, it seems you have an invalid location code. Please select the location again and save it.

tuxlog 2024-03-08T16:37:00+00:00

It turns out that the wrong location code was the problem. By selecting a correct location using the small magnifying class the problem was solved.