Fatal error: Call to undefined function securepages_url() when securepages prevent hijack module is installed

hey,

here's a fix you can try when using the 6.x-2.x-dev version of securepages. it changes the behavior somewhat, but if your secure pages setup is right, it should be ok.

so, to get rid of the error simply comment out the violating section of code, namely comment this out in securepages_prevent_hijack.module:

if ($form['#id'] == 'user-login-form' || $form['#id'] == 'user-login') {    
    $url = parse_url($form['#action']);                                         
                                                                                
    $base_path = base_path();                                                   
    $path = (!strncmp($url['path'], $base_path, drupal_strlen($base_path)) ? dr\
upal_substr($url['path'], drupal_strlen($base_path)) : $url['path']);           
    $options = array('secure' => TRUE);                                         
    if (isset($url['query'])) {                                                 
      $options['query'] = $url['query'];                                        
    }                                                                           
    $form['#action'] = securepages_url($path, $options);                        
    }

the reason this is fine to do is because what that code does is ALWAYS secure the login form. but, you should be doing that anyway in your secure pages by matching user/login. furthermore, the 2.x-dev version of securepages seems to handle the case where you use a login block and it secures that too:

  // If the user/login path matches, also secure the login block.               
  if (securepages_match('user/login') && $form_id == 'user_login_block' && !$is\
_https) {
    $form['#action'] = url($path, array('absolute' => TRUE, 'base_url' => secur\
epages_baseurl(TRUE)));
  }

so if you still want to prevent hijacking, i believe that change should fix things up. i'd hope the author would confirm, but it doesn't seem like they are watching this bug.

Thank you!! Exactly what we needed.

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks