Upgrade Warnings [#670504]

When upgrading a D 6.14 site from getclicky 6.x-1.1 to 6.x-1.4 receiving the following errors:

* warning: array_merge() [function.array-merge]: Argument #2 is not an array in /public_html/dev/2/update.php on line 174.
* warning: array_merge() [function.array-merge]: Argument #2 is not an array in /public_html/dev/2/update.php on line 174.
* warning: Invalid argument supplied for foreach() in /public_html/dev/2/update.php on line 338.
* warning: Invalid argument supplied for foreach() in /public_html/dev/2/update.php on line 338.

The module list is attached.

Experienced the same issue when upgrading the 6.14 to 6.15 and then upgrading from GC 6.x-1.1 to 6.x-1.4.

Comment	File	Size	Author
	modules.txt	4.31 KB	TrinitySEM

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

iryston CreditAttribution: iryston commented 24 January 2010 at 17:20

I've got the same issue when upgrading the 6.14 to 6.15
In my Drupal instalation there are just CoreModules + Nodewords + Printer, e-mail and PDF versions + Token.
Maybe it's problem with Nodewords module or with Drupal itself.

Comment #2

rsvelko CreditAttribution: rsvelko commented 26 January 2010 at 23:37

will report soon what I find after I look into this... stay tuned.

Comment #3

rsvelko CreditAttribution: rsvelko commented 27 January 2010 at 00:02

Title:

Upgrade Error

» Upgrade Warnings

I do not remember when did I became the new maintainer, so I may have gotten on board inheriting some upgrade hidden bombs...

I am tired at this time ... till later.

Apart from these warnings - did sth break bad?

What makes you think that it is this module's fault?

Comment #4

TrinitySEM CreditAttribution: TrinitySEM commented 29 January 2010 at 21:05

Too much time has passed for me to recall. I rolled back to 1.1 and have avoided the newer versions.

I believe the issue to be the GC module because this occurred on two domains.

Thanks for your help.

Comment #5

rsvelko CreditAttribution: rsvelko commented 23 May 2012 at 00:35

Status:

Active

» Closed (cannot reproduce)

1. This bug happens when a mysql query fails on update.
2. When doing a getclicky module update - be careful not to run some other module's update hooks at the same time!
If the other module's update fails you wont know which failed...
In normal situations all is done at once - but when it fails you have to debug one by one... unfortuantely the warnings are not quite informative...

Probably the query warnings are not sth to worry about - no matter which module's bug it is...

The probability of this being a getclicky issue is 1-5%

Here is why:

- all the reporters show me a list of installed modules with plenty of candidates for a failing query
- clicky has no db tables at all - so it does not run queries on updates!!! So on update.php runs - some other module should be causing the warnings...

If all else fails during a getclicky update - just leave the settings page open - then uninstall it via /sites/all/modules/uninstall and then re-enable it... and setup...

Marking issue as cannot reproduce ..