Problem/Motivation

This is a follow up to #1838918: Add 'published' timestamp to nodes and is dependent on that patch being committed.

"Authored on" is a little ambiguous as is, but the addition of a published date field makes its intention even less clear. This can negatively impact UX.

Proposed resolution

Option #1: Remove the "Authored on" field altogether. Let a node's creation date be just that. It could still be changed programmatically, but we would not provide a UI for doing so. Assuming #1892744: Use pulished date, instead of created date, for default node listings gets committed, altering the creation date would be less important anyway.

Option #2: If we REALLY think users need the ability to alter a nodes creation date in the UI, then lets change the field label to "Created on." This at least makes the fields intention clearer.

Remaining tasks

  1. Commit the patch from #1838918: Add 'published' timestamp to nodes
  2. Decide on option #1 or #2
  3. Implement option #1 or #2
  4. Review patch and commit!

User interface changes

The "Authored on" field, on the node edit form, will be renamed or removed altogether.

API changes

None.

Related issues:

Comments

xmacinfo’s picture

xmacinfo
he/him
Primary language French
Location Canada
commented

As seen at #1838918: Add 'published' timestamp to nodes, here is my reaction:

“Authored on” and “First published on” does not mean anything and are confusing.

Do they mean the “created” date? Or the new “published” date?

Please remove any confusion and use simple and understandable lingo. Also think of translation issues when something is not clear, translation will add another degree of uncertainty.

We should stick to Created [date], Modified [date] and Published [date].

jstoller’s picture

jstoller
he/him
commented
Status: Active » Closed (duplicate)

This task has now been rolled into the patch at #1838918: Add 'published' timestamp to nodes.