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

feels posts are listed out of date order when someone edits an entry #27

Open
modgethanc opened this issue Jan 2, 2018 · 3 comments
Open
Assignees
Labels
Milestone

Comments

@modgethanc
Copy link
Owner

modgethanc commented Jan 2, 2018

ttbp.view_feed() uses mtime to determine display order; this means that older entries with a recent mtime will get bumped up on the feed.

the behavior that i intended was that editing a post on the day of should bump it up within that day, but it should not bump a backdated post to the current day.

@modgethanc modgethanc added the bug label Jan 2, 2018
@modgethanc modgethanc self-assigned this Jan 2, 2018
@modgethanc
Copy link
Owner Author

note to self for fixing this:

  • check if entry filename date and mtime date match
  • if they don't match, process it as if it was last modified on the date indicated by filename, rather than the actual mtime date (this will probably include some modification for how core.meta() handles generating the mtime)

(also, now that i'm looking at core.meta(), dear god that is ugly and should get flagged for a refactor)

@modgethanc modgethanc added this to the 1.0 release milestone Jan 2, 2018
@coreyreichle
Copy link

Perhaps just modified mtime of a file, and set it to date that matches the file name?

Can be done from the shell, obviously:
touch -at 1212171600 ./12122017.txt

@modgethanc
Copy link
Owner Author

i think i'd rather not mess with mtime like that, or at least leave it up to individual users if they want to do that, because it's a little bit obscure for less savvy linux users, and also might interfere with other reasons people might have to want to preserve an accurate mtime.

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

No branches or pull requests

2 participants