using a custom field in URL

Hi there @richardhopkins,

Just to clarify, it looks as though the link to the custom field is still valid, but the issue is that the HTML coding to turn that link into a clickable <a> tag is what is broken, is that correct?

Can you share a little more detail about which block you are using in your newsletter to add that link? How is it generated?

Screenshots of your designer screens are always helpful as well!

Lynn, Thanks for the response – I am not able to reply properly for a couple of weeks

Hi again @richardhopkins,

Thanks for letting us know. This thread will remain open and you can share the additional information with us when you are able.

Hi
I have now investigated this issue more fully than I did for the original post.
Back in November I did a mailout where the source text contains the definition of a link –
<a href=”https://simple-registry.greenhawick.org/scdt-event/?pid=%5Bsubscriber:cf_20%5D”>Click here</a>
Of course the pid=[subscriber:cf_20] identifies a custom field which is set up to contain a database key for each subscriber
In an email mailed out back then the generated link yielded the webpage with URL –
https://simple-registry.greenhawick.org/scdt-event/?pid=0QBA9IU&utm_source=mailpoet&utm_medium=email&utm_campaign=silverbuthall-cdt-notification-of-agm-23rd-nov-63
As expected/intended- the source [subscriber:cf_20] has been replaced by the value 0QBA9IU giving the URL which ties into the recipient’s database record; allowing them to update their record.
Now, apparently due to a change in the MailPoet implementation, doing the exact same thing, rather than the above generated URL, I get the generated URL as being –
https://simple-registry.greenhawick.org/scdt-event/?pid=%5Bsubscriber%3Acf_20%5D&utm_source=mailpoet&utm_medium=email&utm_source_platform=mailpoet&utm_campaign=silverbuthall-cdt-notification-of-agm-23rd-nov-63

I.e. the ?pid= … seems to have the source custom-field identifier rather than the value of that field (which obviously does not tie into the required database record)
Is this a MailPoet bug or is it a feature?
Is there anything to be done about this?
I think this is now clearer enough that screenshots would not be needed; if there are specific screenshots that would be helpful for you – I can do that.
By the way, I am again out of email contact from 12th – 19th April, so if you reply during that period I will not be able to repond until my return.

Hello again @richardhopkins ,

Thank you for your detailed message describing the issues you’ve been encountering with generating custom links in your email campaigns using MailPoet.

Your description of the problem is clear. To properly address this situation, we may need additional details to better understand the context, and troubleshoot this issue effectively. If you can provide answers to the following questions, it would be incredibly helpful:

1. Did you recently update your MailPoet plugin? If so, what version did you upgrade to?
2. Did this issue only start happening after any particular update?
3. Can you confirm whether the issue persists for all subscribers or only for specific ones?
4. How did you create said custom field(s)?

Looking forward to hearing back from you.