email (un)cloaking

krileon wrote:

Email cloaking can't be turned off in CB. It's always applied when raw email addresses are displayed. Is there a reason you want it disabled? Only way would be to use a Custom HTML field and substitute in the email address to bypass the cloaking.
 

A third-party booking system (Planyo) pre-fills its booking forms with the user's email address. Users registered on my site after a certain date (around when I installed CB), get @ replaced with [at] in this field. CB email cloaking seems the likely cause.{Note 1}

If I'm right, can I prevent this at the CB end, and if so how?
The booking system uses the email address to confirm bookings, send out reminders, lock codes, etc. So I'm hoping CB can somehow be asked to distinguish between access for "use" vs for "display".

I have very little control over the 3rd party module, so fixing this at the CB end would be highly preferable.

___________
{Note 1}: I disabled the Joomla "Content - email cloaking" plugin a couple of months ago. And to prove it's not a hang-over from when each user's account was registered, even a test user registered today suffers this @ substitution.

Self-help attempts: 

• I've searched for a sample [at] address in my Joomla database (with PHPAdmin) and not found any. So this substitution is happening live. 
• I've tried re-enabling Joomla email cloaking in the hope that it will be used in preference (in which case I might be able to use its controls), but that doesn't seem to be the case.
• I've searched for documentation on CB cloaking, so far without success.

I don't see how email cloaking could have anything to do with your 3rd party extension or the [at] replacement. That's not how email cloaking works in CB. In CB it only happens to the profile display of the email field and it's just replacing the email at document render with JavaScript. CB also doesn't store the email address it. It's stored in _users so 3rd party extensions don't need access to CB or have to use CB API to use it.

I don't see how your issue could be coming from CB unless your 3rd party extension is using CB API to get the email field and they're getting the profile display value of the email field instead of the raw value of the email. I can't think of any other possible way for CB to be the issue here. Have you tried contacting the developer of your extension to see how they're getting email address?