resume nodes show up in search results

Has this issue been dealt with? Please let users know if still represent a security issue for the resume poster.

I'm glad I looked at this bug report, because I didn't realize it was doing that. One of my modules was doing the same thing, and I had to implement hook_db_rewrite_sql to overcome this problem. In this case it would look something like this:

/*
 * Implementation of hook_db_rewrite_sql().
 */
function job_db_rewrite_sql($query, $primary_table, $primary_field, $args) {
  switch ($primary_field) {
    case 'nid':
      // this query deals with node objects
      $return = array();
      if (!user_access('view resumes')) {
        if ($primary_table != 'n') {
          $return['join'] = "LEFT JOIN {node} n ON $primary_table.nid = n.nid";
        }
        $return['where'] = "n.type <> 'resume'";
        return $return;
      }
      break;
    case 'tid':
      // this query deals with taxonomy objects
      break;
    case 'vid':
      // this query deals with vocabulary objects
      break;
  }
}

@klance

There are two modules included with the job search module for node access stuff.

Can you please check if your function should go into the resume_access or job_access module rather than the main? Also please test the results with the new change for regression (current access permissions are not affected).

Thanks

Cut the code from job.module and paste it into resume.module. Same effect, more appropriate location.

Yeesh... that gets it out of the search results, but it causes an SQL error that prevents views from showing up. Oh well...