WPIntell

Source evidence

Warning Message

Logo Switcher · support · 2016-08-11T19:32:00+00:00

Logo Switcher plugin evidence original source source API
mixedsentiment
mediumseverity
0.78relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

3 / 19 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

16 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
sspens resolved
This was the message I received and couldn’t access my website or the dashboard. I had to deactivate the logo switcher plugin to get access to my dashboard and site. Warning: Cannot modify header information – headers already sent by (output started at /home/mindsmatterlv/public_html/wp-content/plugins/logo-switcher/init.php:1) in /home/mindsmatterlv/public_html/wp-includes/pluggable.php on line 1167 https://wordpress.org/plugins/logo-switcher/ Hi, I’ll look into this issue and keep you updated. I hope that’s okay. A website that doesn’t work isn’t acceptable, so I’ll do my best to solve this. Thanks for understanding, Leander Iversen Hi, I advise you download the revised code from here , then install it and see if you get the warning message. Let me know if it for some reason doesn’t work. All the best, Leander Iversen This error has now been fixed in version 1.1.2.

Comments

3 shown
Leander Iversen 2016-08-11T23:03:00+00:00

Hi, I’ll look into this issue and keep you updated. I hope that’s okay. A website that doesn’t work isn’t acceptable, so I’ll do my best to solve this. Thanks for understanding, Leander Iversen

Leander Iversen 2016-08-11T23:26:00+00:00

Hi, I advise you download the revised code from here , then install it and see if you get the warning message. Let me know if it for some reason doesn’t work. All the best, Leander Iversen

Leander Iversen 2016-08-14T13:23:00+00:00

This error has now been fixed in version 1.1.2.