You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I first noticed this when using drupal-starter-installer with saplings to spin up the UCSF Psych site, but I thought/hoped it was a one-off glitch.
But now I see the same bug on UCSF OBGYN after using drupal-starter-installer with saplings. I don't see this problem on the Humane World site because it currently uses the legacy site's config rather than saplings config.
When the Publications Date module is manually enabled on a Drupal 10 site, the new "published_at" property gets added successfully to the node_field_date and node_revision_field_date tables in the database. This ensures there is a Published At input on the node edit form.
When the Publications Date module is enabled by saplings-content-types, the "published_at" property does not get created and the input on the front end is not displayed.
Bandaid
In order to repair Psych and OBGYN, I had to write the following update hook in a *.install file in a custom module. This update has to run on a deployment after and separate from the initial project deployment because it won't work on the same deployment that is enabling the Publication Date module.
I suspect this is caused by a bug in the Publication Date module. I haven't validated this, but I think adding a schema file to the module might fix this. I will test this and try to contrib a fix as time allows, but even if I write a patch, we can't apply it with the recipe. So any fix I might contribute, only fixes this saplings issue once the maintainer merges the fix.
So I think the best short term fix is to consider removing Publication Date from this recipe for now.
If we can get a fix into the stable release, we can add it back at a later time.
The text was updated successfully, but these errors were encountered:
Description
I first noticed this when using drupal-starter-installer with saplings to spin up the UCSF Psych site, but I thought/hoped it was a one-off glitch.
But now I see the same bug on UCSF OBGYN after using drupal-starter-installer with saplings. I don't see this problem on the Humane World site because it currently uses the legacy site's config rather than saplings config.
When the Publications Date module is manually enabled on a Drupal 10 site, the new "published_at" property gets added successfully to the node_field_date and node_revision_field_date tables in the database. This ensures there is a Published At input on the node edit form.
When the Publications Date module is enabled by saplings-content-types, the "published_at" property does not get created and the input on the front end is not displayed.
Bandaid
In order to repair Psych and OBGYN, I had to write the following update hook in a *.install file in a custom module. This update has to run on a deployment after and separate from the initial project deployment because it won't work on the same deployment that is enabling the Publication Date module.
Proposed Resolution
I suspect this is caused by a bug in the Publication Date module. I haven't validated this, but I think adding a schema file to the module might fix this. I will test this and try to contrib a fix as time allows, but even if I write a patch, we can't apply it with the recipe. So any fix I might contribute, only fixes this saplings issue once the maintainer merges the fix.
So I think the best short term fix is to consider removing Publication Date from this recipe for now.
If we can get a fix into the stable release, we can add it back at a later time.
The text was updated successfully, but these errors were encountered: