I understand and appreciate you taking the time to respond here. Our scenario is pretty simple, when a node is added we generate email to the subscribed users and in the email we need a link to that node. We're using DANSE to generate the events and Push Framework to handle the notifications. [current-page:url] renders a link to the cron admin page (https:///admin/config/system/cron).
is what appears in the token browser in the Push Framework admin. It seems like push-object is the only thing that refers to an object with a url but it's not the node.
If there's any more guidance you could provide that would be great, I understand if not and thank you.
Ok, so it sounds like there currently there isn't a way to include a link to the entity that generates the notification. [node:url] does appear to be what we'd want, how would we go about adding it to the token service?
I tried using [node:url] but it doesn't render the link. Is there something we need to do to enable it to be rendered? [current-page:url] does render the link to cron so I'm not sure why [node:url] doesn't work.
So by default private files are not accessible, even to admin?
Thank you, running the prohibits command (I was not familiar with that one) showed there was a module that was preventing the core update to 10.3.x. I updated that module and then was able to complete the core update. Thank you very much, the issue is resolved.
hi @sundhar,
I was able to resolve the issue... the view in question was dependent on a module that I hadn't set up on the site being migrated to. Once I installed it I was able to run the views migration successfully. Thank you for your response!