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

Include future post_status in the Translation Metabox / Change Relationship #284

Closed
luisarn opened this Issue Sep 25, 2017 · 2 comments

Comments

2 participants
@luisarn

luisarn commented Sep 25, 2017

Version Information

  • PHP: 7.1.9
  • WordPress: 4.8.2

Steps to Reproduce

  1. Go to the Translation Metabox
  2. Change Relationship
  3. Select existing post …

What I Expected

Display all the post.

What Happened Instead

Scheduled post are not displaying.

So I added the post status 'future' on line 104 of Mlp_Relationship_Control_Data.php

@tfrommen

This comment has been minimized.

Show comment
Hide comment
@tfrommen

tfrommen Sep 25, 2017

Contributor

Hi there,

yes, this makes complete sense, and as you can see, we already did this for the upcoming major release. Also, there will be a new filter for the complete arguments.

We will also include this in version 2.10.0, which we are about to release soon.

Contributor

tfrommen commented Sep 25, 2017

Hi there,

yes, this makes complete sense, and as you can see, we already did this for the upcoming major release. Also, there will be a new filter for the complete arguments.

We will also include this in version 2.10.0, which we are about to release soon.

@tfrommen tfrommen added this to the v2.10.0 milestone Sep 25, 2017

tfrommen added a commit that referenced this issue Sep 25, 2017

Enhance remote post search. #284
Include scheduled posts.
Introduce query arguments filter.
@tfrommen

This comment has been minimized.

Show comment
Hide comment
@tfrommen

tfrommen Sep 25, 2017

Contributor

Implemented in b7e9e90.

Contributor

tfrommen commented Sep 25, 2017

Implemented in b7e9e90.

@tfrommen tfrommen closed this Sep 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment