No start delay

chrisns - January 14, 2009 - 04:05
Project:UC Node Access
Version:6.x-1.x-dev
Component:Miscellaneous
Category:support request
Priority:normal
Assigned:Unassigned
Status:reviewed & tested by the community
Description

This looks ideal for what I need, however how do I make it so there isn't a delay between the purchase and people being allowed access to the node?
As far as I can see my lowest option is:

Access time delay
Specify the length of time after purchase the customer must wait to have access to the node.
1 day(s)

I'm on Drupal 6.8, ACL 6.x-1.0-beta3, Ubercart 6.x-2.0-beta1, Content Access 6.x-1.0, UC Node Access 6.x-1.x-dev (2009-Jan-08)

#1

chrisns - January 14, 2009 - 04:08
Status:active» closed

Nevermind, I just figured it!
Duh!
In conditional actions, you can either set the action to allow at a later time or just allow.

#2

patchak - January 20, 2009 - 18:00
Status:closed» active

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

#3

patchak - January 20, 2009 - 19:41

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

#4

patchak - January 20, 2009 - 19:43
Status:active» closed

#5

bfelix - March 6, 2009 - 13:12

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.

#6

kleinmp - March 18, 2009 - 15:08
Status:closed» active

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.

AttachmentSize
delay_period.patch 1.16 KB

#7

kleinmp - March 18, 2009 - 15:21

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.

#8

neochief - April 7, 2009 - 13:07
Status:active» reviewed & tested by the community

I can confirm that this patch works for me.

#9

add1sun - May 13, 2009 - 22:57

Yep, same problem and same solution.

#10

j0rd - September 21, 2009 - 06:50

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.

 
 

Drupal is a registered trademark of Dries Buytaert.