I'm working on a project that requires the payment process to kick in when a user edits a node for purchase after it has been created. By default, this module does not process editing an existing, unpublishing for payment. I would like to propose a setting on the node content type to have the module process payments when existing, unpublished nodes are edited.

I will attach a patch for your consideration shortly.

CommentFileSizeAuthor
#1 commerce_node_checkout-existing_node_process_setting-1930644-1.patch2.28 KBjemond
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jemond’s picture

jemond CreditAttribution: jemond commented
FileSize
commerce_node_checkout-existing_node_process_setting-1930644-1.patch2.28 KB

Patch attached.

jemond’s picture

jemond CreditAttribution: jemond commented
Status: Active » Needs review
tannerjfco’s picture

tannerjfco CreditAttribution: tannerjfco commented

Amazing timing, I was just trying to figure out how to do this! I've tested the patch and it works as advertised!

jemond’s picture

jemond CreditAttribution: jemond commented
Status: Needs review » Reviewed & tested by the community
tannerjfco’s picture

tannerjfco CreditAttribution: tannerjfco commented
Status: Reviewed & tested by the community » Needs review

Upon further review, this is unfortunately not quite right. I thought this was working as expected, but as it turns out this patch actually allows the process existing nodes functionality to work if the option is unchecked on the content type. I did not notice this initially, as I did not notice the setting, and the functionality worked as I needed. It wasn't until I installed the commerce_authnet module that the process existing nodes functionality started working as you intended - in that it stopped working as I had it configured, and started working properly once I set the checkbox to enable it.

I'm not really sure what difference the commerce_authnet module makes, but its the only module that has made an impact on this patch. The patch will work for what I need, but I suspect we don't want that functionality running if the setting is not enabled :)

mstef’s picture

mstef CreditAttribution: mstef commented
Issue summary: View changes
Status: Needs review » Postponed (maintainer needs more info)

If you have an updated patch that fixes your issue and applies to the latest code, please post and re-open. I'm not entirely sure how much sense this makes to have in this module. Are you saying that on every edit, the node is added back in to the cart and the edit needs to be paid for before the edit goes live??