You don't need to test anything or update anything for this issue, we are still waiting for decision from our developers, after that, we will update it our document or apply this featurewithout id=”%%POST_ID%%” attribute) in the future (version of Toolset form plugin.
Your existed codes id=”%%POST_ID%% attribute will work in future version of Toolset form plugin too.
And I have marked this thread into "Escalated" status, will update here if there is anything news.
Sorry, that post is my mistake, and I did not clarify it.
I don't feel the documentation has been updated to clearly explain the need to specify the post id - the documentation you've linked to is about post expiry - my original question had nothing to do with post expiry and the documentation update I requested had nothing to do with post expiry either.
The original question of this thread:
https://toolset.com/forums/topic/body-code-placeholder-post_link-output/#post-1114882
It doesn't return anything when used in notifications sent based on a post's expiry date.
And you have confirmed it here:
https://toolset.com/forums/topic/body-code-placeholder-post_link-output/#post-1116919
Can you confirm it again?
You are right, I have checked it in our to-do list, here is feedback from our 2nd tier supporters:
When Notifications are deferred either by expire or post status change, then both Views and Types fields will not return any result if no ID is passed.
To fix this you need to pass an ID, populated with the placeholder of Forms, for example:
[wpv-post-title item="%%POST_ID%%"]
It is waiting for "our developer's confirmation" status, after the confirm, then it will be put into our document.
And I have changed this ticket to "Escalated" status, will update here if there is any news.
