Author Topic: Store multiple versions of the token {domain.address} (Read 265 times)

Shai · November 17, 2014, 01:52:39 pm

Hi Folks,

The {domain.address} token is required for sending CiviMail.

I have a client where four sister organizations share the same CiviCRM installation. They don't need any of the functionality of the multisite extension except for being able to customize {domain.address} for CiviMail.

Their workaround now is to go to Administer => Communications => Organizatoin Name and Contact Info to change the org. address just before sending an email. But this is cumbersome and also makes scheduling emails problematic for fear that the value of domain.address will change between the time of scheduling and the time the email goes out.

Any better workarounds or other suggestions.

Shai

Michael McAndrew · November 18, 2014, 02:47:36 am

Hey there,

Multisite is obviously one way to approach this, but sounds like you are ruling it out (and I have no experience with it so wouldn't want to encourage you to use it)

One thought is that you might be able to use the token hooks (http://wiki.civicrm.org/confluence/display/CRMDOC/hook_civicrm_tokens, and http://wiki.civicrm.org/confluence/display/CRMDOC/hook_civicrm_tokenValues).

You could use them to overwrite domain.address with the address of the employer of the person that is sending the email (and maybe validate to ensure that this employer is valid, i.e. on of the four that you have mentioned).

The only thing I am not sure about is if you can use those hooks to overwrite existing tokens (I've only ever used them to define new tokens) but if that is possible, it might work for you.

Michael

Not sure if it is possible to overwrite

CiviCRM Community Forums (archive)

News:

Author Topic: Store multiple versions of the token {domain.address} (Read 265 times)

Shai

Store multiple versions of the token {domain.address}

Michael McAndrew

Re: Store multiple versions of the token {domain.address}