Fatal error: Call to undefined function: search_index() in /home/www/ahweb45/html/nwp-site/modules/node/node.module on line 2593

Comments

Gurpartap Singh’s picture

Gurpartap Singh commented
Status: Active » Postponed (maintainer needs more info)

Is it being caused by paging? If so, on which page? And did you upgrade from previous release (1.0)?

printoperator’s picture

printoperator commented

Yes, after the upgrade from previous release (1.0) to (1.1). If I update the drupal database paging module (1), I got this error.

VenDG’s picture

VenDG commented
Version: 5.x-1.1 » 6.x-1.0-beta2

This is happening to me with the 6.x version when I run update.

An error occurred. http://yy.com/update.php?id=1&op=do <br /> <b>Fatal error</b>: Call to undefined function node_update_shutdown() in <b>/home/yy/public_html/sites/all/modules/paging/paging.install</b> on line <b>18</b><br />

printoperator’s picture

printoperator commented
Version: 6.x-1.0-beta2 » 5.x-1.1
Status: Postponed (maintainer needs more info) » Active

Yes, after the upgrade from previous release (1.0) to (1.1). If I update the drupal database paging module (1), I got this error.

panji’s picture

panji commented

at first I've got the same problem,.. it's conflict to other module,.. maybe it's about your editor or filter module,.. try to disable and enable it again,.. don't forget to backup ur database (u can use backup and migrate module)... yup,.. I need some tryal time to make this module work for me,..

moggy’s picture

moggy commented

Just got the same error when updating to 5.x-1.1

I don't have search enabled on my site. So I enable search and tried the update again, which then ran perfectly.

Does this happen because the update does a module_invoke on a module that isn't enabled?

Gurpartap Singh’s picture

Gurpartap Singh commented
Version: 5.x-1.1 » 5.x-1.x-dev
Status: Active » Fixed

Fixed in 5.x-1.x. We perhaps didn't check if search module is enabled.

http://drupal.org/cvs?commit=166588

Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.