|
From: Chris W. <ch...@cw...> - 2001-12-11 12:33:00
|
* Andreas Nolte (And...@Be...) [011211 07:07]: > do I get this right: you need an entry in page for every document??? Yep -- I want to be able to have the metadata in the database but the content elsewhere. One of the cool things is that the metadata can define a location for the content by URL. So we're encouraging all the folks who want to wrap another site's content in their own... :-) > 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. There's a migration script in pkg/base_page-x.xx/script/static_page2base_page.pl. But you need to have the 'static_page' package installed to use it. The migration script works very well. I migrated a site with ~1700 pages and it worked great. > BTW: during this I found, that oi_manage list_actions seems to be > broken... I'll check this out. Hm... Do you get a bunch of 'cannot require Class::Blah' messages? (Just to make sure we're getting the same error... :-) > 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? No and no. Hierarchical security still works just the same, and the default handler is 'base_page' instead of 'static_page'. You can run the 'scan_for_new.pl' script (in the pkg/base_page-x.xx/script dir) periodically to create metadata objects from files in the filesystem. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |