openinteract-help

[Openinteract-help] Trouble with oi_manage and create_website on Win32

[David C. R. <dr...@xo...>]

Hi:

Some people have written in regarding a problem with the create_website =
command in the oi_manage batch program on Win32 systems.  After hunting =
around a bit I think I have located the problem.  At line 30 of =
PackageRepository.pm there is a subroutine called "package_filename," =
which in turn calls the method "catfile" in the "File::Spec" module.  =
The "File::Spec" module is designed to handle OS-specific filesystem =
semantics, and the "catfile" method concatenates the arguments passed to =
it in an OS-correct way.   The subroutine "package_filename" in  =
PackageRepository.pm calls the "catfile" method with "/" as the first =
arg (I'm assuming to specify root on *nix machines).  This causes an =
error when prepended in a Windows environment  (i.e., it comes out as =
"/c:\path\to\OI\base\dir").  As a quick fix I replaced the line in  =
PackageRepository.pm with a Windows-appropriate one. My code looks like =
this:

#sub package_filename { return File::Spec->catfile( '/', $_[1], =
$PKG_DB_FILE ) } # original code
sub package_filename { return File::Spec->catfile($_[1], $PKG_DB_FILE ) =
} # new code without forward slash

A more robust fix in PackageRepository.pm might be to check if the base =
directory specified begins with "/" or "c:\" and prepend appropriately =
(or better yet have File::Spec figure this out itself).

Hope this helps,
Dave Reed

Re: [Openinteract-help] Trouble with oi_manage and create_website on Win32

[Chris W. <ch...@cw...>]

David C. Reed wrote:
> Some people have written in regarding a problem with the create_website 
> command in the oi_manage batch program on Win32 systems.  After hunting 
> around a bit I think I have located the problem.  At line 30 
> of PackageRepository.pm there is a subroutine called "package_filename," 
> which in turn calls the method "catfile" in the "File::Spec" module.  
 > ...

Looks great! Thanks for the detective work -- patch applied.

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

[Openinteract-help] SPOPS Error: Can't locate object method "CONFIG"

[David C. R. <dr...@xo...>]

Hi:

I am having a problem with SPOPS.  I have two objects that share a
"links_to" relationship.  When I try to instantiate either I get the
following error message:

Can't locate object method "CONFIG" via package "My::PackageName" (perhaps
you forgot to load "My::PackageName"?) at lib/SPOPS/ClassFactory/DBI.pm line
304.

I have used the structure for creating objects given in the "eg/My"
examples, and require'd the linked objects.   If I comment out the
"links_to" line in the config of one of the objects, that object
instantiates fine and the "links_to" relationship partially works, but not
fully.

Anyone have any ideas about this?

Thanks,
Dave

Re: [Openinteract-help] SPOPS Error: Can't locate object method "CONFIG"

[Chris W. <ch...@cw...>]

David C. Reed wrote:
> I am having a problem with SPOPS.  I have two objects that share a
> "links_to" relationship.  When I try to instantiate either I get the
> following error message:
> 
> Can't locate object method "CONFIG" via package "My::PackageName" (perhaps
> you forgot to load "My::PackageName"?) at lib/SPOPS/ClassFactory/DBI.pm line
> 304.
> 
> I have used the structure for creating objects given in the "eg/My"
> examples, and require'd the linked objects.   If I comment out the
> "links_to" line in the config of one of the objects, that object
> instantiates fine and the "links_to" relationship partially works, but not
> fully.

You need to be sure to instantiate both at the same time since a 
class needs to do some introspection on its related class (to find 
the ID field and such).

The best way to do this is read all your configurations into a 
single hashref and process them all at once. For instance, the 
following should work assuming that 'read_config()' returns a single 
hashref with the configuration for a single object.

  my $config_package_a = read_config( 'conf/package_a.perl' );
  my $config_package_b = read_config( 'conf/package_b.perl' );
  SPOPS::Initialize->process(
            { config => { a => $config_package_a,
                          b => $config_package_b } } );

Hope this helps,

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.