Skip to content

Hotfix/respect future post status#6047

Merged
KingYes merged 4 commits intoelementor:release/2.3.0from
matipojo:hotfix/respect-future-post-status
Nov 6, 2018
Merged

Hotfix/respect future post status#6047
KingYes merged 4 commits intoelementor:release/2.3.0from
matipojo:hotfix/respect-future-post-status

Conversation

@matipojo
Copy link
Copy Markdown
Member

@matipojo matipojo commented Nov 1, 2018

No description provided.

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ matipojo
❌ lb1programmer


lb1programmer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@matipojo matipojo force-pushed the hotfix/respect-future-post-status branch from 671c962 to ff2d1e9 Compare November 5, 2018 09:35
@joshmarom joshmarom closed this Nov 5, 2018
@KingYes KingYes reopened this Nov 5, 2018
@KingYes KingYes merged commit 2153c8e into elementor:release/2.3.0 Nov 6, 2018

$statuses = get_post_statuses();
if ( 'future' === $this->get_main_post()->post_status ) {
$statuses['future'] = __( 'Feature', '' );
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo

@KingYes KingYes mentioned this pull request Nov 6, 2018
12 tasks
@matipojo matipojo deleted the hotfix/respect-future-post-status branch November 12, 2018 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants