Springshare is deprecating the URL pattern we have used previously when loading their javascript-based chat integration. The new URL pattern makes use of our custom doman name, rather than a generic domain across all customers.
This updates libchat.js in the parent theme to use the new URL pattern
The theme version is bumped because of this change, to 1.13.2.
** Document any side effects to this change:
I'm choosing to include the https protocol now, rather than the protocol-agnostic // prefix. The Springshare documentation uses the protocol in their examples, and it seems safe to explicitly call for https at this point.
Status
Use labels (review needed, in progress, or paused) to declare status
What does this PR do?
A few sentences describing the overall goals of the pull request's commits.
Why are we making these changes? Is there more work to be done to fully
achieve these goals?
Helpful background context (if appropriate)
How can a reviewer manually see the effects of these changes?
** Why are these changes being introduced:
** Relevant ticket(s):
** How does this address that need:
** Document any side effects to this change:
//prefix. The Springshare documentation uses the protocol in their examples, and it seems safe to explicitly call for https at this point.Status
Use labels (
review needed,in progress, orpaused) to declare statusWhat does this PR do?
A few sentences describing the overall goals of the pull request's commits. Why are we making these changes? Is there more work to be done to fully achieve these goals?
Helpful background context (if appropriate)
How can a reviewer manually see the effects of these changes?
What are the relevant tickets?
Screenshots (if appropriate)
Todo:
Requires new or updated plugins, themes, or libraries?
NO
Requires change to deploy process?
NO