Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly set post type param to fix issues with Polylang and possibly others. #109

Closed

Conversation

JoryHogeveen
Copy link
Member

Setting the post type to any can cause edge case issues with other plugins and WP core.

For non-translatable post types this will create compatibility issues with Polyland since adding any will trigger Polylang to add the language queries, even though the ID's might not be translatable.

Other than that, setting any also affects WP default query to only include public posts. I can imagine edge cases where this might cause issues.

Polylang auto enables translation if the post type is `any`, this causes edge case issues for non-translatable post types.
@quasel
Copy link
Member

quasel commented Oct 16, 2020

looks good for me!

@quasel quasel self-requested a review October 16, 2020 14:27
@sc0ttkclark sc0ttkclark self-assigned this Dec 30, 2020
@sc0ttkclark sc0ttkclark deleted the branch pods-framework:1.x December 30, 2020 14:39
@JoryHogeveen
Copy link
Member Author

@sc0ttkclark Why was this closed? I just encountered the same issue again, I thought this was merged haha

@quasel Maybe revive this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants