Steps to reproduce:
Create a new commerce_database
Install a fresh install of Commerce Kickstart (Mine was locally on MAMP with mysql).
Set up store products, shipping rules etc.
Move to a multisite set up as it will be on the server. (Again a separate local MAMP install with other sites already set up.)
Copy the relevant additional modules across to the existing base Drupal installation. (Note this is not a commerce kickstart installation profile.)
Add the new sites/example_new_commerce_site folder to the existing base Drupal installation.
Copy the default default.settings.php to sites/example_new_commerce_site and create settings.php as per multisite set up.
Edit settings.php to connect to the database with all the products set up in step one.
Visit admin/reports/status

You then get the following errors:

Notice: Undefined index: name in system_requirements() (line 39 of /modules/system/system.install).
Backtrace:
system_requirements('runtime')
call_user_func_array('system_requirements', Array) module.inc:819
module_invoke_all('requirements', 'runtime') system.admin.inc:2288
system_status()
call_user_func_array('system_status', Array) menu.inc:517
menu_execute_active_handler() index.php:21

Notice: Undefined index: version in system_requirements() (line 41 of /modules/system/system.install).
Backtrace:
system_requirements('runtime')
call_user_func_array('system_requirements', Array) module.inc:819
module_invoke_all('requirements', 'runtime') system.admin.inc:2288
system_status()
call_user_func_array('system_status', Array) menu.inc:517
menu_execute_active_handler() index.php:21

Notice: Undefined index: value in theme_status_report() (line 2552 of /modules/system/system.admin.inc).
Backtrace:
theme_status_report(Array) theme.inc:1044
theme('status_report', Array) system.admin.inc:2302
system_status()
call_user_func_array('system_status', Array) menu.inc:517
menu_execute_active_handler() index.php:21

From the research I have done, I understand this is related to the fact that the base Drupal install was just a core standard install with no instillation profile.
After the move, the modules are connecting to a database that was installed and added to on a Commerce Kickstart instillation profile.

Can anyone help me solve this problem without having to start setting up the whole store from scratch on a new database as that is a lot of work?
I tried copying the commerce kickstart profile folder across but that made no difference. I don't know anywhere near enough about drupal core and installation profiles to know where to start.

Andrew

Comments

damien tournoud’s picture

damien tournoud commented
Category: bug » support
Status: Active » Fixed

That's likely because you failed to keep the profile in place.

andrew.scullion’s picture

andrew.scullion commented

Hi Damien,

I have spent a lot of time trying to get to the bottom of this with no joy. You appear to be suggesting that I have failed to move the commerce kickstart local development correctly, would you please explain to me what you mean.

That's likely because you failed to keep the profile in place.

I do not understand what this means, how do I keep the profile in place?

I simply installed all the relevant commerce modules into the base drupal sites/all/modules/contrib
Added the sites folder for the new settings.php and copied the database from the local kickstart intsall across to the server.

Andrew

damien tournoud’s picture

damien tournoud commented

When you installed, you had the profile in profiles/commerce_kickstart. When you moved your site around, you removed that profile. Drupal is complaining because of that.

On Drupal 6, the profiles were used only during the initial installation. On Drupal 7, they are a critical part of the site, even after the initial installation. You cannot just remove the files of the profile without Drupal complaining.

andrew.scullion’s picture

andrew.scullion commented

As I said in the initial post:

I tried copying the commerce kickstart profile folder across but that made no difference

So have I missed something here or is there an issue with just adding the profiles/commerce_kickstart/ to the standard install file set (minus the kickstart modules folders which where put in sites/all/modules/contrib/)

Thanks for your help.

klavs’s picture

klavs commented

I have the same problem - which only showed when upgrading from 7.12 to 7.14 - it had been running without those complaints about missing index'es for a long time beforehand.

I'm not running multisite though.

I've tried to download latest commerce kickstart profile and copy the commerce_kickstart profile folder into profiles on the site, but that didn't change anything :(

andrew.scullion’s picture

andrew.scullion commented

Reading through this post helped me solve this error:

http://drupal.org/node/1170362

Basically I went into the database 'system' table and re-set the status of the standard profile to '1'

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

altern8’s picture

altern8 commented

If we actually need to *keep* the original profiles/ directory during a minimal core update (7.12 -> 7.14 in this case), shouldn't that be mentioned in the update instructions?

Salif’s picture

Salif commented

Hi,
I've run in the same problem after upgrade to the latest commerce_kickstart-7.x-2.7

Notice: Undefined index: value in theme_status_report() (line 2583 of /home/.../public_html/modules/system/system.admin.inc). Backtrace:
theme_status_report(Array) theme.inc:1146
theme('status_report', Array) system.admin.inc:2333
system_status() 
call_user_func_array('system_status', Array) menu.inc:517
menu_execute_active_handler() index.php:33

The reason could be:
Since I've started using commerce kickstart, I've always moved from profiles/commerce_kickstart/ modules: the commerce_kickstart and contrib folders to sites/all/modules. Every things worked great. as mentionned in: http://www.drupalcommerce.org/user-guide/installing-commerce-kickstart-1x (but I saw this now considered as bad practice!)
Or something else could be the reason.

Need advise, help please.
How can I move back the modules to profile and keep the site safe?