Re: [Openinteract-help] oi_manage w/ apply_package, fails 'Website name not set in package object'

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

Jon wrote:
> But All Of A Sudden:
> 
> [root@3evtowers demo]# oi_manage --base_dir=/usr/local/OpenInteract 
> --website_dir=/home/httpd/OIdemo --package=demo apply_package
> Running apply_package...
> =========================
> 
> Status of the packages you requested to be applied:
> demo (0.01)
>   FAILED!: Cannot install package to website. Error: Website name not
>            set in package object.
> 
> Hard to trace, as I cannot find this defined anywhere - the error is 
> indeed accurate! :)  Saying where "Website name" is set might make the 
> error msg more useful if that's unproblematic.  FWIW my package.conf the 
> default one spat out by the create_skeleton.  I can give more stats as 
> to my environment as required, not posting 'em now cos I had the whole 
> thing working.  Just can't apply my new package :(

That's very strange... this isn't set in the package itself (that 
is, the 'package.conf' file in the package), it's set into the 
information passed to the relevant OI::Package routine. What's 
strange is that oi_manage should read this information from your 
base configuration file -- sort of a bootstrapping file that gets 
everything up and going. It should be in $WEBSITE_DIR/conf/base.conf 
and have your website name defined. Does yours have this field?

> Out-of-the-box do Pages > Create.  For location put something a bit 
> silly like oooooohhh 'demopage'.  Add some copy, save it ("Status Object 
> created properly."), view it - 404 error.  Now it can be seen in the 
> list, but can't be edited cos it can't be found, so you can't remove it 
> through the UI as far as I can see.  How do you delete it safely - I 
> assume ripping out of the DB isn't as it would mess up some internal 
> records of OI? (I have no problems using '/demopage.html' etc).

Actually you can just delete the database record. I thought I'd 
fixed this... ah, that was something else. There's something deeply 
weird going on here... trying to create a 'demopage' record forced 
my mod_perl process to gobble up every bit of available memory. Not 
good! I'll fix this shortly.

> Failing that, maybe change the "Must be unique; use only letters and 
> numbers, no spaces or other characters" copy by the Location: widget to 
> be more all-inclusive, or surely it's possible not to create the page in 
> the 1st place if OI predicts it will result in a 404 (can't see why this 
> shouldn't be possible).

That's possible... I'm pretty sure this has to do with the lack of a 
file extension and treating it like a directory request... a bit 
more digging to do.

> Apart from that it looks really cool, sitting nicely between bare 
> templating systems and overweight CMS's.  I've been evaluating 
> mod_perl-y things like this for about a month and I'd like to settle 
> with OI.

Cool. The 'page' stuff allows for some very simple CMS operations, 
but you'd probably have to extend it or write your own for anything 
fancier. It works fairly well for creating/editing HTML/text 
documents as well as a browser-based shared filespace.

Good luck!

Chris

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