|
Matt
|
January 11, 2015 at 3:02 pm
I am using the price modifier and it is working OK – but is there an easy way to find out how many options are remaining?
If I “edit” the question where I have placed the options then I can see a box where it says:
“Price modifier items sold”
But there are no figures in there, so where can I see the number sold?
|
|
Matt
|
January 12, 2015 at 8:09 am
Any help available with this?
|
|
Matt
|
January 13, 2015 at 3:18 am
Still waiting for help on this. Why are you ignoring it?
|
|
Dean
|
January 13, 2015 at 6:26 am
Hi Matt,
This issue should have been fixed in Price Modifier 0.0.5.b, but it looks like it has re-occurred for some reason. I will raise a developer ticket to look into the issue.
Please know that we are not ignoring you, we try to respond to support queries as fast as possible.
The support team does try to resolve support queries from oldest to newest (we don’t always succeed, but that’s our aim), so “bumping” a thread will generally get the thread knocked to lower in the queue and therefore take longer to respond to.
|
|
Matt
|
January 13, 2015 at 9:38 am
Thanks Dean.
Another issue that has just cropped up…
A customer has tried to edit their details and add one of the options that would mean an extra cost. He hasn’t been prompted for payment and the system hasn’t recognised the question updating?
|
|
Dean
|
January 15, 2015 at 6:58 am
Ok, thanks for that I’ll get a ticket raised for it as well.
|
|
Dean
|
January 20, 2015 at 8:48 am
Hi Matt,
Regarding this issue, it does actually work.
What needs to happen is that the the sold field needs to also be pre-populated with the questions|value pair.
E.g. if you have a question with the answers Chicken|10, Steak|10, then in the sold you would put Chicken|0, Steak|0 and these will increase as the items are sold.
|
|
Matt
|
January 20, 2015 at 9:07 am
OK thank you.
Maybe this could be made clearer in the documentation?
If I make the fields to what has currently been sold, will this work?
Any idea on the other issue:
“A customer has tried to edit their details and add one of the options that would mean an extra cost. He hasn’t been prompted for payment and the system hasn’t recognised the question updating?”
|
|
Josh
|
January 21, 2015 at 1:56 pm
Hi Matt,
We’d be more than happy to consider any ideas to make the documentation more clear. If you have any suggestions to edit the following, please let us know:
This field will track how many price modifer items have been purchased to date.
This field will be adjusted automagically as items are purchased during registration, but can also be modified manually here, in a similar fashion to above where the number after the pipe represents the number of price modifer items that have been purchased.
Eg. If 15 Steak Dinners, 10 Chicken and 2 Vegan dinners had been purchased so far, then this field would display: ” steak|15, chicken|10, vegan|2″
If they go back to try to edit details and the price does not automatically update, can they try a new registration?
|
|
Matt
|
January 21, 2015 at 2:05 pm
Josh, I would add a line at the bottom something along the lines of:
This field will track how many price modifer items have been purchased to date. In order to function this needs to be pre-populated. e.g if starting with no tickets: steak|0, chicken|0, vegan|0.
This field will be adjusted automagically as items are purchased during registration, but can also be modified manually here, in a similar fashion to above where the number after the pipe represents the number of price modifer items that have been purchased.
Eg. If 15 Steak Dinners, 10 Chicken and 2 Vegan dinners had been purchased so far, then this field would display: ” steak|15, chicken|10, vegan|2
As for the new registration, this would not work.
We are selling entries with add-on products, the add-on isn’t available as a separate item.
|
|
Josh
|
January 21, 2015 at 2:19 pm
I’m not sure I understand why re-registering in order to get the add-on would not work. Why’s that?
|
|
Matt
|
January 21, 2015 at 2:20 pm
They would need to purchase the ticket again?
|
|
Sidney Harrell
|
February 3, 2015 at 11:41 am
That may be what needs to happen. They may need to contact you to have you cancel out their original order and create a new registration with the add-on selected. The price modifier, even if it adjusts the ticket price after the registration is completed, is probably not going to be able to handle sending the registrant back through the payment process to collect the difference.
Please understand that the price modifier add-on was written for a specific EE customer that paid for that custom development. But because other EE customers found it useful, we put it in the pre-release channel.
That said, we are here to help, so please let us know if there is anything we can do for you. Thanks.
|
