I think there is a good use case for when you may want a set price. Couldn't this be accomplished with a hidden field?

CommentFileSizeAuthor
#1 webform_pay-1038408.patch644 bytesjdwfly

Comments

jdwfly’s picture

jdwfly commented
Status: Active » Needs review
StatusFileSize
new webform_pay-1038408.patch644 bytes

Pretty simple patch but it seems to work for me.

charlie-s’s picture

charlie-s commented

I second this feature request. I currently create a disabled field for cost and use CSS to hide it everywhere that I implement Webform Pay.

quicksketch’s picture

quicksketch
he/him
commented
Status: Needs review » Fixed

Sounds good, just be aware that your users can edit the price by using a tool like Firebug!! The Webform issue at #630476: Allow hidden fields to handle unsafe tokens by making the "value" type fields would solve this problem by making hidden fields really "value" components.

Committed to the project.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.