8000 Feature request: ability to specify date=NOW in metadata settings · Issue #277 · prose/prose · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature request: ability to specify date=NOW in metadata settings #277

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.

Sign up for GitHub

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

Jump to bottom
Closed
darvin opened this issue Jan 13, 2013 · 20 comments · Fixed by #831
Closed

Feature request: ability to specify date=NOW in metadata settings #277

darvin opened this issue Jan 13, 2013 · 20 comments · Fixed by #831
Labels
regression

Comments

@darvin
Copy link
Contributor
darvin commented Jan 13, 2013 
#prose.io settings
prose:
  rooturl: "source"
  metadata:
    "source/_posts": |
      layout: post
      title: "Title"
      date: 2012-12-22 14:07
      comments: true
      categories: 
      published: true

I would like to be able to specify date: CURRENT or something and have this field autogenerated on document creation. or just point me on place to implement this
@darvin darvin mentioned this issue Jan 13, 2013
Merged
@dhcole
Copy link
Member
dhcole commented Mar 25, 2013

CURRENT_DATETIME should work now, via b22708a

@dhcole dhcole closed this as completed Mar 25, 2013
@bcomnes bcomnes mentioned this issue Jul 31, 2013
< 8000 div class="mt-2 d-flex flex-items-start flex-column flex-md-row">
Closed
@bcomnes
Copy link
bcomnes commented Jul 31, 2013

I added this variable to the wiki to make it more visible.

@bcomnes
Copy link
bcomnes commented Jul 31, 2013

With that being said, I can't get it to work. Can anyone provide an example on how to use this?

@mikemorris
Copy link
Contributor

Looks like this was only ported over to preserve existing implementations of default metadata for older versions of Prose. Support hasn't been added for the new metadata editor configuration yet.

@mikemorris mikemorris reopened this Aug 1, 2013
@joewiz
Copy link
joewiz commented Aug 20, 2013

Before I added prose configuration to my _config.yml, prose.io was prepopulating the filenames of new Jekyll posts with the current date. But once I added prose configuration, it stopped doing that, even after I added - date: CURRENT_DATETIME as suggested above.

@bcomnes
Copy link
bcomnes commented Aug 22, 2013

@joewiz That advice was from an older version of prose. It sounds like it needs to be re-implemented at this point.

@mikemorris
Copy link
Contributor

Yep, that's correct @bcomnes @joewiz

@joewiz
Copy link
joewiz commented Aug 23, 2013

Ah, thanks, guys. A very nice feature indeed.

@ghost
Copy link
ghost commented Sep 20, 2013

Currently, once configuration is added to _config.yml for Jekyll-based sites, the ISO date is not required in the post title field in Prose, and will be added automatically upon file save.

@mohamnag
Copy link

and what about - date: CURRENT_DATETIME? when will it work? or is there another way to set YML on new posts to current date time?

@orschiro
Copy link
orschiro commented May 7, 2014

I am also currently moving my blog to be managed with prose. However, handling date is a really important feature.

Any chance that this will be working again any time soon?

Thanks!

@LPTK
Copy link
LPTK commented May 16, 2014

I'm having the same problem. Having a date for my posts is one of the most important things. It seems the right date is already generated for the name of the file... couldn't it be used also for a "date" meta field?
@JHabdas I'm not sure what you mean. For me, whether I specify it or not in the config file, the date field seems to be never inferred.

@mikemorris mikemorris mentioned this issue Sep 8, 2014
Open
@mikemorris mikemorris mentioned this issue Feb 2, 2015
Closed
@fulldecent
< 8000 div class="ml-n3 timeline-comment unminimized-comment comment previewable-edit js-task-list-container js-comment timeline-comment--caret" data-body-version="197a43ad3b09539f77b6dd591906d2277dbd34c51cdc41acbbfa88d7a1f79661">
Copy link

Hello and thank you for this issue report. There have been several point releases in Prose since this issue was opened and there has not been much discussion here. I wanted to ask if you could please assist in confirming this is still an issue in the latest version of the product. If it is fixed, please close this issue :-)

Also, if possible could you please

  • Create a test case -- a list of steps we can perform to reproduce the problem

Since this project is looking for new maintainers (#743), it will be helpful if users can double check the old issues and delete ones that are fixed. This will be super helpful for the new team that works on moving this project forward.

I'm sorry this message is impersonal. And thanks for your help!

@orschiro
Copy link
orschiro commented Feb 7, 2015

I think this issue is fixed. Last time I created a new md document, I didn't specify any date, which was automatically inserted by Prose using the current date.

frolic added a commit to frolic/prose that referenced this issue Apr 29, 2015
@frolic
Re-implement CURRENT_DATETIME replacement in metadata
7b4089b 
Closes prose#277
@frolic frolic mentioned this issue Apr 29, 2015
Merged
frolic added a commit to frolic/prose that referenced this issue May 13, 2015
@frolic
Re-implement CURRENT_DATETIME replacement in metadata
353efbf 
Closes prose#277
@dereklieu
Copy link
Member

#831 allows you to set date: CURRENT_DATETIME to get the current date.

You can also do something like:

- name: "date"
  field:
    element: "text"
    label: "Date"
    value: "CURRENT_DATETIME"

@joewiz
Copy link
joewiz commented May 13, 2015

Wonderful! Thanks very much for this!

@ndarville
Copy link

@dereklieu What am I doing wrong, if I just get a date field with the CURRENT_DATETIME string in it instead of the date?

@dereklieu
Copy link
Member

@ndarville If you're using prose.io then these changes haven't been deployed yet. We're discussing automatic deployment in #835. I will look into a manual deployment in the meantime.

@ndarville
Copy link

@dereklieu Ah, I see.

@orschiro
Copy link

@dereklieu This is fantastic. Thanks very much for your efforts!

kennethormandy pushed a commit to losttype/losttype-prose that referenced this issue Aug 3, 2015
@frolic @kennethormandy
Re-implement CURRENT_DATETIME replacement in metadata
abb0524 
Closes prose#277
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
regression
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Re-implement CURRENT_DATETIME replacement in metadata frolic/prose
0