Limit on Published nodes

That is confusing. Sorry, but it should actually state create and not publish.

As far as limiting the amount a user could publish, it cannot do that. Now this could be something I might add in, but I just wonder how many would want to do that.

I'm going to see how long this would take me, but I wanted to make a 1.0 release soon. Patches are welcome.

Yes, that is exactly the method I would take. It needs to be its own rule otherwise rule setup could get confusing.

Limit "Published" nodes would be very helpful.

Any update on limiting "published" nodes and not every node created by the user?

I'm about to release the 2.0 so this is probably going to move to the next version.

How about now?
This is exactly the feature I have been looking for.

+1 subscribing

Does anyone know of any workaround for this?
Is there anyway of creating a condition for number of published nodes of content type x that a user has?

Thank you very time

Hi, is this a feature that can be sponsored?

I have developed a solution to add limit on published nodes rule condition, This work was done on the Node limit number 6.x-2.x-dev (I am including the patch) by request of Evelyn (@nyleve101) and is now working satisfactorily. I hope it helps for someone, can be improved or to be included in a future.
Juan

Thanks for the patch, but the problem with it is that there is no way we change the existing rule functionality. If something like this were to get into the module it would need to be its own event/condition so as to not break any existing implementations.

But the bigger problem is that there isn't a whole lot of configurability with how it chooses the nodes. It really needs some type of query builder so that you can precisely choose which nodes you want. You want published nodes only, but someone may want both... there is another issue that needs nodes before/after certain dates. Before I keep slapping on new ways to limit there really needs to be some thought put in to how to account for all the different ways people want to limit and how can they be implemented incrementally as needed without having to rework the entire module.

Thanks for your quick response, well I agree that is possible add more functionality, but it could be the basis for a new update (evelyn just needed this and I shared here), I believe that you would have no problem adding a condition for node types, you could do:

<?php
/**
 * Helper function to check limit published
 */
function _node_limitnumberpublished($time, $node, $user, $limit, $type) {
  if ($type != $node->type) {
    return FALSE;
  }
  $values = array();
  $values[] = $node->type;
  $values[] = $user->uid;
  $query = $time == 'none' ? "SELECT COUNT(nid) AS num FROM {node} WHERE status <> 0 AND type = '%s' AND uid = %d" : "SELECT COUNT(nid) AS num FROM {node} WHERE status <> 0 AND type = '%s' AND uid = %d AND created > %d";
  switch ($time) {
    case 'daily':
      $values[] = strtotime(date('Y-m-d'));
      break;
    case 'weekly':
      $values[] = time() - 604800;
      break;
    case 'monthly':
      $values[] = strtotime(substr(date('Y-m-d'), 0, 8) .'01-01');
      break;
    case 'annually':
      $values[] = strtotime(substr(date('Y-m-d'), 0, 5) .'01-01');
  }
  if ($node->nid) {
    $query .= " AND nid <> %d"; 
    $values[] = $node->nid;  
  }
  $count = db_fetch_object(db_query($query, $values));
  if ($count->num >= $limit) {
    return TRUE;
  }
  return FALSE;
}

?>

Juan

Hi!

I saw that patch#14 is included in latest 6.x-2.0-beta2, but I am not sure how to figure it.
When I try to edit "Example: Authenticated Users create only 1 page" rule there is no event to "check a published node limit". Only "check a node limit" is available.

Did I miss something?
Sorry if my question has no sense :D

.