Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It is currently possible to manually set the `content_origin` for Lift credenials in settings.php
$config['acquia_lift.settings']['credential']['content_origin'] = '1c98ab71-96bb-43cf-4909-81b7f4fbc868';
However, I think it might be better to make us of Drupal's great configuration system.
I suggest we add `content_origin` to the admin settings form so that user can easily update, export and deploy this settings.
I've added a patch for review.
Note: for those who don't know, the `content_origin` credential is used to filter content by site UUID in Lift Experience Builder.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 0001-Add-content_origin-credential-settings.patch | 3.2 KB | matthieuscarset |
Comments
Comment #2
matthieuscarset commentedPatch was missing a line.
I've reupload it.
Comment #3
matthieuscarset commentedComment #4
ynx commented@matthieuscarset Thank you for the patch! I think the "content origin" was intentionally skipped from form; the intended use was just Drush variable set. Let me check with the Product Owner before merging.
Comment #5
matthieuscarset commentedThere was a typo in my patch.
Issue was in the form validate function. I was setting an error if the site UUID was valid (which was supposed to be the contrary).
I re-upload the patch.
Sorry about that :)
Comment #6
matthieuscarset commented@ynx any news from the Product team?
Comment #7
ynx commented@matthieuscarset thank you for the follow up! Product confirmed that It's a great addition to the UI and we have a ticket in the backlog to implement. We are still to determine where the option should be (possibly not with the rest of credentials), but once in development, it's just use your code, slightly move things around, and then add a test for it. I will be very surprised if our next acquia_lift module release does not include this UI feature.
Comment #8
ynx commentedI have applied the patch, and brought in other required changes. Noteworthy ones:
1) Content Hub Site UUID is not Drupal site ID. This is because we are to identify different sites although people copy their databases around.
2) Added required schema definitions, etc.
3) Added unit and functional tests.
4) Other misc changes.
Will go out in next release. Thank you again @matthieuscarset.
Comment #9
ynx commentedComment #10
ynx commented