This is the respective issue for https://www.drupal.org/project/drupal/issues/1838918
Problem/Motivation
The current
{node}.createdand{node}.changedcolumns are often insufficient to meet the needs of publishing workflows. Take the following use case...An author creates a new article on May 1. This article is edited several times, eventually being published on May 9. Any chronological article listing should now list the article's date as May 9. On May 15, a small typo is discovered. The article is then edited to fix the typo and saved, but chronological article listings should still list the article's date as May 9, since that is when it was originally published.
Currently there is no straightforward way of accomplishing this. Listing articles by creation date doesn't account for articles which are held in draft form for a time while being readied for publication. Listing articles by their modification date fails to account for articles which need minor corrections after they have been published.
Proposed resolution
Add a "published" timestamp column to the
{node}table. When a node is saved, if{node}.status=1and no publication date has been set, then set{node}.published={node}.changed. However, if{node}.publishedis not empty, then maintain the existing value.User interface changes
Replace the current "Authored on" field, under the "Authoring information" tab on node edit forms, with a new "First published on" field. When the node edit form is loaded, if
{node}.published > 0then the existing value is displayed, otherwise the field is blank. If this field is empty when the node is published, a published date will be generated automatically on submission. If the user manually enters a value in the "First published on" field, then it will be used in place of the default value for{node}.published, overwriting any existing value.The default front page node listing —and its equivalent Views display— will sort on the new published date, instead of nodes' created date. Likewise, the submission information displayed on nodes will use the published date.
Alternatives:
There is currently a contrib module for this: https://backdropcms.org/project/publication_date
API changes
Minor changes to implement
{node}.published, but nothing that should impact other modules, unless they want to use the new timestamp for something.
Recent comments
I have had a read of what Lando provides, and it's an excellent development tool, and it would solve the problem. But, I would prefer to find out why the problem is there in the first...
How often is the settings.php loaded.
Thanks for the info. I will give it a try...
How often is the settings.php loaded.
I use Lando (a wrapper for docker) and find settings changes happen straight away
How often is the settings.php loaded.