Indexing Error When URL Field Returns 404 or Forbidden

Tagged:
  • pridigital
    Participant
    1 year, 4 months ago #54219

    Hi,

    I’m encountering an issue when trying to index a post in the “3. Process Data” tab. Here’s the error message I’m getting:

    Error on embedded URL “https://xconomy.com/national/2020/04/17/covid-19-vax-efforts-aim-to-balance-speed-efficacy-in-race-to-market/” of post_id 10157. Could not access the attachment content. Not Found

    It seems the indexing process fails completely when one of the custom fields references a URL that either returns a 404 or a 403 Forbidden response. This behavior wasn’t happening before the latest update—in the past, the post would still be indexed even if a linked URL was inaccessible.

    I’d like to continue indexing posts regardless of whether the referenced URLs are reachable or not. Removing entries from the index due to broken or restricted links isn’t ideal for our use case.

    Could you please advise on how to disable this behavior or suggest a workaround?

    Thanks!

    wpsolr
    Keymaster
    1 year, 4 months ago #54221

    I guess you are using the WPSOLR ACF add-on. The piece of code that extract file contents from ACF file fields has not changed, and was always expected to fail on 404 or 403.

    The only thing you can do is to fix each post with urls, or prevent them from being indexed:
    – Deactivate the ACF add-on “Index all files option”, and activate the same option on each post meta-field without error
    – Or activate the ACF add-on “Index all files option”, and deactivate the same option on each post meta-field with errors

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.