By annsera on
Drupal is installed and works...somewhat.
Certain modules don't configure. First, I had a number of errors whenever I tried to access certain modules' configuration pages: array_merge() [function.array-merge]: Argument #1 is not an array in /.../includes/menu.inc line 351..
I used an array() cast to get rid of the error message, but the fundamental error still seems to exist. When, for example, I attempt to configure the audio system, the general site configuration comes up. This happens for the vast majority of the modules.
Has anyone heard of anything like this happening?
Comments
What modules? Were they
What modules? Were they included in CivicSpace or did you get them from here? I am asking because:
a) The Drupal version number is very important. Modules for Drupal 4.7 don't work with Drupal 4.6 (and vice versa). So, you need to know to which Drupal version your CivicSpace version corresponds (and even if you do, nothing is guaranteed -- there may be more errors waiting).
b) The CivicSpace distribution is meant to be a customized suite of well tested Drupal modules which work together for a complete solution. Usually they lag behind in Drupal version number, because of customization, testing etc.
Just CivicSpace
Thanks for your quick reply!
I am aware of the 4.6 vs. 4.7 issue and the modules were all included with the CivicSpace distribution.
I wish that was the only problem!!!
Lots more information -- site just doesn't configure
Here are the modules that I can configure as "reachable" by the Navigation menu:
administer site->features->, or "reachable" by using this link:
http://www.mysite.com/sadmin/modules
Note that there are other modules enabled that are NOT listed here
(like buddy, poll, etc) and trying a link like http://www.mysite.com/admin/settings/module_name
for those brings up a 404. Thus, I have no known way of configuring them at all (if they are configurable, that is.
I should think that some of them must have some configuration associated with them).
administration --- OK
audio --- No, get general site configuration page (name of site, etc.)
event --- No, get general site configuration page
eventfinder --- OK
eventfinder settings --- There are 4 tabs and the first one is the SITE configuration,
not the eventfinder main settings. The other 3 tabs are ok.
flexinode --- No, get general site configuration page
image --- No, get general site configuration page
location --- There are 2 tabs and the first one is the SITE configuration,
not the location main settings. The "map links" tab is OK.
mass mailer --- No, get general site configuration page
massmailer --- First, note that there is "mass mailer" with and without spaces,
both listed. No, get general site configuration page
node_privacy_byrole --- No, get general site configuration page
notify --- No ,get general site configuration page
privatemsg --- No get general site configuration page
profiles --- OK
queue --- No, get general site configuration page
role lists --- OK
search --- OK
statistics --- No, get general site configuration page
theme editor --- Seems to work, not well tested
throttle --- No, get general site configuration page
tinymce --- OK
volunteer --- No, get general site configuration page
It's possible that some of those things (statistics?) are actually configured on the main configuration page,
but I think they are supposed to have their own pages.
Notice that there are a numerous other errors that I get. I was hoping that the other
errors were due to lack of configuration, but I'm not sure. Here's some of the other errors I've noticed:
I just tried to add a text field in the profile configuration and got:
warning: Illegal offset type in /var/www/vhosts/mysite.com/httpdocs/modules/profile.module on line 608.
I also wanted to change the word "forums" to "Forums" on the main navigation. So, I went here according
to the breadcrumb: Home » administer site » build >> menus, or here according to the URL:
http://www.mysite.com/admin/menu. Tried to hit "edit" next to the "forums" entry, and got this:
warning: sprintf() [function.sprintf]: Too few arguments in /var/www/vhosts/draftjohn2008.com/httpdocs/includes/database.inc on line 154.
user error: Query was empty
query: in /var/www/vhosts/draftjohn2008.com/httpdocs/includes/database.mysql.inc on line 66.
Just seems like everywhere I turn, I get errors and strange behavior. I do SEEM to have my permissions set, my tables set up, etc.
Installation reported that everything was good.....
Any help would be appreciated. If I really have to install everything myself, why on earth would I stay on 4.6?
Not all modules have an
Not all modules have an /admin/settings page. Some just add some options to another page and some don't appear anywhere. Some are just programming APIs for other modules to use.
Generally each module contains a readme and/or an install file containing information about its requirements, operation and what to expect. For example, audio module for 4.6 says that it requires a third party package called getID3. The 4.7 version says that it is optional. Not sure if CivicSpace includes that. You can ask more in its project page (http://drupal.org/project/issues/audio). Generally this is how we get our support here -- the module project pages.
But you are right that there is no reason to use a 4.6 distribution if it does not work out of the box, except if the guys at CivicSpaces can give you some pointers about how to make the whole package operate reliably. There is no point in correcting bugs yourself using only general programming skills without knowing all the internals. New subtler bugs may be introduced, as it happens all the time in the development here.
With the release of Drupal 5.0 in a couple of months, 4.6 will become officially unsupported. Already many of the initial maintainers of the 4.6 modules either have changed or they don't even remember what 4.6 was like. You will expect support mostly from CivicSpace.
So, I suggest that you either get in touch with CivicSpace and see if you can establish a good communication or get Drupal 4.7.4 and collect the modules you need. Some of the modules you mentioned haven't been updated for ages and won't do. With 4.7.4 you will also have a clean upgrade path to the upcoming 5.0 version.
I hope something somewhere in here helped.