get Email thru Plugin API

[h1979pk]

Hello,

Can we get email address or custom field value thru plugin API like pb.data('user').email ?

Thanks

[Wormopolis]

custom profile fields you can (unless you are on posting page). but email addresses are not part of global data. and pb.data only applies to the member that is logged in. you cannot get a list of all the email addresses of all your members through javascript if that is what you are possibly after.

[h1979pk]

we are not after all email addresses of members. The members that will join board will be invited only, so we already have their email addresses. what we need the plugin to do is either get the email address of logged in person or value of a custom field of a logged in person. How can we get value of a custom field ?

Thanks

[Wormopolis]

all custom fields are available in pb.data('user').custom_fields[NAME OF FIELD]

but it looks like they are only filled when looking at posts. when viewing threads or looking at home, they apparently dont have values. not sure why that is though.

Tim Camara why do custom fields only have values when looking at posts? can that data just be made global all the time? can email be listed in proboards.data or would that violate privacy?

[h1979pk]

thanks Wormopolis, is there any way to get value of custom fields on all page?

[Wormopolis]

that would be why I asked Tim

[h1979pk]

I dont think he is gonna reply. Anyway thanks guys. We have decided to install our own forum.

[Wormopolis]

He is off on the weekends. He will be in at 9am on monday

[Chris]

I would venture a guess that the limitations on custom fields are actually a conscious decision and inline with other variables where it is present only where it is needed (in this case where profiles exist) and not unnecessarily included where it is not. That and the fact that custom fields are a free and effectively unlimited resource could make expanding its reach a poor business decision. A plugin key, on the other hand, is also capable of storing that information on a global basis but is rationed thus providing a better chance of generating opportunities for revenue, this is after all a business.

The privacy issue I don't think would be an issue if the user is actively filling in that information which would serve as a form of consent.

[Wormopolis]

I can consent to that. Though I still would like to see them available on the posting pages.

[Tim Camara]

Chris pretty much nailed it as far as it being a conscious decision is concerned. The reasoning behind it was actually entirely divorced from plugins, and is merely about trying to limit the amount of data overhead on every page load. Custom fields loading for every user that is loaded on every page could add a significant server load, so as much as we'd love to make every piece of data available everywhere, it's just not practicable. I can however see the argument for providing the current user's custom fields on the posting page, so I'll add that to our list (if it's not already on there somewhere).