AW: [Openinteract-help] static page serving and templates

[<And...@Be...>]

Hi Chris,

do I get this right: you need an entry in page for every document??? =
Maybe,
this explains my problems when updating to 1.36 from 1.30, when I =
removed
stativ_page altogether. When I did this, no file was deliverd at all, =
only
stuff from handlers.

BTW: during this I found, that oi_manage list_actions seems to be =
broken...

Back to subject: does this mean, that hierachical security in the form =
like
in static_page does not work anymore and that there is no =
default-handler to
serve files?

later,

Andreas

-----Urspr=FCngliche Nachricht-----
Von: Chris Winters [mailto:ch...@cw...]
Gesendet: Dienstag, 11. Dezember 2001 02:55
An: jo...@po...
Cc: ope...@li...
Betreff: Re: [Openinteract-help] static page serving and templates


* John Sequeira (js...@me...) [011210 17:29]:
> I'm having some trouble serving static pages.  I've got a package
> with some web pages in the /html folder.  GIF's in a package
> subfolder /html/images are served up correctly from my templates,
> but I can't directly access these pages from a url. In other words,
> http://myserver.com/mylogo.gif works but
> http://myserver.com/newpagename.htm get a file not found error.  The
> OpenInteract default page serves up correctly, so base_page is
> working...  but not on html within my package.

Doh! I forgot to add this in to the apply/upgrade_package process. The
problem is that there are no 'page' objects corresponding to the files
in the filesystem. I'll try and fix this for the next verrsion. (BTW:
the /images files probably work because, if you're using the
recommended two-server setup the front-end deals with everything under
that URL-space)

Until I fix this, there's a script
(pkg/base_page-x.xx/script/scan_for_new.pl) that should take care of
it for you. It scans your /html directory (ignoring /html/images and
/html/oi_docs) for files that don't have a corresponding 'page' object
and creates them for you. Take a peek at it -- it's fairly simple.

> Second question is, how do I override the default template provided
> by OI?  I'd like to implement something as simple as a per-website
> header/footer, which seems like it might be covered by either a
> config file option, or being able to overload the Template
> initialization routine and redefine the wrapper routine.  I wasn't
> clear on how to do this from read the Template::* pod files.

If you're using 1.35 and higher, you can just edit
$WEBSITE_DIR/template/base_main to do this. Super easy.

Mostly OT: You can also define custom template processing
configuration parameters through OpenInteract::Template::Process --
it's got pretty thorough docs on this.

Chris

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

_______________________________________________
openinteract-help mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/openinteract-help