Haven't tried to debug this any further, and it's possible this is something unique to the test site where I'm doing this import, but I have a clean copy of core, tw, migrate, and a handful of standard module (views, cck, token, etc) plus ubercart. Whenever tw is enabled and I clear my views cache, I get the following error:
warning: array_merge_recursive() [function.array-merge-recursive]: recursion detected in /.../includes/module.inc on line 473.
That's in module_invoke_all():
$return = array_merge_recursive($return, $result);
I at least narrowed it down to hook_views_default_views. If I just have tw_views_default_views() return immediately, the error goes away. No time now to look closer, but wanted to open an issue about it in case anyone has any bright ideas.
Thanks,
-Derek
Comments
Comment #1
mikeryanGoogling around, the phrase "seems to occur randomly" is highly associated with this message. Without a reproducible case, there's little we can do. The one thing I can suggest is disabling "Provide default view" for one of your TW tables at a time to see if one specific table is triggering this.
Comment #2
dwwGood idea (although, wow, the tw UI doesn't make that task very easy...) ;)
Tracked it down to this. The legacy DB I'm importing from has a table named "calendar". If I leave the default view name as "calendar", I get the error and no view actually shows up. If I rename it to "foo_calendar", the error goes away. Here's the view export in case this is helpful:
No time to further debug this. I'm not sure what the "bug" is. Perhaps it's just a UI thing, and tw should detect collisions like this and provide a more meaningful error. Maybe something's actually going wrong under the covers. Although I have calendar module enabled on this site, I don't have any calendar views configured, so I'm not sure what the conflict even is...
Comment #3
mikeryanOK, this looks like another symptom of #617142: Horrible collisions of death when adding a table w/ same name as Drupal table or existing view - the views structure for the external calendar table collides with the one for the calendar module's table...
Thanks for further diagnosing this.
Comment #4
dwwcalendar module has no such {calendar} table, so I don't think that's directly the problem...
Comment #5
mikeryanCalendar does create a view named calendar. It's not technically a collision of tables, it's a collision of views structures.