I will create a page "email" containing info vars like:
"[email protected]: myID"
so, e-mail->id: {email:[email protected]}
and id->email: {~myID:email}
I can easily write a plugin (or just the function myself) if I needed
it. If strpos for @ returns a positive number, convert to ID,
otherwise, convert to E-mail.
conversion would be something like stripping out the @ and dot (.), or
replacing them bij _at_ and _dot_ or something.
Thanks for the help,
Mark
On Aug 3, 3:30 pm, The Editor <[email protected]> wrote:
> I think you have the situation assessed pretty well. Having a simple
> conversion routine from a standard email address to some kind of
> encoded format and then back might work the easiest. You would simply
> want a command/function that encodes/decodes. I have a script
> somewhere that will transform an email into a string of numbers.
> Perhaps you could use that. I'll see if I can't find it...
>
> Though it is possible to change the chars allowed in page names, there
> is not really much wiggle room in BoltWire, with all the utf issues,
> and the page shortcuts and the like. And hierarchies. Actually, I
> think it might just as well be a good idea to strip out that
> capability, as just about any changes you make to it are going to
> cause problems somewhere.
>
> I'll have to wait till later to get to my regular computer to find the
> encode/decode plugin. I don't see it on the BoltWire site. Maybe that
> will work for you. It's a good idea...
>
> Cheers,
> Dan
>
> On Mon, Aug 3, 2009 at 7:12 AM, Mark
>
> Marijnissen<[email protected]> wrote:
>
> > On my site, what is unique about each member their e-mail. They can
> > have the same member names, etc.
>
> > I really want that the BOLTid and the e-mail are the same, because the
> > BOLTid is used to identify members and to store information that is
> > coupled to them.
>
> > I could, of course, use another unique BOLTid. I can easily retrieve
> > the e-mail with {~id:email} and I can retrieve the ID with an e-mail
> > using a search, or perhaps keep a special list somewhere. While this
> > already takes some extra effort that is a bit clumsy, I have a bigger
> > problem: I need to store information coupled to certain e-mail
> > adresses of member that have not even registered yet! I could
> > automatically register when some information with that e-mail needs to
> > be stored... The registering only couples the BOLTid and e-mail. But
> > that gives me trouble when the person with the e-mail tries to
> > register: account already exists. (Of course, i can modify the
> > BOLTXregister to deal with that).
>
> > As you can see, lots of trouble.
>
> > All of this would be solved if the BOLTid and e-mail were simply the
> > same. All information just gets stored (on other pages than "login*"),
> > and when someone registers, a "[email protected]" is created with
> > the register-information, and the registrant has acces to all the
> > information he/she needs.
>
> > Unfortunately, boltwire does not allow @'s in the pagename (or it
> > converts them to "group"). And dots (.) delimit pages. How can I
> > escape this behavior for the login* pages? I have a custom BoltWire
> > application, so I can do anything. I tried altering the "$pageArray"
> > and removing the "@" shortcut - but I got into trouble with links,
> > since e-mail adresses in a link get automatically converted to a
> > "mailto:"; link.
>
> > Maybe I should replace the @ and . with something else? This way, e-
> > mail and ID are not the same, but easily converted into eachother...
>
> > Any suggestions, tips, help with this? Thanks a lot!
>
> > Cheers,
> > Mark
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
