WordPress.org

Ready to get started?Download WordPress

Forums

Broken Link Checker
Make compatible with Advanced Custom Fields Plugin? (7 posts)

  1. Jean Goodwyn
    Member
    Posted 1 year ago #

    I have the same problem as the gent who posted this:
    http://wordpress.org/support/topic/plugin-broken-link-checker-custom-fields-cause-phantom-broken-links

    In short, we're not really able to make it check custom fields created by the Advanced Custom Fields plugin. ACF seems fairly prolific; any chance we could get some built-in support for it? I don't know about everyone else, but I personally would be delighted with just a checkbox on the What To Check tab for 'Advanced Custom Fields'.

    Love the link checker, SO want it to work on all the content. :)

    Thanks!

    http://wordpress.org/extend/plugins/broken-link-checker/

  2. trinzia
    Member
    Posted 1 year ago #

    Not working on custom fields inside custom post types. Which is 99% of my site. Would be glad for a fix for that.

  3. David
    Member
    Posted 1 year ago #

    Ditto to all of that. Virtually all of my data is added through Advanced Custom Fields, but just finding links in specific custom fields on custom post types would be enough for me.

  4. msebald
    Member
    Posted 12 months ago #

    I am also looking for support for ACF as most of the data on my website is stored in custom fields generated with ACF.

  5. Jacob Gotwals
    Member
    Posted 11 months ago #

    It seems to be working for me for URLs in a "Text" custom field containing a single URL, created by ACF, on a custom post type.

    In BLC settings under "Look for Links In", I checked "Custom fields", clicked "Configure", added the "Field Name" from ACF, and also checked the box for my custom post type. Then I tried adding a few custom posts, some with working links in my custom field and some with broken links. When I went to Tools / Broken Links, the broken ones were listed.

    Hope that helps...

  6. eliot.eshelman
    Member
    Posted 11 months ago #

    I'm fighting with similar issues and have tracked down some of the cause. BLC does not assume that we're putting arbitrary HTML into custom fields. It only looks at the first line of a custom field.

    Comment from the metadata.php file:

    If this is a multiline metadata field take only the first line (workaround for the 'enclosure' field).

    I've never used "enclosure" fields, so I'm not certain exactly how to patch this without breaking them. Overall, I'd rather have BLC run the regular HTML check on my custom fields. The current custom field check is clearly causing people issues.

  7. eliot.eshelman
    Member
    Posted 11 months ago #

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic