I have tested this QR field type with a couple different tokens which seem to work (just shows the code), nowever NID does not work. Do you have any suggestions on how to pass the node being created NID into the url for the qr code? Full path wont work, I need the actual NID. Thanks

Comments

stangslvr created an issue. See original summary.

borutpiletic’s picture

StatusFileSize
new75.59 KB

@stangslvr
Can you provide more information on where you are having this issue?
If you added QR field to your content (as a configuration field) than "nid" should be available to you because fields attached to the content type are aware of the content context.

See my attached image.

If you used the QR field as a block, then, unfortunately (currently) it does not support the "current node context", so this could be a feature request.

borutpiletic’s picture

Status: Active » Closed (works as designed)
greg.1.anderson’s picture

Title: Token issues for NID » Fix Token rendering for [node:...] and other entity keys
Status: Closed (works as designed) » Needs review
StatusFileSize
new740 bytes

I also discovered that [node:...] token replacements were not working in this module. The problem stemmed from a simple typo; fix attached.

borutpiletic’s picture

Thank you for the patch, looks good!

  • greg.1.anderson authored 11eceac on 1.x
    Issue #3156229 by greg.1.anderson: Fix Token rendering for [node:...]...
borutpiletic’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

borutpiletic’s picture

Status: Closed (fixed) » Fixed
borutpiletic’s picture

Status: Fixed » Closed (fixed)