How should you use tokens when you have multiple nodes?
It works when I have one node id, but when there is an array or multiple node id's it doesn't work.

Thanks!

Comments

wizonesolutions’s picture

Version: 6.x-1.6 » 6.x-1.x-dev
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

1. Does it work in the development version?

2. If no, what does your Fill PDF link look like and what token are you trying to use?

sydkoh’s picture

Version: 6.x-1.x-dev » 6.x-1.6
Category: support » bug
Status: Postponed (maintainer needs more info) » Active

My question above relates to custom path for pdf's that are created... i put it in the title but just wanted to clearify.

sydkoh’s picture

Here is the link: http://plprov2:8082/fillpdf?fid=75&nids[]=30&nids[]=1&nids[]=8&nids[]=9&nids[]=10&nids[]=18&nids[]=29&nids[]=&flatten=0

For instance if the token is [title] it pulls from nid=1
If the token is [field_bind_f1-formatted] which is uniquely from nid=75
the custom path = Policy/[field_bind_f1-formatted]

wizonesolutions’s picture

Version: 6.x-1.6 » 6.x-1.x-dev

Multiple nids are a bit weird IIRC. I think it only checks the last one you pass, which in this link is actually blank. I'll check the code when I get a chance and let you know. But avoid them for now if possible.

sydkoh’s picture

thanks! By the way... can i contact you for some "on the side" work?

wizonesolutions’s picture

Yeah, I can at least check if I have time. https://fillpdf-service.com/contact

wizonesolutions’s picture

Title: Custom Path/Tokens For Multiple Nodes » Multiple tokens should aggregate the latest non-empty values from among the nodes/webforms
Version: 6.x-1.x-dev » 7.x-1.x-dev
wizonesolutions’s picture

Issue tags: +Needs tests, +fillpdf2

Check this during refactor.

wizonesolutions’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
wizonesolutions’s picture

Version: 7.x-2.x-dev » 7.x-1.x-dev
Component: Web Service » Code
Issue summary: View changes
Status: Active » Closed (won't fix)
Issue tags: -fillpdf2

No patches for this, so going to wontfix. Will look at this in the next version, though (along with tests).