-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Token Replacement Doesn't Seem To Work #10
Comments
So there are 2 token replacements that take place. The debug more takes place after the 1st token replacement. I did this to simplify the debug code but looking back now It may make sense to move it into the connector so that way we can provide the completed url before we sent it to guzzle and we can also capture the response. I have pushed a update to the debug branch that should show you the fully replaced uri. If there is a still a problem with the token replacement let me know we can troubleshoot further. |
Awesome. I was also having trouble getting the tokens to actually work. If you have some time today, perhaps a quick video call will help me get on the same page. |
Token are working just need to add better documentation on how to use them appropriately going to track some documents in issue #22 |
I had a replacement string in my path...
I wanted to replace it with the node title or any other field for that matter and the debug shows this.
I suspect that this is not working right. It looks like to me it literally used
[node:title]
as the value of the string.The text was updated successfully, but these errors were encountered: