Source evidence

Problem with upgrade to 1.3.0

No unsafe-inline · support · 2026-03-12T20:21:00+00:00

complaintsentiment

mediumseverity

0.86relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 35 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

support

mp42 unresolved

Opportunity

Multisite portfolio governance for governing updates, reporting, and client-safe operations across many WordPress sites

Buyer: agencies, multisite operators, and maintenance teams

Wedge: surface multisite update risk, network drift, reporting gaps, and client-site exceptions

Proof Blocked card complete market

heuristic-v1

Summary: Problem with upgrade to 1.3.0: users show bugs, compatibility, setup pain that may indicate a product gap.

Affected feature: bugs

bugs compatibility setup

API

No unsafe-inline

200 active installs · 11.6K downloads · rating 100.0

content security policy csp multisite security unsafe-inline

2 shown

mp42 2026-03-13T09:35:00+00:00

FYI, the issue of the header not being set starts with the upgrade from 1.2.1 to 1.2.2

Giuseppe 2026-03-16T06:11:00+00:00

Please, send an URL to the page. Try to regenerate the trained estimators (run cluster scripts) and let me know if this solve the problem