Opened 11 years ago

Last modified 6 years ago

#620 assigned Bug/Something is broken

Welcome E-mail is confusing for * subdomains and other already-transferred domains

Reported by: Daniel Kahn Gillmor Owned by: Jamie McClelland
Priority: High Component: Outreach
Keywords: welcomeemail Cc:
Sensitive: no


I just got the welcome ticket that closes #618. Thanks!

It's a little confusing, though: i requested the domain (which was granted), but the welcome mail says:

Your web site address is:

If your domain name is not registered or you have not transferred
your domain to the May First/People Link name servers, you can
access your web site via:

Isn't this information discoverable at the time that the e-mail is generated and emitted? If it is, shouldn't this e-mail be adjusted to display the relevant information? At the very least, subdomains of (and should be treated differently.

I imagine (at least) two different forms of this e-mail, based on whether the domain has been registered, and whether the nameservers for it already point to the MF/PL nameservers.

I think this sort of change would make our initial welcome message to new members less intimidating, which can help people feel more in control of the tools they use.

Change History (7)

comment:1 Changed 11 years ago by alfredo

LOL Oh man. One of the great obstacles we've had in our development has been our handling of sites that aren't "www". We have most of it right but there have been a few bugs that have arisen, especially in the Drupal set up script.

This clarifying language you're suggesting would be very useful. I think some work on our automatic email script could do this and ticket #622. A couple of filters in the posted variables and a simple line added with the "server" variable that's in the hosting order already, after all.

What do you think, Jamie?

Good looking out, my brother! :-)


comment:2 Changed 11 years ago by Jamie McClelland

Yes - those changes would be an improvement. Most members join with a domain name - so the two links would be different (avoiding the most confusing aspect). However, it would be a simple check.

And checking to see if a domain name is under our control would be fairly simple as well.

Thanks for the suggestions.

comment:3 Changed 11 years ago by alfredo

Owner: changed from alfredo to Jamie McClelland

comment:4 Changed 6 years ago by Daniel Kahn Gillmor

Owner: changed from Jamie McClelland to Daniel Kahn Gillmor
Status: newassigned

comment:5 Changed 6 years ago by Daniel Kahn Gillmor

Owner: changed from Daniel Kahn Gillmor to Jamie McClelland

I'm not sure how to approach this, since the templating approach used by red doesn't have any conditional logic in it. jamie, can you propose a way to do this cleanly? I'm happy to implement it, but i'd like to keep red relatively internally-consistent, and i don't see that happening with the current templating approach.

comment:6 Changed 6 years ago by Jamie McClelland

Priority: MediumHigh

comment:7 Changed 6 years ago by Dana

Is there an update on this, it's been a while since the last response.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.