No start delay

Actually, I have the same issue.. (I think)...

On my product node I get this message : Node access Grant indefinite access to node 1, 1 days after purchase.
Applies to SKU: Lesson 2 in the Features section.

On the other hand, in the conditional actions, I setup a new action with the condition :

Condition: Check the order status > Completed

and the action :

Action: Grant node access to customer

So there are some contradictory instructions, or so it seems... I'm not sure what I could do to fix this...I tried to create a new product, but still the instruction on the "Features" section, mentions that the node will be made available one day after the transaction.

Any help please? I need the node access to take effect immediately!

Patchak

Ok I figured it out.. It seems I was using the wrong trigger, as the right trigger is not when the order is completed, but it works with the " Order status gets updated" trigger.

I will close the issue now, since I got it all sorted out!

Patchak

Regardless it seems to me that its quite confusing not to have either a "0 days" option, or to clearly indicate there that this is driven by the Order update trigger.

In the function uc_node_access_feature_form, it looks like the fieldset $form['delay_period] and all it's elements are declared twice. I'm not sure why, but here's a patch for it in case this is a problem. This also allows users to set the node access delay period to 0 days.

To clarify - $form['delay_period']['delay_period_value'] was defined tqice, as far as I can tell, and one of them sets the range of values from 1 to 52 and the other sets them from 0 to 52. I removed the one the sets the value range from 1 to 52.

I can confirm that this patch works for me.

Yep, same problem and same solution.

As a veteran Ubercart and Drupal user, this confused me as well and I had to search around looking for a fix for my "in 1 day" issue.

Should have an option to 0 days or something, to avoid this confusion.

Same for me :)

works for me

Patch from #6 worked for me.

This is actually a bug...

Committed