What are the plans for upgrading to 6.x Drupal.

This is the only way to get the fine grained control of sites.

Thanks
Emery Gordon

Comments

antiorario’s picture

subscribe

seedseller’s picture

Please. PLEASE! I need this for Drupal 6.

N.Simpson’s picture

I need this too. I'm happy to lend a hand where possible, I can write PHP pretty well but have no experience with Drupal module development.

BenK’s picture

Subscribing as well... looking forward to a D6 version!

emerygjr’s picture

I believe the module node_privacy_byrole can be a replacement for this module. It is available in 6.x.

Emery

BenK’s picture

Unfortunately, I don't believe node_privacy_byrole allows you to grant access to a node just to a specific user (you must grant access, I think, to an entire role). The ability to grant access using either roles or a uid is a big advantage of this module. One with similar functionality is content_access, but that hasn't been ported to 6.x either.

ash55’s picture

hi i wonder if can help me i just cant seem to sort this out
This code is from a theme that works in drupal 4, 5 but not 6 wiyh the Sidebar and Header regions specified it returns with Arry
Thanx

function _phptemplate_variables($hook, $vars = array()) {
  switch ($hook) {
    case 'page':
  
        if ((arg(0) == 'admin')) {
            $vars['template_file'] = 'adminpage';
        }
      
        $pid = 2;
        $menu = menu_get_menu($pid);
        $output['content'] = "<ul>";
        $output['subject'] = $menu['items'][$pid]['title'];

        if ($menu['visible'][$pid]['children']) {
          
            foreach ($menu['visible'][$pid]['children'] as $mid) {
                $output['content'].= "<li>".menu_item_link($mid);
              
                if (count($menu['visible'][$mid]['children']) > 0) {
                  
                    $output['content'].="<ul>";
                  
                    foreach ($menu['visible'][$mid]['children'] as $sid) {
                        $output['content'].= "<li>".menu_item_link($sid)."</li>";
                    }
                    $output['content'].= "</ul>";
                }
              
                $output['content'].= "</li>";
              
            }
        }
        $output['content'].="</ul>";
      
        $vars[primary_links] = $output['content'];
        $vars[secondary_links] = theme_menu_tree(variable_get('menu_secondary_menu', 0));
      
        $sl = menu_get_menu($pid);
      
        $output = '';
      
        foreach ($sl['visible'][$pid]['children'] as $mid) {
            $type = isset($menu['visible'][$mid]['type']) ? $menu['visible'][$mid]['type'] : NULL;
            $children = isset($menu['visible'][$mid]['children']) ? $menu['visible'][$mid]['children'] : NULL;
          
            if(menu_in_active_trail($mid) || ($type & MENU_EXPANDED)) {
                $output = theme('menu_tree', $mid);
            }
        }
      
        $vars[secondary_links] = $output;//$output;
      
        $vars[site_name] = "Human Capital Architecture Group (HCAG)";
      

  }
  return $vars;
}

function eu_breadcrumb($items, $i = 0) {
  
    $st = "";
    if($items && count($items) > 0 && $i < count($items)) {
        $st = "<ul>";
        $st .= "<li>";
        $st .= $items[$i];
        $st .= eu_breadcrumb($items, $i+1);
        $st .= "</li>";
        $st .= "</ul>";
    }
  
    if($i == count($items) && !drupal_is_front_page()) {
        $st .= "<ul><li>".drupal_get_title()."</li></ul>";
    }
    return $st;

}

function eu_regions() {
  return array(
      'sidebar' => t('Sidebar'),
      'content' => t('Content'),
      'header' => t('Header'),
      'footer' => t('Footer')
  );
}

function theme_views_view_latest_news($view, $type, $nodes, $level = NULL, $args = NULL) {
  $num_nodes = count($nodes);

  if ($type == 'page') {
    drupal_set_title(views_get_title($view, 'page'));
    views_set_breadcrumb($view);
  }

  if ($num_nodes) {
    $output .= views_get_textarea($view, $type, 'header');
  }

  if ($type != 'block' && $view->exposed_filter) {
    $output .= views_theme('views_display_filters', $view);
  }

  if ($num_nodes) {

    if ($level !== NULL) {
      $output .= views_theme('views_summary', $view, $type, $level, $nodes, $args);
    }
    else {
      $plugins = _views_get_style_plugins();
      $view_type = ($type == 'block') ? $view->block_type : $view->page_type;
      $output .= "<dl>".views_theme($plugins[$view_type]['theme'], $view, $nodes);
    }
    $output .= views_get_textarea($view, $type, 'footer');


    if ($output) {
        $output = "$output</dl>\n";
    }
    if ($type == 'block' && $view->block_more && $num_nodes >= $view->nodes_per_block) {
      $output .= theme('views_more', $view->real_url);
    }
  }
  else {
    $output .= views_get_textarea($view, $type, 'empty');
  }





    if ($view->use_pager) {
    $output .= theme('pager', '', $limit, $view->use_pager);
  }
  return $output;
}


function eu_contact_list($category_array) {
  drupal_set_title(variable_get('contactlist_title', 'contact list'));
  $output = "<p>".t('Select the topic about which you want to contact us from the list below:')."</p>";
  $output .= '<div id="contact-list">'. theme('item_list' , $category_array ) .'</div>';
  return $output;
}
gintass’s picture

subscribing

mantyla’s picture

I recently made a largish update of the D5 version and posted about it here: http://drupal.org/node/274900. But since the project maintainer seems to have been missing for nearly a year, the odds of my patch getting accepted appeared low. Unless, of course, I adopted an orphaned project and made it my own, which is exactly what I'm planning to do.

My first step in making this happen is to show that I've got what it takes. So here you go: new versions for both D5 and D6. For the sake of making future updates easier, I had to rearrange much of the D5 code as well to match the format of the D6 version - I didn't change nearly as much as a diff output might tell you.

I have tested both versions, including updating from an older version, and they seem to work fine. Still, if you have a test server where you can play around with them, please do - and let me know how it turned out.

I also fixed a bunch of bugs I discovered in the current development version:
- fixed user search: consecutive searches no longer fail
- default permissions for new users now work
- no more writing of empty permissions
- deleting a node will no longer leave behind garbage in node_access
- changing a node type will no longer result in loss of author permissions
- new node types have default author permissions

Anonymous’s picture

Status: Active » Needs review

Hey folks, I'm working on the D6 upgrade, hope to have it ready for beta testing by next week. There are a lot of UI ideas I have to improve this module and make it better to work with but I will start out with just a D6 version of what is there. I haven't quite decided how future improvements will take place, I'd like to focus on D6 for UI tweaks and added functionality however there are a lot of people out there still using 5.x so I'm not sure how feasible that is. I know that with most new projects I still use 5.x because there are many modules not D6 compatible still (this is mostly why I'm so delayed in upgrading this one since I'm still working on 5.x due to other modules not being updated, catch 22...).

mantyla’s picture

Hello. I admit I'm surprised to see you back, since I'd already believed this project orphaned. I already made a direct request for project takeover here: http://drupal.org/node/276989. I was told to post about it here, so here I am, although now that you are back the situation has changed. Since you say you are working on a D6 upgrade yourself, and I have my own D6 upgrade in working order, I'll offer my cooperation. After all, during the last week or so I've spent a considerable amount of time on this, and now that I am intimately familiar with the inner workings of this module, I'd hate to see that work go to waste. Especially the part about identifying and fixing a number of bugs I noticed during my tests and studying the code.

I'll include the latest versions of my own work with this post, should they be of interest - Drupal 5 and 6 versions alike. The translations are not included, as I haven't modified them to match the new versions yet.

EDIT: Removed attachments, as they're now official versions.

dascope’s picture

debtman7 and mantyla,

I am also very keen on using this module with D6.2. I was about to go for node privacy by role which I think would suit my needs fine but I read it clashes with Taxonomy Access Control and don't want to run into issues in the future.

How far is your version mantyla? Is it ready for a production environment? And will you keep maintaining it even if you cannot settle with debtman7?

I appreciate all your efforts very much.

Best wishes,
da scope

mantyla’s picture

Hello. Glad to hear there is someone interested in my work.

I'd say my version is sufficiently ready. I am using it in a production environment myself. It does have some things that need work: it doesn't react to deletion or insertion of roles (should be harmless, but leaves some outdated permissions in the nodeaccess table), manually removing all grants from a node makes it have default grants after rebuild, and most seriously, when you save changes in the grant tab the priority of this or other node access modules is not consulted (fairly harmless, since permissions from other modules are left alone, but needs to be fixed).

As for maintaining it, I certainly intend to do that. I am working on an upgrade right now, that will fix the issues I mentioned above and introduce new options as well, most of which were specifically designed to make this work with any node access module out there.

darumaki’s picture

That attachment for drupal6 doesn't even appear in the module list

gintass’s picture

I just tried to install your attached version of nodeaccess on Drupal6.3 and it doesn't even show up in the list of available modules in my site: http://mysite.com/drupal6/admin/build/modules

mantyla’s picture

My best guess why the module doesn't show is that the file permissions are wrong. I'm developing this in my work environment, and the permissions of my files are probably different than those used in Drupal CVS. You could try commands like chown, chgrp and chmod to change the owner, group and permissions of the files. If that is the problem, it will go away if and when I get a CVS account.

darumaki’s picture

I can confirm that it was the permissions, once corrected, it shows up in the list

gintass’s picture

You are right, it was permissions problem. I didn't notice that nodeaccess/ directory permissions were 764 instead of 755.
Thank you very much.

darumaki’s picture

the grant tab doesn't show up though in a node

mantyla’s picture

Status: Needs review » Closed (fixed)

I am now co-maintainer of this module, and yesterday I finally figured out how to use cvs - and not without making a newbie mistake while at it. But in the end, the 1.2 versions for both D5 and D6 are out.

As for the grant tab not showing in a node: you'll have to give me more information than that. I had the grant tab appear just like it was supposed to, after I'd given the necessary access permissions and enabled the grant tab for the node types I wanted. Have you done this? If yes, and the grant tab still doesn't show, what sort of node is it? Which permissions did you give, and to which roles? Is the node published, and what is its input format?

Despite my best effors, it is possible that bugs still remain in the code. But to hunt them down, I really need to know where to start looking.

darumaki’s picture

I must be doing something wrong then because in both 5 and 6 the grant tabs do not show up in the node, will research it more. I didn't think I needed to give any permissions since I'm admin, admin should by default able to grant access on a node

mantyla’s picture

Well, the admin account, with user ID 1, should bypass all the access checks, so I guess those can't be your problem. But, even the admin needs to enable the grant tab for each content type in the settings.

As for the admin being able to grant access by default, I quite agree it should work by default. And in 2.0 it will. I'll need to rewrite the README.txt, otherwise the D5 version is ready for release.