ACF not working for specific post type

  • Resolved Yvan

    (@dugwood)


    4 months, 1 week ago

    I was struggling with the range filter, based upon an ACF Numeric field. At last, I’ve added the ACF group to default post type (post), and it works. It even works with Text fields.

    So I think your demo on https://demo.filtereverything.pro/example/acf/ is an ACF group linked to « Posts », and not a dedicated post type (as we can create in /wp-admin/edit.php?post_type=acf-post-type).

    Can you confirm this behaviour? And fix it if possible 🙂

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support fesupportteam

    (@fesupportteam)

    4 months, 1 week ago

    Hi @dugwood

    Please provide the following screenshots so that we have enough information to recreate this on our end:

    1. ACF field settings – This should include the field group, the exact ACF data, on which post type it is applied.
    2. CPT data – Its name and, if possible, how it was created.
    3. Post editing – How you applied this data in the custom field of your CPT post.

    Best Regards,
    Victor

    Thread Starter Yvan

    (@dugwood)

    4 months, 1 week ago

    Hello Victor ( @fesupportteam ),

    I’ve only done this:

    • create a new post type: Test
    • create a new group in ACF
    • added a new field (numeric type, but text type is okay too), say « my_field »
    • associate this new field with both post types: Post and Test
    • create the same content, both in Post and Test, with the same values and same extra field my_field = 5

    Then:

    • create a new Filter set
    • matching post type = Post
    • Custom field numeric

    Then when I set the [fe_widget] on a Post archive page: it works as expected (I can see the extra field is in the range of 5 to 5)

    • change the Filter set to post type = Test

    Then on a Test archive page: range is 0 to 0.

    I’ve also noted that your example https://demo.filtereverything.pro/example/acf/ seems to use the « product » post type, which might be the one from Woocommerce. I’ve tested another keyword, but perhaps if my new post type is indeed « product », that may work.

    I’ll test it again from scratch if needed, but all my post types are failing, unless I attach everything to Posts. Tested with ACF and SCF, same outcome.

    Plugin Support fesupportteam

    (@fesupportteam)

    4 months, 1 week ago

    For clarification, do you have the PRO or the Free version of the plugin?

    Best Regards,
    Victor

    Thread Starter Yvan

    (@dugwood)

    4 months, 1 week ago

    @fesupportteam I’m using the Free version, on the latest WordPress release.

    Plugin Support fesupportteam

    (@fesupportteam)

    4 months, 1 week ago

    The Free version works only with the main query, so if you are using a custom query to display your CPTs, this is exactly why you cannot see the values from the custom fields. On default posts, the values are visible because the main query is being used.

    However, here’s what we recommend trying for testing:

    1. Use this plugin to add CPTs: https://ww.wp.xz.cn/plugins/custom-post-type-ui/
    2. Add a new numeric custom field with a unique name that has never been used before, such as fe_num_test_fld. This ensures the field is completely new and avoids mixed data type issues in the database if a field with the same name was previously used with a different data type.
    3. Turn off all caching on the site during testing, especially object caching.

    Best Regards,
    Victor

    Thread Starter Yvan

    (@dugwood)

    4 months, 1 week ago

    Thanks Victor,

    That may be the issue. It should be visible somehow… I’ve seen there’s a « debug » that’s checked by default, so it should leverage such information.

    But, if it’s not a bug in the Pro version, that’s fine by me. I’ll use it on standard posts for the time being.

    If there was a lifetime offer, I would pay it for my client, but yearly subscription is a no go.

    Best regards,
    Yvan.

    Plugin Support fesupportteam

    (@fesupportteam)

    4 months, 1 week ago

    We only have a lifetime license for the PRO version. For information regarding this, you can contact us in the comments section on the site where the plugin can be purchased, and we will provide all the required details.

    Unfortunately, we cannot provide that information here. As per forum guidelines, we are not allowed to discuss commercial products or share links to the pages where they are sold.

    Best Regards,
    Victor

    Thread Starter Yvan

    (@dugwood)

    4 months, 1 week ago

    I didn’t see that was a one time fee, so Pro is the best solution 🙂 Sorry I missed it! Thanks for the fast support!

Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.