When I go to "checkout completed page" I get Notice: Undefined index: path in token_tokens() (line 762 of /sites/all/modules/token/token.tokens.inc).
and the "checkout completed" message looks like html message with plain_text filter - html tags are rendered as .
As far as I see, there are two issues here:
1) there is no "commerce-order:url" token
2) commerce tries to load unexisting filtered_html format and the falls back to plain_text, which breaks html in completion message
when I created filtered_html input format, the message looks better, but the link to "view your order" still leads to website front page, so I guess we need to implement url token in commerce_order.tokens.inc ?
also, I think that there should be a warning that filtered_html format is required for correct message rendering.
Comments
Comment #1
xibun commented+1
Comment #2
rszrama commentedThis is a duplicate of #1280608: Commerce with the "Minimal installation profile" and a couple others. I thought I documented this as an FAQ, but apparently it's just an unpublished blog post. I'll move it over to dc.org ASAP. Not sure why the Token module is being invoked, though. Those tokens should work independent of the Token module. Could be that's why your tokens aren't working.
Comment #3
restyler commentedthanks for quick reply.
I'm not sure that I understand what I should do with tokens issue.
Comment #4
rszrama commentedI'm not either - it's a separate issue, and perhaps it's an unintentional conflict between Rules / Token, but I'm using Token just fine on a personal store. I suspect there's something else going on, so if you can trace that down, feel free to reopen / repurpose this issue.
(The best thing to do is reproduce the error on a clean installation of Commerce Kickstart with whatever contribs you need to reproduce it. With the step-by-step, we can then get a site in the same broken state and try to fix it. Otherwise it's impossible to debug.)
Comment #5
finex commentedHi! I'm experiencing the same problem of @restyler. I've changed the text format from "plain text" to "full html" and the problem has been solved.
If you don't enable the "custom message" you cannot change the text format and probably commerce assume to use the "plain text" format.
Comment #6
finex commentedComment #7
rszrama commentedI'm still not sure we should reopen this - what you've done is basically the solution. Alternately you can change it to a custom message and just remove the HTML but leave it as a plain text message. If you have thoughts on how to improve this, feel free to open a separate feature request.