What does this error message mean?
wtt - December 9, 2007 - 12:28
"
* warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/jkwuliuc/public_html/drupal/includes/theme.inc on line 275.
* warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/jkwuliuc/public_html/drupal/includes/theme.inc on line 278.
"
How can I solve that?

This answer might be just as confusing but...
it means that that function is expecting an array of arguments and that array doesn't exist. You would solve it by making sure the arguments are being passed as arrays.
Since you didn't post the theme that you were using or any other information that might be helpful in investigating your problem, I can't tell you how to solve it.
Maybe a psychic could help ;)
joel
I had the same thing
I've also just moved from one hosting provider to another and managed to fix the problem. It is something to do with your database character sets, and their not being the same on the two servers (I think).
I was using php code to control when certain of my blocks would display and when I went in to have a look at them I saw that things like the curly braces in my php were replaced with Å and Ä :) Oops. I'm sure there's an elegant way to fix this directly in the database only I'm too scared to try on this site which is now live and working after I'd fixed the borked braces.
Incidentally, the other place that you should check and fix is in your user account: the @ in my email address was no longer an @.
Re: array merge () .... on line 278
We were changing the name of the Drupal database when we hit this error after doing an SQL dump, a series of find-and-replaces for various paths that included the old name, and then a batch import (create tables, the works) into an empty database.
When we uploaded the old dump into the new database WITHOUT the find-and-replaces, no error. So Kevin the Honorable painstakingly find-and-replaced, table by table, until he found the error.
It was in the variable table, under the theme line: theme_[themename]_settings
By leaving this as it was but changing the setting in admin/build/themes/settings/[themename] we were able to update and lose the error.
I don't know why this worked.... but it did.
-Bram
I had the same problem when
I had the same problem when moving my test site to a production server. I needed to change the sites directory name which required the editing of some database tables. Your solution worked for me but first I needed to go to the site configuration > file system page and re-input the files and tmp file locations.
Patrick