Events Made Easy › Forums › Bug fixed or feature request implemented › Show pricing details from multiprice in RSVP emails
Tagged: multiprice, RSVP
- This topic has 15 replies, 3 voices, and was last updated 10 years, 11 months ago by Anonymous.
-
AuthorPosts
-
Tue 5 Nov 2013 at 14:21 #44088AnonymousInactive
While I see where I can get TOTALPRICE easily, is there a way to email out the details of what a user registered for? For example if there are two prices for seats and the user registers for 2 of one price and 1 of the second price, can I show that info in the RSVP emails?
Tue 5 Nov 2013 at 15:49 #50843FrankyKeymasterWell … apparently not. Moving to feature requests to be implemented asap. It shouldn’t be too difficult to create #_TOTALPRICE1, 2, 3, …. placeholders.
Tue 5 Nov 2013 at 16:17 #50844AnonymousInactiveGreat! thanks…
Tue 5 Nov 2013 at 22:43 #50845FrankyKeymasterimplemented in trunk:
Fri 13 Dec 2013 at 12:46 #50846AnonymousInactiveThanks for adding this feature, it is a nice addition.
I added this changeset and tried using it, but could not get the #_TOTALPRICEx to show the amount… instead I kept getting the value of the #_TOTALPRICE with the ‘x’ concatenated at the end. So if the total cost was $203, I was seeing $2031 for #_TOTALPRICE1, and $2032 for #_TOTALPRICE2, etc.
I also could not get #_SEATS to work but #_SPACES did, so that was great. I tried using #_SPACESx also to get the individual counts of the multiprice, but they also showed as above. (ie. if total #_SPACES = 5, then #_SPACES1 was showing ’51’.
Is there anything I have overlooked in making this change?
Fri 13 Dec 2013 at 12:51 #50847FrankyKeymasterNo, you’re correct: it’s a bug. That part of the code is fine, but the str_replace just below is causing the problem. I’ll need to resort to preg_replace for that as well.
Moving to bugs, hoping to fix it this evening.
Fri 13 Dec 2013 at 20:38 #50848AnonymousInactiveThanks Franky – I’ll check back later.
Fri 13 Dec 2013 at 23:12 #50849FrankyKeymasterSee if this solves it:
http://plugins.trac.wordpress.org/changeset/821551
(untested, please let me know the results)
Sat 14 Dec 2013 at 06:13 #50850AnonymousInactivehmmm, the #_SPACES1 was as before, showing “601” (if #_SPACES=60)
The #_TOTALPRICE placeholder is not returning the values, but rather repeating the placeholder name. In the email where I was getting $102 for “#_TOTALPRICE” and $1021 for #_TOTALPRICE1, now I am getting “#_TOTALPRICE” and “#_TOTALPRICE1”
Sorry for the news, hope that it is a simple fix from here.
Sat 14 Dec 2013 at 08:20 #50851FrankyKeymasterI only made the fix for #_TOTALPRICES, #_SPACESxx never existed (yet), #_RESPSPACESxx did.
This should now fix it for #_TOTALPRICESxx (easier fix than before):
http://plugins.trac.wordpress.org/changeset/821720
And this for #_SPACESxx:
Sat 14 Dec 2013 at 19:44 #50852AnonymousInactivehmm, I’ve checked my updating and it appears I have correctly transferred the changes, but now I am getting more errors.
My bad on not realizing that there was a #_RESPSPACES placeholder already – I would have used that. I did place it in my test email to try it, and it also exhibits the same problems as the #_SPACESx : for #_RESPSPACES1 it shows “601” (if #_RESPSPACES=60)
I am still not getting the values for #_TOTALPRICE or #_TOTALPRICEx, the text “#_TOTALPRICE” or “#_TOTALPRICE1” is showing.
The additional problems have cropped up here:
In the RSVP:mail, where I have ” #_EVENTNAME on #m #d, #Y. “
what I am now seeing is: ” MyEventNameArrayth on Array4 25, 2Array14. “
I also am now getting errors in the custom fields display in the emails.
I was getting the correct values for my formfields, but now here I use #_FIELDS in the rsvp email, I am getting::
“MY_Field Name: Array” instead of “MY_Field Name: 3”
I did notice that in changeset http://plugins.trac.wordpress.org/changeset/821720
on line 1144, it shows
#$placeholders = array(‘#_RESPNAME’ => $person, ‘#_RESPEMAIL’ => $person, ‘#_RESPPHONE’ => $person, ‘#_SPACES’ => $booking,’#_COMMENT’ => $booking, ‘#_TRANSFER_NBR_BE97’ => $booking, ‘#_TOTALPRICE’ => $total_price, ‘#_FIELDS’ => $field_replace );
which appears to be being commented out by the prior line. I tried removing the “#” at the beginning of the line, but to no avail.
Perhaps I made some mistakes on while making the edits, but I double-checked them all and I think I have it correct
So very sorry for the trouble here!
Sun 15 Dec 2013 at 12:49 #50853FrankyKeymasterI just got around to testing it here locally, so finally it works 🙂
#_TOTALPRICExx is working ok for me, but my last change created a bug for #_SPACESxx, which is now fixed by:
http://plugins.trac.wordpress.org/changeset/822426
But I don’t know on what base you started patching of course … eme_rsvp.php went through a lot of changes. So if you want all latest features, I suggest you get the latest dev version in a whole.
Mon 16 Dec 2013 at 00:13 #50854AnonymousInactiveThanks Franky, I will try this tonight when I get home, if I need to get the latest dev version, where is the best place to find this?
Thanks again for all of the efforts!!
Mon 16 Dec 2013 at 03:28 #50855AnonymousInactiveMine is still not working, but was there another changeset (besides 822426) in your last reply? If not, could you direct me to the latest dev version, as I want to make sure I get the right version at this point. Thank you!
Mon 16 Dec 2013 at 05:04 #50856AnonymousInactiveI used the version at the page bottom of 822426, and am getting a fatal error when trying to register:
Fatal error: Call to undefined function eme_transfer_nbr_be97() in …/wp-content/plugins/events-made-easy/eme_rsvp.php on line 596
where should I find the missing function?
Mon 16 Dec 2013 at 05:19 #50857AnonymousInactiveFOUND, in eme_functions.php
OK, yeah!! success – so far looks good!
I will test it some more, but I think we are there –
THANKS A TON!!!
-
AuthorPosts
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.