Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
system.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
2 Aug 2012 at 23:37 UTC
Updated:
11 Jan 2017 at 16:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tim.plunkettI wouldn't characterize this as a critical bug. What happens when you rerun the update?
Comment #2
JvE commentedCould you check the code of function system_update_7074() in /modules/system/system.install ?
Mine looks like this:
Comment #3
Thomas_Zahreddin commentedsame for me: i got the same message - and i think the text of the message is confusing:
7074 - This update has been removed and will not run.
-> This update … will not run.
This leaves the admin alone and i did not knew what to do.
Better message would be:
7074 - The code of this update has been removed. It is safe to run it.
This message is the N out of system_update_7074 concatenated with the comment of the function, so the comment of the function should be changed.
And one has to run this update anyway in the moment when system_update_7075 arrives (possible with any further release of D7).
Maybe it is also a good idea to change the subject of the issue
to reflect that just the message is confusing.
I call it a bug, since a bug by my definition is all behavior of a software, that does not meet the users expectations.
Comment #4
payamspot commentedI had the same problem ("update from drupal 7.14 to drupal 7.15 fails during update.php running") and the reason was Speedy module. I uninstalled Speedy module, then updated D7.14 to D7.15 without any problem.
Comment #5
Jooblay.net commentedOne note on updating CORE is remember to take your time:) most of the time these errors are just simple config or corruption or .htaccess files that are hidden on the server due to the (dot)htaccess.
I would start by checking all your core files to make sure they are available and not corrupted to boot.
Remember within the chaos is always tranquility:)
Comment #6
dddave commentedI am boldly setting this issue to fixed as it seems the OP has solved his problem.
@Thomas_Zahreddin please create a new issue if you still see the need for your patch which won't solve the problem at hand but would improve usability.
Comment #8
sarika_sics commentedwhen run upgrading from Drupal 7.1 to 7.51, i got "The update process was aborted prematurely while running update #7074 in system.module. All errors have been logged. You may need to check the watchdog database table manually."
and shows completed 94 of 94
updating mimemail module.
and when check watchdogs
“Watchdog” log is having the similar errors messages to the previous deployment.
a:6:{s:5:"%type";s:6:"Notice";s:8:"!message";s:21:"Undefined index: type";s:9:"%function";s:15:"drupal_get_js()";s:5:"%file";s:56:"/var/www/releases/20161122001301/src/includes/common.inc";s:5:"%line";i:4475;s:14:"severity_level";i:5;}
I can't rectify the issue based on the above watchdog issue...In my satgeing and test server all are working fine.This issue is only in production server. and sever configurations are same in all servers.
Can you please help me..?This is a critical issue..I need to upgrade the site...
Comment #9
sarika_sics commentedwhen upgrade from Drupal 7.1 to 7.51. The upgrade process seems to work in all of our development and test environments, but fails when we attempt the upgrade on the live server
Message in live shows ..
The update process was aborted prematurely while running update #7074 in system.module. All errors have been logged. You may need to check the watchdog database table manually.
and completed 94 of 94 and updating mimemail module and when check watchdogs shows ""
“Watchdog” log is having the similar errors messages to the previous deployment.
a:6:{s:5:"%type";s:6:"Notice";s:8:"!message";s:21:"Undefined index: type";s:9:"%function";s:15:"drupal_get_js()";s:5:"%file";s:56:"/var/www/releases/20161122001301/src/includes/common.inc";s:5:"%line";i:4475;s:14:"severity_level";i:5;}
can you please help me?I can't resolve the issue..
Comment #10
cilefen commented@sarika_sics Please open a new issue as this one is four years old and the error is different.