Plugin Conflict – Causes W3C Validation Fatal Error

  • Ramiz Theba

    (@ramizmyadvice)


    7 months, 1 week ago

    Plugin: Lead Forensics
    Issue Type: Compatibility / Validation Error
    Website: https://myadvice.com
    Staging URL (plugin disabled): https://stg-myadvicecom-stage.kinsta.cloud/Description of the Issue:

    We’ve identified that the Lead Forensics plugin is causing a fatal validation error when analyzing our site using the W3C Validator.

    Error Message Displayed:

    Fatal Error: Cannot recover after last error. Any further errors will be ignored.

    This happens only when the Lead Forensics plugin is active.
    Disabling it immediately resolves the issue.

    Steps to Reproduce:

    1. Activate the Lead Forensics plugin.
    2. Visit the live site and copy the page URL.
    3. Validate the URL using the W3C Markup Validator at https://validator.w3.org/nu/.
    4. Observe that the validator halts with a Fatal Error message.
    5. Deactivate the plugin and recheck – the issue no longer appears.

    Expected Result:
    The plugin should not interfere with or break W3C validation.
    Actual Result:
    Validation fails with a fatal error when the plugin is active.

    Request:
    Please investigate this conflict — it seems the plugin output or injected script might be producing invalid or malformed HTML that prevents the validator from parsing the document correctly.
    Any guidance, fix, or patch would be highly appreciated.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Ramiz Theba

    (@ramizmyadvice)

    7 months ago

    I wanted to follow up on the ongoing ticket regarding the validation error issue caused by the Lead Forensics plugin on our website.

    Plugin: Lead Forensics
    Issue Type: Compatibility / Validation Error
    Live Website: https://myadvice.com
    Staging (Plugin Disabled): https://stg-myadvicecom-stage.kinsta.cloud/

    As shared earlier, the plugin appears to generate invalid or malformed markup that results in a fatal W3C validation error. Summary of Findings:

    • Validation works correctly when the plugin is disabled:
      🔗 Validation (Plugin Disabled)
    • Validation fails with a Fatal Error when the plugin is enabled:
      🔗 Validation (Plugin Enabled)
    • Error Message: “Fatal Error: Cannot recover after last error. Any further errors will be ignored.”
    • The issue is fully resolved once the plugin is deactivated.

    We’re hoping to understand whether a patch or update is planned to address this, or if there’s a recommended workaround to ensure compatibility while keeping the plugin active.

    Please let us know if you require any additional logs, access details, or test results from our side to expedite the investigation.

    Looking forward to your update.

    Thread Starter Ramiz Theba

    (@ramizmyadvice)

    6 months, 3 weeks ago

    Follow-Up on Validation Error Caused by Lead Forensics Plugin

    Hi @lead-forensics

    I’m following up on the open ticket regarding the W3C validation error triggered by the Lead Forensics plugin on our website.

    To recap:

    Summary of Findings:

    • ✅ Validation passes when the plugin is disabled
      🔗 Validation (Plugin Disabled)
    • ❌ Validation fails with a fatal error when the plugin is enabled
      🔗 Validation (Plugin Enabled)
    • Error Message:
      “Fatal Error: Cannot recover after last error. Any further errors will be ignored.”

    Image What need to be changed : https://prnt.sc/wHo2w1OpyWeu

    I have fixed it and it resolve the issues on my staging site. Please release new update with above changes.

    Please let us know if you require any additional logs, access credentials, or test results to assist with your investigation.

    Looking forward to your response.

    Best regards,
    Ramiz

    • This reply was modified 6 months, 3 weeks ago by Ramiz Theba.
    • This reply was modified 6 months, 3 weeks ago by Ramiz Theba.
Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Plugin Conflict – Causes W3C Validation Fatal Error’ is closed to new replies.