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

Change future config default to true as docs state it should be #10

Merged
merged 1 commit into from Aug 19, 2011

Conversation

javierjulio
Copy link
Contributor

The default for the future config item should be true after reading the documentation as it states as if it were true: "Articles with a date in the future will not appear on the site, thus allowing you to prepare article that should be published later."

colszowka added a commit that referenced this pull request Aug 19, 2011
Change future config default to true as docs state it should be
@colszowka colszowka merged commit 5e31a59 into colszowka:master Aug 19, 2011
@colszowka
Copy link
Owner

Thanks, well observed :)

…he documentation as it states as if it were true: "Articles with a date in the future will not appear on the site, thus allowing you to prepare article that should be published later."
@javierjulio
Copy link
Contributor Author

No problem, happy to contribute. :) Still going strong with Serious. I have another topic branch with documentation updates. I haven't edited it in awhile so I'll just push that through sometime today to get your feedback at least. Hopefully that gets incorporated as well.

@javierjulio
Copy link
Contributor Author

Yikes! Sorry @colszowka I realize I made a big mistake here. The value should be false. The tests are failing since the default value is true meaning future posts are included but that is incorrect. Per the documentation should be false so posts with a future date are NOT included. Sorry. :(

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.

None yet

2 participants