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

Feature: Better support for posts without titles (microblog posts) #1274

Closed
markphilpot opened this issue Apr 16, 2018 · 7 comments
Closed

Comments

@markphilpot
Copy link

Right now there is nothing that prevents the creation of posts without titles, but the UI shows empty regions for those posts.

image

It would be nice if instead it showed the first X characters (~120) of the post when there is no title.

@erquhart
Copy link
Contributor

Totally agree.

@tech4him1
Copy link
Contributor

Agree, but I think we'll have to wait for #445.

@markphilpot
Copy link
Author

To be clear (and I don't know if this comment belongs here or #445) I was able to create a post without a title (and hence no slug) by relying completely on the time fields:

slug: "{{year}}-{{month}}-{{day}}-{{hour}}_{{minute}}_{{second}}"

I agree it's probably better to fix the handling in #445 before but it might not be required.

@barthc
Copy link
Contributor

barthc commented Dec 12, 2018

I don't think it's possible any more to create a post without an identifier field or with empty identifier field value, as this error
Failed to persist entry: Error: Collection must have a field name that is a valid entry identifier, or must have 'identifier_field' set
popups up. Even for slug format like so:
slug: "{{year}}-{{month}}-{{day}}-{{hour}}_{{minute}}_{{second}}"

@tomrutgers
Copy link
Contributor

Just tested this and you are correct @barthc. That error only shows up in the console, so there's not a hell of a lot of feedback as to what's happening but the post isn't published anymore.

@tech4him1
Copy link
Contributor

@tomrutgers Do we have another issue covering actual support of posts without titles, or should we reopen/expand this issue to include full support?

@tomrutgers
Copy link
Contributor

@tech4him1 There was this one, #1700 but it got closed by #1543. We could reopen/expand but then again this issue hasn't been very active anyway.. Thoughts?

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

No branches or pull requests

5 participants