Error When Activating Module

It's unlikely that I will be running that configuration any time soon. Can you output some debug information to see why that index is not defined when the routine runs, possibly also a trace output?

The same message occurs on a LAMP stack.
Drupal 7.12
PHP 5.2.17

Do you have any advice for debugging on a Mac? Not something I've done before, but can give it a shot.

Same problem,

setup:

VPS on
- CentOs 5.7
- Apache 2.2.22
- MySQL 5.1.61
- Php 5.2.17

Don't know if it's related but APC is enabled (allready had some issues cause of APC during an drupal core and drupal module install)

Same issue with this setup Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8n DAV/2 PHP/5.2.13 mod_jk/1.2.31 MySQL/5.1.46
Think this is not environment related problem...

I have a development server running a LAMP stack with PHP 5.3.3. I spun up a site running Drupal 7.12. I enabled the 7.x-1.0 release of this module as well as the 7.x-1.x release with no errors in either case. This site only has Views (and UI) enabled along with minimal core modules.

Please provide more detailed information. If someone could output the array on line 63 (see Issue Summary), that would be helpful. Do you have existing views and fields defined before enabling this module, or afterward? I tried it either way and never had any notices.

same here

Here https://gist.github.com/2412451 is comlete dump of $field['settings']['views_base_table'], $data, $field and $module variables from the moment when i got the error.

Also figured out that the error is shown only when Localization update (http://drupal.org/project/l10n_update) is enabled.

I got the same error when activating the module...

Notice: Undefined index: views_base_table in views_field_field_views_data_alter() (line 63 of /var/aegir/platforms/drupal-7.12/sites/MYSITE/modules/views_field/views_field.module).

best regards
Christian

@radimklaska, would you attach the output from views_trace() or similar function when you encounter the notice? The notice would result if hook_field_info_alter() is not called before hook_field_views_data_alter(), but I would like to understand under what circumstances this might occur, as it does not for me.

I believe cause of problem may be simply from enabling and installing too many modules at the same time from which some may use Views field module. I was setting up about 4-6 OpenLayer and MapBox related modules together with "Fieldgroup views" module and the error mentioned above popped up. Disabled fieldgroup views module and uninstalled ... error went away, re-installed ... no error. No idea about what, how or why it happened ... doesn't seem to cause any errors from my point of view, nor does it seem to be a error caused by Views field module.

This notice appears when you enable this module, and refreshing clears this. may be some routines are required to map the fields to clear the default state of fields

Fixed in this commit.

I did not encounter the notice as my site had admin_menu enabled and it, after enabling this module, would invoke a refresh of the field_info. This, in turn, would result in the key in question being defined when views updated its data, thus omitting the notice.