Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
The API key cannot be used in multiple places so if we use it on stager then, they can’t use it on live.
The best way to create test content on the live site is on an unpublished page.
Error:
Client error: `GET https://api.shorthand.com/v2/publish-configurations` resulted in a `409 Conflict` response: @"code":"DATA_CONFLICT",
"message":"Provided token is invalid, or has been removed."
#0 /site/vendor/guzzlehttp/guzzle/src/Middleware.php(65):
GuzzleHttp\Exception\RequestException::create() #1
/site/vendor/guzzlehttp/promises/src/Promise.php(204): [...]Proposed resolution
Set the display options for the 'Publishing status' field in the edit form.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | shorthand-publishing-status-3417860-3.patch | 722 bytes | natnatalia |
Comments
Comment #2
natnatalia commentedComment #3
natnatalia commentedAdded in the ShorthandStory entity class baseFieldDefinitions() the setDisplayOptions part.
Comment #4
natnatalia commentedComment #5
vladimirausThanks for contribution! 🍰
Keep in mind: shorthand story functionality is deprecated in 4.0 and will be removed in 5.0 in favour of shorthand field for all entities used in version 4.0.
Comment #7
vladimiraus