I get the following when I try to run update.php:

An error occurred. http://efbandung.com/update.php?id=6&op=do
Fatal error: Call to undefined function views_invalidate_cache() in /home5/talking6/public_html/efbandung/sites/all/modules/image/contrib/image_gallery/image_gallery.install on line 97

CommentFileSizeAuthor
#1 drupal_image_issue_569766.diff419 bytespatryk

Comments

patryk’s picture

patryk commented
Assigned: Unassigned » patryk
Priority: Normal » Critical
StatusFileSize
new drupal_image_issue_569766.diff419 bytes

fix in the patch

Anonymous’s picture

Anonymous (not verified) commented

Ditto.

Call to undefined function views_invalidate_cache()

How do I apply a patch to fix this?

rubensans’s picture

rubensans commented

Same here.

How do we apply that patch?

patryk’s picture

patryk commented

See http://drupal.org/patch/apply for some info on patching.

Anonymous’s picture

Anonymous (not verified) commented

Same error

However, I am not knowledgable enough to do patches and such. Will there be a fix in the near future? Can I just go back to the previous version without damaging my site?

patryk’s picture

patryk commented

I'm not a maintainer of Image module, so I have no idea when it will be applied into next version. However, I think you should be fine to skip this update in your update.php runs.

joachim’s picture

joachim commented
Status: Active » Fixed

Ouch... I think this was a commit I made late in the code sprint.

Thank you very much for the patch. I've just committed it to HEAD and it will be in the next release.
And yes, #6 is correct. All this update does is clear your views cache so the new default views show up. It's merely a convenience.

Anonymous’s picture

Anonymous (not verified) commented

Skipping the run for update.php might be ok for now, but if another module comes along with an update that DOES require the update, then what?

Does anyone know when the patch will be applied to the next release of the Image module?

I've tried to comprehend the instructions on applying a patch and it's a greek to me.
How about an example for this particular patch? perhaps that will shed some light on patching.

Hetta’s picture

Hetta commented

techgy: ... clearing the views cache will NEVER be critical - especially if you don't even have one, cos you don't have views installed. It's a "safe to ignore" error.

joachim’s picture

joachim commented

techgy: the status change means the fix is in, will be in next release.
If you want to try patching, start here: http://drupal.org/patch If that section of the docs is unclear, then file issues on it. It's meant to be n00b-friendly ;)
But as Hetta says, this error is absolutely not critical. You can clear the views cache yourself in the admin UI.

Borromini’s picture

Borromini commented

Thanks for the patch, the first hit on my google query was the duplicate thread... Hence the post there ;-).

Keep up the good work!

Status: Fixed » Closed (fixed)

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