|
Matthew Farrand
|
May 7, 2014 at 3:19 pm
WordPress Version: 3.9
PHP Version: 5.4.14
MySQL Version: 5.0.96
Event Espresso Version: 4.2.0.reg
We’re having lots of challenges w/ the new message system:
1. Finally realized that the [Event_List] field loads on the Visual tab, and we have to click the Text tab to edit. Not sure what the deal is w/ “Main Content.” Can this be set to load in the Text tab by default in a future update?
2. Would really like to use all short codes in all fields. For instance, I want to include [EVENT_NAME] in the subject line. This limitation is really frustrating.
3. In v3, it was really easy to send confirmation emails to an alternative email address for each event. This was useful for us since most of our “event coordinators” are volunteers and NOT the [EVENT_AUTHOR_EMAIL]. I realize that I can use a custom template for each event that can be addressed to the event coordinator, but it would be nice to have a short code for additional emails in the global TO field. Could this be added using [ALT_EMAIL] or other custom field?
4. Can the custom message template start w/ the global message template? Most of my custom message needs are slight modifications of my global setup.
Thanks!
|
|
Matthew Farrand
|
May 7, 2014 at 3:44 pm
I vote that you BAG the entire multi-field message building system and let me build the messages in the MAIN CONTENT field only. Or, at the very least, let me use all the short codes in the main field so that I can elect to ignore the other fields and just build in one.
Can you please explain the reasons this convolution is necessary?
|
|
Matthew Farrand
|
May 7, 2014 at 4:01 pm
The test emails don’t seem to match the edits I’ve made to the templates…
|
|
Matthew Farrand
|
May 7, 2014 at 9:57 pm
Ok, I’ve figured out why the test emails were wonky.
However, I still have two MAIN challenges I can’t seem to figure out:
I really, really don’t want to have to make a custom message for each event just to send to an alternate email address.
I can’t get the [PRIMARY_REGISTRANT_EMAIL] to show up in the content of the email no matter what I try.
I’ve currently got this inside the [Event_List] field:
[PRIMARY_REGISTRANT_FNAME] [PRIMARY_REGISTRANT_LNAME]
[PRIMARY_REGISTRANT_EMAIL]
The name fields come through fine, but the email is null every time… even when I complete the registration form w/ a good email addy in the field.
Any ideas?
|
|
Matthew Farrand
|
May 8, 2014 at 8:10 am
Bump on that last one. Really struggling w/ getting the [PRIMARY_REGISTRANT_EMAIL] to appear in ANY content field of the message.
|
|
Tony
|
May 8, 2014 at 10:48 am
Hi Matthew,
Thank you for the feedback, I have made a note of your points and would just like to add we are currently working on simplifying the Messages Interface but this will results in losing a lot of the current flexibility within the system, so we need to find a balance.
1) The EVENT_LIST and Main Content areas should load on the Text tab by default.
2) I’ll add this to a ticket for review.
3) Not currently, as you correctly mentioned this would need to be via custom templates.
4) With EE 4.2 the message is created from the default of that message type. The new system UI works slightly differently so should accommodate this better.
Regarding [PRIMARY_REGISTRANT_EMAIL] I can confirm this shortcode parses only within the Main Content area currently. I believe this to be a bug so I have issued a ticket for the developers to investigate.
|
|
Matthew Farrand
|
May 8, 2014 at 11:21 am
Hey Tony, thx for your reply.
Obviously, I had a bit of a tough night w/ this stuff, so sorry for all my followup posts. I think I’ve got workarounds figured out that will get us through the current registration cycle. I appreciate the effort you’re putting in to strike the balance between simplicity and robust features!
Thanks for starting a ticket re: #2 and the [PRIMARY_REGISTRANT_EMAIL] bug.
Can I make a feature request for #3? Or maybe support of message short codes for custom fields?
Thanks again!
|
|
Tony
|
May 8, 2014 at 1:05 pm
No Problem.
Can I make a feature request for #3? Or maybe support of message short codes for custom fields?
Sure, I’ll add this to the feature request list, however as we are currently changing the UI, the new system may address this or if it is to be added it would likely be added there although I can not say for sure as that will be up to the developers.
I’m glad you found some workarounds for your current event 🙂
|
