By mxc4 on

Hi all,

The documentation says to run update.php after a module upgrade but the update.php page warns that the script should not be run more than once. Which one is correct?

1) If it shouldn't be run more than once it is a security risk leaving the file in place as anyone could mess up your site by running the script.

2) I backed-up my site and ran the script again when upgrading ecommerce module. At first all seem ok but I now cannot edit any content. When I click edit I just get a blank page and nothing to edit. This happens for old and new content. i.e content added before or after the update. There is nothing in the watchdog logs about an error. Any ideas how to fix this?

thanks

⋅ Categories: Drupal 4.7.x

Comments

vm’s picture

vm commented

update.php would need to be run after "each" update of a module" do not run twice, means do not run twice in a row. update module, run update.php, update another module run update.php. update core run update.php

not

update module run update.php run update.php. update core run update.php, run update.php.
so basically do not run more then once for any single update of any single module or core update. hope this better explains.

1. noone else but the 1st created user can run update.php. find this out for yourself. logging out then trying to browse to update.php. Thus no security issue.

blank page errors can be found in your apache logs. when you recieved the blank page, did you do a view source to see if anything was there ?

mxc4’s picture

mxc4 commented

Hi there,

Thanks for the info. I thought I had replied to the post but couldnt find it. At first I found no errors in the logs but I was looking in the wrong place. I find this error in the log when trying to edit any content other than product content of type "apperal" from the ecommerce module.

[notice] child pid 2643 exit signal Segmentation fault (11)

It seems like a general error. After upgrading to 4.7.4 all worked fine until I upgraded the ecommerce module.

http://www.jumpingbean.co.za/php/development
http://www.cyberdesigns.co.za/content/view/22/40/

z3cka’s picture

z3cka commented

This seems like a good way to go about updating modules and running the update script. Is this still a good practice when updating?

vm’s picture

vm commented

yes. Nothing has changed in the way the updating/upgrading methods go.