Support » Theme: Startup Blog » Incorrect URI

  • I use the plugin “S.A.F. – wpTools Security” to scan my site for security issues and others. Every time it runs, I get 404 errors: “Incorrect URI”. The most recent list includes these. Is this a Theme issue?

    /.well-known/assetlinks.json
    /wp-content/themes/startup-blog/assets/font-awesome/css/font-awesome.min.css?ver=5.2.3
    /wp-content/uploads/2018/07/Oatka-10-07-06_015-e1532222397809.jpg
    /wp-content/themes/startup-blog/assets/font-awesome/css/font-awesome.min.css?ver=5.2.2
    /wp-cron.php?doing_wp_cron=1567542788.3397889137268066406250
    /2018/09/22/wayo-interview-with-al-abonado-about-where-is-the-river/feed/
    /2007/07/05/412/
    /2018/08/17/review-of-looking-askance-by-laura-klinkon/feed/
    /?author=15
    /?author=14

    Any suggestions how to fix? Thank you.

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

Viewing 1 replies (of 1 total)
  • Theme Author Ben Sibley

    (@bensibley)

    Thanks for using Startup Blog!

    I’m not sure the exact nature of the report you’re getting, but out of the URLs listed these are the two that are relevant to the Startup Blog theme:

    /.well-known/assetlinks.json
    /wp-content/themes/startup-blog/assets/font-awesome/css/font-awesome.min.css?ver=5.2.3
    /wp-content/uploads/2018/07/Oatka-10-07-06_015-e1532222397809.jpg
    /wp-content/themes/startup-blog/assets/font-awesome/css/font-awesome.min.css?ver=5.2.2
    /wp-cron.php?doing_wp_cron=1567542788.3397889137268066406250
    /2018/09/22/wayo-interview-with-al-abonado-about-where-is-the-river/feed/
    /2007/07/05/412/
    /2018/08/17/review-of-looking-askance-by-laura-klinkon/feed/
    /?author=15
    /?author=14

    Those two URLs produce 404 errors when I visit them, but to be honest I’m not sure why the plugin is detecting those URLs at all. The Font Awesome stylesheet they’re referencing is being loaded properly at this URL when I visit the site: http://pics.competethemes.com/92ffe36f1f0c

    I think you can safely ignore those two 404 reports since they aren’t affecting real visitors. I’m guessing there is a small glitch with how the plugin generates these URLs or something like that.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.