You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2019. It is now read-only.
I'm currently looking for a solution on a very specific problem on our end.
We have several different custom post types in our WordPress dashboard but for our front-end user they should all look the same, like "News".
What we are currently doing is listing those posts in another website with vanilla js Algolia, but since they are all segregated we need to query multiple Algolia indexes even tho they should all look the same.
The ideal solution would be to have a single Algolia index with all multiple custom post types (posts, pages, posts_news, posts_clippings). Is that achievable?
I'm even trying to create a CPT in WordPress which is the combination of multiple CPT but really can't seem to find a solution.
EDIT: Found similar Issues listed here but I believe the other ones had different outcomes.
Thank you
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm currently looking for a solution on a very specific problem on our end.
We have several different custom post types in our WordPress dashboard but for our front-end user they should all look the same, like "News".
What we are currently doing is listing those posts in another website with vanilla js Algolia, but since they are all segregated we need to query multiple Algolia indexes even tho they should all look the same.
The ideal solution would be to have a single Algolia index with all multiple custom post types (posts, pages, posts_news, posts_clippings). Is that achievable?
I'm even trying to create a CPT in WordPress which is the combination of multiple CPT but really can't seem to find a solution.
EDIT: Found similar Issues listed here but I believe the other ones had different outcomes.
Thank you
The text was updated successfully, but these errors were encountered: