Installing on a multisite

I created a site running in a core multisite environment. I added the prosepoint profile to the 'core' and then did an install on the sub site. Everything went fine except I got the following warning after the sample content had been loaded:
warning: array_map() [function.array-map]: Argument #2 should be an array in /home/cfbusine/public_html/modules/system/system.module on line 966.
Then, when I went to the new 'home' page, I got the following? Can I fix this??
* warning: array_map() [function.array-map]: Argument #2 should be an array in /home/cfbusine/public_html/modules/system/system.module on line 966. * warning: array_keys() [function.array-keys]: The first argument should be an array in /home/cfbusine/public_html/includes/theme.inc on line 1762. * warning: Invalid argument supplied for foreach() in /home/cfbusine/public_html/includes/theme.inc on line 1762. Mark
Interesting. It seems like Drupal didn't notice the tma2 theme during installation. If you visit .../admin/build/themes, that will trigger a rescan and your messages should go away.

I'm getting this on install:
Fatal error: Call to undefined function date_format_save() in /home7/aboutshe/public_html/profiles/prosepoint/prosepoint.profile on line 68
Any tips?
Regards,
Mark C.
Hi,
You should probably have started a new thread since your issue is unrelated to the original post. I'll answer quickly, but if the problem persists, please start a new thread to follow up instead of posting onto this one.
The function date_format_save() is defined by the date_api module which is bundled with ProsePoint. Since your installation is reporting that the function cannot be found, I would suspect your source code files are not quite correct.
Please check that your uncompression software works properly, then please check that you have uploaded your files to your web server without any errors, then please completely clear out your database and reinstall from the beginning.
If the problem still occurs, please start a new thread to continue this discussion. Thank you.
Beng,
Thanks for the reply. I think this is the right forum for this topic. I should have mentioned that I am also using multisite. What I did was ftp the prosepoint profile folder to my profiles folder. That was the only one I uploaded, presuming that is all I needed to do.
The installation ran fine until I got to the part when asked if I wanted a demo site or a minimal site and whichever I chose, I got that message. However if I just when to my installation at prosepoint.adesignforlife.net I could look at the admin area (which just looked like a normal drupal admin, nothing extra) but there was no navigation menu - Creae Content, etc.
If this is still the wrong forum, let me know, and I'll start a new thread.
Regards,
Mark C.
Hi,
> What I did was ftp the prosepoint profile folder to my profiles folder. That was the only one I uploaded, presuming that is all I needed to do.
This should be sufficient since ProsePoint would just as happily operate off the vanilla Drupal core instead of the slightly modified ProsePoint version.
When you say ProsePoint profile folder, I presume the folder has a directory named 'modules' with some other stuff in it?
If so, I think there may be a mismatch in the Date module which ProsePoint is finding when installed on your multisite. Perhaps it is seeing a Date module without a defined date_format_save() and this then causes installation to fail.
Please check which Date module(s) are available in your multisite installation and let me know.
When you say ProsePoint profile folder, I presume the folder has a directory named 'modules' with some other stuff in it?
If so, I think there may be a mismatch in the Date module which ProsePoint is finding when installed on your multisite. Perhaps it is seeing a Date module without a defined date_format_save() and this then causes installation to fail.
Please check which Date module(s) are available in your multisite installation and let me know.
-- What I did was downloaded ProsePoint and then copyied the folder called 'prosepoint' from the Profiles folder and pasted that into the profiles folder of my multisite installation. There was a directory in it called modules, with CCK and others (whatever the prosepoint install has). I didn't touch that folder or any others.
I don't have any date module installed on my multisite installation, so I presumed the issue is coming from the date module that prosespoint installs - presuming it does install a date module.
Regards,
Mark C.
> There was a directory in it called modules, with CCK and others (whatever the prosepoint install has). I didn't touch that folder or any others.
Correct.
> I don't have any date module installed on my multisite installation, so I presumed the issue is coming from the date module that prosespoint installs - presuming it does install a date module.
And my suspicion is that you have a Date module in your multisite installation somewhere. Do you have a .../sites/all/modules directory with other modules in it? Or do you have a sites/default/modules (or other similar equivalent) directory with other modules in it? If there is a Date module in either of these two locations, ProsePoint might be picking that up instead of the Date module bundled with ProsePoint.
In other words, do ANY of the sites on your multisite installation also use the Date module?

Hi,
I've just tested using ProsePoint with unmodified Drupal core and I got the same error. ProsePoint should work with Drupal core, so this is a confirmed bug. Let me investigate further.