Unbelievably we have filters just about everywhere in the code but NOT on the users email address! And really – rather than just saying hack the code I would much prefer to put a filter in place you could use – it’s not even too late to get that into the 5.2 release. At least by doing that you would not need to hack core code and would be protected from losing it on future upgrades.

So how about we put a filter in the subscriptions code and then I tell you name for the filer so you can out it in place and wrote your code and then when we release the next update it will still work?

Not sure to understand everything in your answer as english is not my native language, so let’s rephrase it to be sure.

I understand you can provide a clean way to do what I want using “filter” and you could give me the code of this filter in a “5.2 subscription”.

Where can I find the documentation to use filter ? In your codex ?

When will you be able to give me access to this code ? I can wait days but not weeks.

Well the fist place to look for documentation would be here – http://codex.wordpress.org/Plugin_API – as filters are a WordPress construct.

Basically it means you write a small function outside of SP and we provide the filter which can call your code and pass any information you need to manipulate – in this case, perhaps, the users ID and stored email address.

You then take that ID and your code does what it needs to do and returns the email address you want to be used.

The beauty of this is that there is NO core code changes to anything which also means that you can continue to update SP safely.

As I said – we do not currently have a filter on the email address being used but I can add one a any time enabling you to add it to SP code AND wrote your filter code and start using it straight away.

have a look at the documentation and let me know if you want us to do this.