Adding CPT to Index under 2.2 doesn’t appear under Send your data tab.

  • dcminyard
    Participant
    1 month, 2 weeks ago #45868

    My index is hosted under OpenSolr. I have some custom post types, one of which is being successfully indexed. I tried to add another CPT (webinars) using tab 2.2. I have ticked the box (as shown in the screengrab here: tab 2.2. However, this CPT doesn’t appear in the Send your data tab (as shown here: send your data. There are already posts under this CPT, and the WPSolr index option does appear :wpsolr index option for posts. Is there something I’m missing? Is the fact that there are already posts under this CPT the problem? I moved one as a test to draft, then republished, but no progress. Any suggestions?

    • This topic was modified 1 month, 2 weeks ago by dcminyard.
    • This topic was modified 1 month, 2 weeks ago by dcminyard.
    dcminyard
    Participant
    1 month, 2 weeks ago #45871

    Sorry, here is the image that corresponds to tab 2.2. I should also add the CPT webinars is generated by ACF.

    • This reply was modified 1 month, 2 weeks ago by dcminyard. Reason: adding clarity
    wpsolr
    Keymaster
    1 month, 2 weeks ago #45873

    Does the “Webinar” CPT have something different in its WP definition?

    dcminyard
    Participant
    1 month, 1 week ago #45957

    I see the post type is set as a sub-menu under “post-types”, as shown here. Other than this, it’s a standard ACF post type.

    wpsolr
    Keymaster
    1 month, 1 week ago #45958

    Is this post type searchable?

    dcminyard
    Participant
    1 month, 1 week ago #45959

    Yes, at least the option NOT to search is enabled on the post type: WPSolr search option. The ACF plugin is active in the WPSolr configuration too. ACF plugin for WPSolr.

    wpsolr
    Keymaster
    1 month, 1 week ago #45960

    It could be that the ACF post type is registered after the WPSOLr code is executed. Can you control in ACF the hook priority?

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

You must be logged in to reply to this topic.