@Upchuk

Indeed, there is this hash validity configuration but the problem is that it's general, used both for removing and adding subscriptions.

IMO, for removing subscriptions (i.e. unsubscribing) we shouldn't construct hurdles for users to unsubscribe.

So I made a patch that does a check for this and only checks for the hash validity if the action is not to remove.

Here you go. Are there no tests running?

upchuk → created an issue.

Renaming to patch :)

MR 8619 patch attached that applies on 10.3.

Hey there,
For the sake of simplicity, I think better to leave it granular. It's also more clear.

Thanks

Ah, wrong file name.

Here is a patch that does a check before trying to move the file.

Upchuk → created an issue.

@znaeff, hello, no, the solution cannot be that I give you access to my site. It happens on multiple sites, on multiple local environments, and it didn't use to happen. that's 1,

and 2, maybe you can explain what the purpose of that check is there? What does it mean?

Upchuk → created an issue.

penyaskito → credited Upchuk → .

Here's a quick patch that does this. So now the token can return a comma-separated list of values and EPP can explode them and set them onto the field.

Upchuk → created an issue.

Sorry everyone, this tiny module was not really on my radar anymore. @bletch, I made you maintainer. Thanks for the help!

D

hey there,

Any movement on this for a review perhaps?