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

Resource creation date column don't use datetime.utcnow() #3447

Closed
Engerrs opened this issue Feb 20, 2017 · 0 comments
Closed

Resource creation date column don't use datetime.utcnow() #3447

Engerrs opened this issue Feb 20, 2017 · 0 comments

Comments

@Engerrs
Copy link
Member

@Engerrs Engerrs commented Feb 20, 2017

CKAN Version if known (or site URL)

Current version

Expected behaviour

When creating resource for dataset and entering to it summary page, in additional information table, there are two dates of Creation. One is showing only month,day,year. Second one is showing when we click on 'Show more' button under the table, this field should show how much time ago the resource was created, for example, if it was created just now, it should display 'Just now'.

Actual behaviour

When we create new resource for dataset, on resource summary page in additional information table, when we click 'Show more', field 'created' shows '-1 days ago'.

What steps can be taken to reproduce the issue?

1.Create dataset.
2.Create resource for this dataset.
3.Enter resource summary page.
4.Click 'Show more' under the Additional info table.
5.'created' field shows '-1 days ago'.

Engerrs pushed a commit to Engerrs/ckan that referenced this issue Feb 20, 2017
@Engerrs Engerrs changed the title Resource creation date don't use datetime.utcnow() Resource creation date column don't use datetime.utcnow() Feb 20, 2017
wardi added a commit that referenced this issue Feb 20, 2017
…t_use_utcnow

[#3447] Resource creation date use datetime.utcnow()
@wardi wardi closed this Feb 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants