Currently views scheduler implements hook_user.

function views_scheduler_user($op, &$edit, &$user, $category = NULL) {
  switch ($op) {
  case 'view':
    $items[] = array('title' => t('Subscribed to '),
    'value' => t('none')
    );
      return array('History' => $items);
    
    break;

  case 'categories':
    return array(array('name' =>'schedule_subscription',
			 'title' => 'Subscribe to scheduled view',
			 'weight' => 4));
    break;

  case 'form':
	$form[$category]['affiliate_enabled'] = array
	  ('#type' => 'radios',
	   '#title' => t('Is as Affiliate?'),
	   '#default_value' => 1 ,
	   '#options' => array(t('Disabled'), t('Enabled')));
      return $form;
    break;
  }
}

What is the plan for this function? This seems like a half implemented feature. The problem is this creates a confusing account edit setting for all users in which the views scheduler is installed. We've had to comment out the function.

Comments

flk’s picture

oops sorry i forgot to branch the versions....the plan for the _user is to give users the ability to subscribe to a view and get update once schedule runs....ie get an email when a new release takes place.

Zack Rosen’s picture

Cool. could you branch this so that this doesn't show up in 4.7 version of the module till it is ready?

flk’s picture

Status: Active » Fixed

done, thnx

Anonymous’s picture

Status: Fixed » Closed (fixed)