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 request: Backend, Date for Entries #260
Comments
+1 |
Can't promise this for Stable, will keep it in mind for Future. |
For my ISO-8859-1 special chared testblog I do it like this (only a simple approach) <a href="?serendipity[action]=admin&serendipity[adminModule]=entries&serendipity[adminAction]=edit&serendipity[id]={$entry.id}" title="#{$entry.id}: {$entry.title|escape:'html':{$CONST.LANG_CHARSET}:false} ({$entry.timestamp|@formatTime:$CONST.DATE_FORMAT_SHORT})">{$entry.title|escape:'html':{$CONST.LANG_CHARSET}:false|truncate:75}</a> |
Thanks, but since |
Since space if scare in the dashboard, scheduled entries will now display their publish date instead of the 'Scheduled' badge. The info that this is a scheduled entry will be available in a tooltip of the pulish date. This seems like the best compromise on all devices/resolutions. References #260
It should be pretty obvious that an entry is scheduled if it displays a date in the future, right? So I decided to just display that date and some extra info in a tooltip of the date badge. That should do the trick. |
This is pretty nice and would help a lot. What about showing the time for Draft articles as well (instead of using the word "Draft")? The gray backgrounds states that the article is not online yet. |
btw can you both access {if $entry.ep_is_sticky}? |
OK, in dashboard overview.inc.tpl this should be BUG! And, If set as a |
(To seperate issues.) |
I don't think so.
|
There is a big green button titled "published" which shows that the article is a draft. In my opinion the button does not make any sense without the information about the date of the draft. |
You are right, because all it does is publish the draft. What (I think) it should do is set the date/time to current and publish. The current behaviour of the Publish button doesn't make much sense, I think. See #262 However, I don't see the usefulness of a date of a draft. It is not necessarily the date the draft was last edited (you'd have to reset that manually, I don't think we store a “last edited” timestamp), but it's not necessarily the date the draft is supposed to be published at, either. Even if so, wouldn't you schedule an article if you already knew the date it's supposed to be published at? Maybe I just use drafts differently than other people, but to me, a draft is something that will be published (or scheduled) once it's finished. So the publication date depends on the completion of the content, which is not necessarily tied to a date. |
I like that approach and I like to discuss that in #262 Keeping this in mind we would not need the draft status to be displayed. Articles in the dashboard would be either articles coming in the future or being drafts. So the only information needed would be the future date or the publish button. Good one! |
Well, it doesn't hurt to display it, either. Also, we might decide to add other article states to the dashboard at some point. I think it's a good idea for the future to have a state indicator of some kind for any article. |
In my opinion it would be a great idea to show the dates of the entries on the right hand side of the dashboard.
I geht a "vorgemerkt", in case an article is ready to be published at some point in time in the future, but I can not see the date.
The text was updated successfully, but these errors were encountered: