Thanks for reporting this! We are chasing a lead on this particular issue affecting you and a handful of other websites. As soon as we have confirmed what we believe to be the root cause, we will get a patch pushed accordingly. We are working diligently to get this resolved ASAP.
The issue with the CERN Landing Page only applies to websites moved directly from the old infrastructure (or new websites cloned from such websites) and is caused by database misconfiguration. If you create a new website today on the new infrastructure, the CERN Landing Page will not be throwing this error.
Er… it seems I need a Red Hat account and subscription to download the OpenShift console (I am following this procedure as I don’t have the console installed, it appears).
Is this something CERN already has - are there organisational credentials I can already use?
@joachim the drush command you mention above doesn’t seem to work on WLCG right now. Is it due to Drupal 9.3? Here’s what happens when I try running it:
/app $ drush config-set core.base_field_override.node.landing_page.uid default_value_callback
'Drupal\node\Entity\Node::getDefaultEntityOwner'
[error] Config core.base_field_override.node.landing_page.uid does not exist
In fact, there’s no configuration core.base_field_override.node.landing_page. There are other core.base_field_override.node.* settings.
Something has clearly changed since November when I wrote the above instructions as those were indeed what we used to resolve the same issue on different websites. I will have to look into this and get back to you both. As you have already submitted a ticket on the matter, @noble, I will respond on the ticket and here in case others face the same issue.
