• Ever since installing the plugin we are getting a lot of 404 errors posted as shown below. We just updated to 1.60 of the plugin and are using WP Version 6.8.2

    I was trying to attach a screenshot but it won’t let me. The 404s appear to be referencing fonts which are not installed or in the directory listed

    /wp-admin/~@/assets/fonts/Inter-SemiBold.ttf

    /wp-admin/~@/assets/fonts/Inter-Bold.ttf

    /wp-admin/~@/assets/fonts/Inter-Regular.ttf

    /wp-admin/~@/assets/fonts/Inter-Bold.ttf

    • This topic was modified 7 months, 3 weeks ago by mbang.

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

Viewing 1 replies (of 1 total)
  • Plugin Author Hueston

    (@huestonwins)

    Hi there,Thank you for reaching out and providing the details about the 404 errors you’re experiencing.I’ve reviewed our plugin code thoroughly, and I can confirm that these 404 errors are not being caused by the LLM Bot Tracker plugin. Our plugin does not load, reference, or include any font files whatsoever, including the Inter font family you’re seeing in the errors.The unusual path structure (/wp-admin/~@/assets/fonts/) is not something our plugin creates or uses. These errors are likely coming from:

    1. Another plugin or theme that’s trying to load Inter fonts but has incorrect paths
    2. WordPress 6.8.2’s new Font Library feature – This version introduced new font management that might be misconfigured
    3. A caching or optimization plugin that’s attempting to optimize fonts but has path issues

    To identify the actual source:

    1. Quick Test: Temporarily deactivate LLM Bot Tracker – you’ll see these 404 errors continue, confirming it’s not our plugin
    2. Plugin Conflict Check: Deactivate other plugins one by one until the 404s stop
    3. Theme Check: Switch temporarily to a default WordPress theme (like Twenty Twenty-Four) to rule out theme issues
    4. Browser Console: Check if these font requests are coming from inline styles or a specific plugin/theme file
Viewing 1 replies (of 1 total)

The topic ‘404 errors from plugin’ is closed to new replies.