|
From: Eric R. <er...@1s...> - 2002-09-13 22:01:13
|
Chris Winters <ch...@cw...> said: > > I see the line in question (when the \'field\' value of an SPOPS > configuration is undefined), but this should have been defined earlier > in the process.... Just for kicks, do something like: > > # cd $WEBSITE_DIR/pkg > # find . -name \"spops.perl\" | xargs grep \' field \' > > And see if you have any items with one of: > > field => \'\' > field => undef, > > If so, try changing them to: > > field => [], > > And see what happens. Clearly this is fragile and shouldn\'t be so. > Hah. I had an SPOPS object defined without a \'field\' value in my package\'s spops.perl. I had mistakenly only defined a \'field_order\', and since I haven\'t yet used this object, I didn\'t see the error until now. It\'s always something simple. For some reason, the migrate script still doesn\'t like me. Here\'s what we\'ve got now: -- Using (/home/1stcontact.com/intranet) for \'website_dir\'. Can\'t locate object method \"process\" via package \"SPOPS::Initialize\" (perhaps you forgot to load \"SPOPS::Initialize\"?) at script/migrate_to_filesystem.pl line 30. -- It has been a week since I\'ve had any time to tackle this one, so I\'m probably overlooking something else. Another push in the right direction would of course be greatly appreciated. Thanks again. Eric |