Closed (fixed)
Project:
Drupal core
Version:
7.14
Component:
update.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Oct 2011 at 05:56 UTC
Updated:
10 May 2015 at 05:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #0.0
i46 commentedfew edits
Comment #0.1
i46 commentedadding more info
Comment #1
wildfeed commentedReporter should specify modules that produced the result. I downloaded a newer version of Pathauto and ran update.php. Update was performed successfully. Also downloaded a newer version of Token module, ran update.php and it completed properly.
Comment #2
wildfeed commentedBug fixed awaiting review.
Comment #3
marcingy commentedThe correct status is postponed as we need more information from the original reporter of the bug.
Comment #4
i46 commentedThanks a lot guys for your efforts.
there was no error message, the update process wasn't completed.
I tried to upadte after release of token new version, but it has nothing to do with the token module.
and the page stops at the same step when ever I try to run the update. see attached picture
Running the update script, doesn't it mean going through all steps and running updates and ending with the log review!?
Comment #5
marcingy commentedThe issue sounds like it could be related to your hosting provider, although just stalling is really really strange. Have you tired doing a search on drupal.org using the name of your host or on google for a problem with drupal and your host. Do you have any access what so ever to php error logs to see if they show any more information?
Comment #6
i46 commentedThanks for your prompt reply,
as I mentioned I have two websites, one on VPS and the other on hostgator where they're not related at all and had the same error.
I did some search with no avails. I asked for help via drupal IRC channel but as you said it's a weird issue.
Comment #7
i46 commentedWhat do you think it? what could it be!?
I tried my best, I opened a ticket and the hosting support said it's drupal issue.
I'm ready to give you an access to my site. To check is it drupal issue or server issue!?
Comment #8
nick_vhCan you give us a list of the modules you installed and the exact procedure on how to reproduce this? It seems (according to your screenshot) you are using another language as well so be sure to include those steps in the guide.
Hopefully we'll figure it out!
Comment #9
i46 commentedThanks Nick for your support
Yes my website is in Arabic with bunch of modules but as I clarified earlier I have another website on shared hosting with pure english language with only token installed and has the same issue. [see attachment]
I'm used to drupal 6. So the way I update modules, I just open FTP and delete the module file "the old version" completely and upload the new version, and run the update script by browsing to www. mysite. com/update.php, go through all the steps and I'll be directed the log review page.
But now with drupal 7.8 as you may noticed on the attached photo, the process stops at the same step "Review updates" and never passes that point.
Btw, I asked my hosting suport to provide me with a php log, whenever I get that message I'll post it here
Comment #10
i46 commentedThey just replied, there is nothing major in the PHP logs ..
Comment #11
marcingy commentedAre you disabling all contrib modules before you start the upgrade process and are you also removing the file sites/default/default.settings.php and making your settings.php writable so as it can be upgraded?
You should have a look at the instructions in upgrade.txt as the process is somewhat different from updating from say 6.21 to 6.22.
Comment #12
i46 commentedDo I need to disable all contrib modules every time I had to run the update script !!?
I just deleted the default.settings.php file, made the settings.php writable (was 775 - changed it to 777)
disabled all contributed modules and still have the same issue
I'm trying to run the update script (update.php) after installing new version of few modules on a virgin drupal 7.8 (freshly installed, not upgraded).
Comment #13
marcingy commentedOh I misread that you were trying to upgrade from d6 my bad. No you don't need to disable all modules on a point update.
Comment #14
i46 commentedNo worries ,, it's my fault :P
I shouldn't ve mentioned drupal 6 from the beginning.
I was trying to say I update modules the way it should be done in whatever drupal version.
Comment #15
i46 commentedI contacted my Hosting MST, they went through everything related to my server, they couldn't find something wrong
they even tried to reproduce the issue themselves. there is No php errors, no dblog errors.
Comment #16
nick_vhCould it be that there are no updates? No Pending updates in your screenshot mean that there are no updates to be done?
Please give us a concrete usecase on how to reproduce it
Exact version of drupal, exact version of a module + the exact version of the new module
Comment #17
i46 commentedYour questions are the asme ones I'm trying to figure out.
I'm not sure if the module that I did update needs to go through "run updates" step or not.
Does update script suppose to go through all the steps with every module update? or it goes whenever a module needs to!!?
I'm using drupal 7.8
token old version: 7.x-1.0-beta5
token newer version: 7.x-1.0-beta6
Comment #18
i46 commentedI just Had another module update which answered all my questions
Thanks for your support
Comment #19
i46 commentedComment #20
geiraage commentedI have the same problem iMz. How did you solved this?
Comment #21
geiraage commentedComment #21.0
geiraage commentededit
Comment #22
mgiffordComment #23
dcam commentedClosing old issues.