WPIntell

Source evidence

PHP Warning

Meerkat Markdown for AI Visibility · support · 2026-06-21T10:54:00+00:00

complaintsentiment
mediumseverity
0.75relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

7 / 29 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Frank unresolved
PHP Warning (Attempt to read property “childNodes” on null) in simple-html-to-markdown.php Hi there, I noticed a PHP warning in my server logs caused by the Meerkat Markdown for AI Visibility plugin. The error occurs under PHP 8.5.x when the HTML-to-Markdown parser encounters an unexpected or empty node. Error Log: Plaintext [proxy_fcgi:error] AH01071: Got error 'PHP message: PHP Warning: Attempt to read property "childNodes" on null in /wp-content/plugins/meerkat-markdown-for-ai-visibility/includes/simple-html-to-markdown.php on line 50; PHP message: PHP Warning: foreach() argument must be of type array|object, null given in /wp-content/plugins/meerkat-markdown-for-ai-visibility/includes/simple-html-to-markdown.php on line 50' Cause: In includes/simple-html-to-markdown.php , the method process_nodes( $node ) receives $node which can sometimes be null (either on the initial call or during recursion). Line 50 tries to access $node->childNodes directly without validating the variable first. Suggested Fix: Adding a simple guard clause at the very beginning of the process_nodes function resolves the issue cleanly: PHP private function process_nodes( $node ) { if ( ! $node ) { return ''; } $markdown = ''; foreach ( $node->childNodes as $child ) { // ... rest of the code Could you please include a null-check in the next plugin update to prevent these warnings from flooding the logs? Thank you for your great work! Best regards, Frank

Comments

0 shown

No comments were stored for this source.