Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
MarketingCloudSession cannot fetch a fresh token, because it is trying to fetch "requestToken_url". This does not exist, and should be changed to "request_token_url".
This is because recent changes to make marketing_cloud config settings standard and follow snake case have not been fully migrated to MarketingCloudSession.
Comment | File | Size | Author |
---|---|---|---|
#2 | marketing_cloud-MarketingCloudSession_requestToken_url-2974651-2.patch | 772 bytes | john_a |
Comments
Comment #2
john_a CreditAttribution: john_a as a volunteer commentedPatch created, please review
Comment #3
john_a CreditAttribution: john_a as a volunteer commentedReviewed and tested by self, using marketing_cloud_example.
Testing steps (these should have been included in the ticket description):
Expected results
drupal message
Message not sent - errors: 400 Bad Request
watchdog message
"Client error: `POST https://www.exacttargetapis.com/sms/v1/messageContact/<short_code>/send` resulted in a `400 Bad Request` response:@"errors":["No valid subscribers were provided."]"
The watchdog message would show that a valid token has been sent in the request, but then failed because the dummy mobile number is not a valid subscriber in Salesforce, and so returns a bad request error.
Actual result
drupal message
Message not sent - errors: 400 Bad Request
watchdog message
Fetching a new token.
"Client error: `POST https://www.exacttargetapis.com/sms/v1/messageContact/<short_code>/send` resulted in a `400 Bad Request` response:@"errors":["No valid subscribers were provided."]"
Message not sent - errors: 400 Bad Request
Patch applied cleanly and the results are as expected.
Comment #4
john_a CreditAttribution: john_a as a volunteer commentedpatch applied
Comment #5
john_a CreditAttribution: john_a as a volunteer commented