|
Paul de Groot
|
January 15, 2016 at 6:50 pm
Hello,
When I insert a [PRIMARY_REGISTRANT_ANSWER_*XXXX] field in the invoice template it does not show on the invoice output.
This is the code:
<h2>Bill to:</h2>
<div id="client-details" class="vcard">
<div class="fn">.[PRIMARY_REGISTRANT_ANSWER_*INSTELLING].</div>
<div class="fn">[PRIMARY_REGISTRANT_FNAME] [PRIMARY_REGISTRANT_LNAME]</div>
<div class="adr">
<div class="street-address">[PRIMARY_REGISTRANT_ADDRESS]</div>
<div class="street-address">[PRIMARY_REGISTRANT_ZIP_PC] [PRIMARY_REGISTRANT_CITY]</div>
<div class="street-address">[PRIMARY_REGISTRANT_COUNTRY]</div>
</div>
</div>
I inserted the dots around the field to make sure I was editing the correct template. The dots do show on the invoice, but my custom field remains invisible. It does not matter which question field I choose. I am only able to succesfully insert the standard (system) fields from the selection list.
Version 4.8.30.p
Hope you have a suggestion.
|
|
Josh
|
January 16, 2016 at 8:33 am
Hi Paul,
Is the question name actually typed out in all caps? If not, the shortcode should be typed out as:
[PRIMARY_REGISTRANT_ANSWER_* Instelling]
The question in the shortcode needs to be an exact match of the question text. You’ll note the use of a space in the above shortcode between the * and the question name as well.
|
|
Paul de Groot
|
January 16, 2016 at 6:58 pm
Hello Josh,
Thanks for the quick reply!
Yes I created the field with all caps. I have tried the shortcode with and without the space but it did not help.
Meanwhile I found out that this behaviour also occurs in all other templates on my site. I tried to simulate this on the demoee environment, but (luckily) there it works as it should.
I use a standard clean installed (up-to-date) WordPress 4.4.1 installation with the basic WordPress Twenty Eleven theme. I have disabled all other add-in’s. No luck. I have changed back to the standard WordPress theme, also no luck.
If you have another quick and simple suggestion let me know. If not I think I reinstall WP and EE just to clear whatever is bugging me ;-).
|
|
Tony
|
January 18, 2016 at 6:32 am
Hi Paul,
Can you enable the Invoice payment method so I can use it to finalize a couple of test registration please?
Event Espresso -> payment methods -> Invoice -> Activate invoice payment method.
|
|
Paul de Groot
|
January 18, 2016 at 6:50 am
If you choose the second ticket you can use it for registration, there is no payment needed (free ticket).
|
|
Tony
|
January 18, 2016 at 7:21 am
I was trying not to take any places within the event, which a free ticket will 🙂 but I’ve registered onto the free ticket.
Your shortcode should be:
[PRIMARY_REGISTRANT_ANSWER_*Instelling] (A space at the beginning/end will be trimmed)
Can you go to Event Espresso -> Registration form.
Edit the ‘Instelling’ question and confirm there is no whitespace before/after the text (EE should remove that but I’d just like to double check)
|
|
Paul de Groot
|
January 18, 2016 at 7:30 am
Hi Tony, no worries the site has not been made public yet. But will need to go live in a few days. I checked for the spaces, but they are not there. As I mentioned before I do have this problem with all custom fields in other messages. For example they also do not show in the ticket. My custom ticket should display 2 fields under the name but they remain blanc.
|
|
Tony
|
January 18, 2016 at 7:40 am
I understand, however if we find the cause on one of those field it will likely be the same cause for all as they are all pulled in from the DB in the same way regardless of the message type.
Can you send me temporary login details so I can take a look at the template please?
You can use this form to send the details: https://eventespresso.com/send-login-details/
|
|
Tony
|
January 18, 2016 at 8:22 am
Ok, I can see the issue.
The dynamic shortcodes within the messages system, such as the ANSWER_* shortcodes pull in the question based on the ‘Question Text’, not the ‘Question Label’ fields.
So in the case of the Instelling question, it needs to be:
[PRIMARY_REGISTRANT_ANSWER_*<strong>Instelling</strong>]
Because you’ve added the HTML to the question text – http://take.ms/9kecp
The text after the _* must match the question text field, exactly. So any question you have HTML within the question text, needs to use that question text within the shortcode.
|
|
Paul de Groot
|
January 18, 2016 at 8:54 am
Hi Tony, This indeed solves my problem.
I did not expect the field to be pulled from the question text.
Unfortunately I had to use the HTML to add descriptive texts for some of the fields 🙁 Maybe EE could consider adding the option for a description and also the ability to select a default value to the question fields?
Thanks for your help!
|
|
Lorenzo Orlando Caum
|
January 18, 2016 at 11:22 am
Hi Paul,
We have two enhancement tickets open including explanatory text (e.g. help text) and placeholder text (sample text that appears within the form fields but disappears as you enter new information).
I’ll add additional feedback to both as I do think these would be helpful.
—
Lorenzo
|
