From: Steve S. <sap...@gs...> - 2003-05-01 22:35:27
|
This seems like a silly question, but I'm wondering if there's an easy roadmap for getting started on setting up a full OI site. I have done all the required single steps -- what I'm missing is how to incorporate the provided OI management functionality provided by the default OI home page into a real intranet-type site. Is it best to start from scratch with my own front-end design and push the provided home page off to the side; or (I suspect) start with my own design and copy the functions of that home page over to the starting point I create? If I missed some docs in this area, let me know ... Thanks. Also, if I replace the default, what happens on upgrades? ---- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Chris W. <ch...@cw...> - 2003-05-02 03:47:26
|
Steve Sapovits wrote: > This seems like a silly question, but I'm wondering if there's > an easy roadmap for getting started on setting up a full OI > site. I have done all the required single steps -- what I'm > missing is how to incorporate the provided OI management > functionality provided by the default OI home page into a real > intranet-type site. Is it best to start from scratch with my > own front-end design and push the provided home page off to the > side; or (I suspect) start with my own design and copy the > functions of that home page over to the starting point I create? > If I missed some docs in this area, let me know ... Thanks. I think the former is best, if only on principle: your framework should work for you, not the other way around. My 'mangement functionality' I assume you mean the administration boxes along the right-hand side. You can put those boxes anywhere you like -- you can copy the links from them and put them into a separate page. Or you can even do this in your normal text: <p>Here is the admin tools box:<br> [% OI.comp( 'admin_tools_box' ) %] It might look odd without the borders, etc., but you get the idea. You can modify the 'base_main' page to not have any boxes at all, and only files in a particular directory (e.g., '/admin/') protected by directory security have the management functionality. Hopefully whatever you can think up, OI can accommodate. > Also, if I replace the default, what happens on upgrades? The $WEBSITE_DIR/html and $WEBSITE_DIR/template directories should have each had a file '.no_overwrite' placed there on website installation. Any files listed there (one per line) should *not* be overwritten when you do an upgrade. I can attest to this since it works on my own site :-) Good luck! Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Steve S. <sap...@gs...> - 2003-05-03 23:32:03
|
I wrote: > This seems like a silly question, but I'm wondering if there's > an easy roadmap for getting started on setting up a full OI site. I > have done all the required single steps -- what I'm > missing is how to incorporate the provided OI management functionality > provided by the default OI home page into a real > intranet-type site. Is it best to start from scratch with my > own front-end design and push the provided home page off to the > side; or (I suspect) start with my own design and copy the functions > of that home page over to the starting point I create? If I missed > some docs in this area, let me know ... Thanks. Chris responded: > I think the former is best, if only on principle: your framework should > work for you, not the other way around. Making some progress here. Is there a way to use any of the canned TT styles (e.g.. Splash!) as (or as part of) OI themes? -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Steve S. <sap...@gs...> - 2003-05-04 07:38:14
|
I did some upgrading (TT and SPOPS) and now get this instead of the main page: Can't locate object method "id" via package "feeds::User" (perhaps you forgot to load "feeds::User"?) at /usr/local/lib/perl5/site_perl/5.6.1/OpenInteract/Auth.pm line 36. 'feeds' is my site name. I see a feeds::Handler::User package in feeds/tmplib, but can't find any references that indicate what might be configured wrong. -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Steve S. <sap...@gs...> - 2003-05-04 17:08:12
|
I wrote: > > I did some upgrading (TT and SPOPS) and now get this instead of the > main page: > > Can't locate object method "id" via package "feeds::User" (perhaps > you forgot to load "feeds::User"?) at > /usr/local/lib/perl5/site_perl/5.6.1/OpenInteract/Auth.pm line 36. > > 'feeds' is my site name. I see a feeds::Handler::User package in > feeds/tmplib, but can't find any references that indicate what > might be configured wrong. This went away when I flushed my browser cache. I assume there was some cookie set with the old version that's incompatible with the new? But this leads to another error. I'm using the Apache set-up with a modperl backend and a lightweight front end Apache server. The modperl server is getting this error now: --EXITED WITH ERROR from main handler eval block Error: Can't locate object method "throw" via package "feeds::ErrorObject" (perh aps you forgot to load "feeds::ErrorObject"?) at /usr/local/lib/perl5/site_perl/ 5.6.1/OpenInteract/Error.pm line 94. Again, I see now feeds::ErrorObject package anywhere even though that's in the default server.ini configuration. I can't leave this empty or I get a similar error: --EXITED WITH ERROR from main handler eval block Error: Can't call method "throw" on an undefined value at /usr/local/lib/perl5/s ite_perl/5.6.1/OpenInteract/Error.pm line 94. I'm having the feeling I messed something up doing the upgrade ... -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Steve S. <sap...@gs...> - 2003-05-04 17:20:09
|
I wrote: > But this leads to another error. I'm using the Apache set-up with a > modperl backend and a lightweight front end Apache server. The modperl > server is getting this error now: > > --EXITED WITH ERROR from main handler eval block > Error: Can't locate object method "throw" via package > "feeds::ErrorObject" (perh > aps you forgot to load "feeds::ErrorObject"?) at > /usr/local/lib/perl5/site_perl/ > 5.6.1/OpenInteract/Error.pm line 94. > > Again, I see now feeds::ErrorObject package anywhere even though that's > in the default server.ini configuration. I can't leave this empty or I > get a similar error: > > --EXITED WITH ERROR from main handler eval block > Error: Can't call method "throw" on an undefined value at > /usr/local/lib/perl5/s > ite_perl/5.6.1/OpenInteract/Error.pm line 94. > > I'm having the feeling I messed something up doing the upgrade ... I recreated my site, saving the old and copying its config files over and all works now. I must have fat fingered something ... -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Chris W. <ch...@cw...> - 2003-05-04 17:22:19
|
Steve Sapovits wrote: > ... > I recreated my site, saving the old and copying its config files over > and all works now. I must have fat fingered something ... That's the first time I've heard that phrase. Gotta store that for future reference ;-) Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Chris W. <ch...@cw...> - 2003-05-04 17:20:35
|
Steve Sapovits wrote: >> I did some upgrading (TT and SPOPS) and now get this instead of the >> main page: >> >> Can't locate object method "id" via package "feeds::User" (perhaps >> you forgot to load "feeds::User"?) at >> /usr/local/lib/perl5/site_perl/5.6.1/OpenInteract/Auth.pm line 36. >> >> 'feeds' is my site name. I see a feeds::Handler::User package in >> feeds/tmplib, but can't find any references that indicate what >> might be configured wrong. Did you try to rename your website as part of the upgrade? This error indicates that the SPOPS class for the user object was not either not properly built or was built under a different name. > This went away when I flushed my browser cache. I assume there was > some cookie set with the old version that's incompatible with the new? If configured OI will do some object caching in a session for the 'user', 'groups' and 'theme' objects. If you flush your browser's cache (delete the cookie referring to a session) there's no danger of the session object and the object OI thinks it should have getting out of sync. BTW: If you're debugging it may be a good idea to turn this off. Just set the different 'session_info.cache_*' keys to 0. > But this leads to another error. I'm using the Apache set-up with a > modperl backend and a lightweight front end Apache server. The modperl > server is getting this error now: > > --EXITED WITH ERROR from main handler eval block > Error: Can't locate object method "throw" via package > "feeds::ErrorObject" (perh > aps you forgot to load "feeds::ErrorObject"?) at > /usr/local/lib/perl5/site_perl/ > 5.6.1/OpenInteract/Error.pm line 94. > > Again, I see now feeds::ErrorObject package anywhere even though that's > in the default server.ini configuration. I can't leave this empty or I > get a similar error: This sounds like the same type of error as above. Can you look in your server error logs (not the vhost error logs) and see if OI is complaining about anything at startup? The errors get placed in the server because generating SPOPS classes is part of the ChildInitHandler phase, before the vhost is entirely initialized. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Chris W. <ch...@cw...> - 2003-05-04 17:14:25
|
Steve Sapovits wrote: > Making some progress here. Is there a way to use any of the canned > TT styles (e.g.. Splash!) as (or as part of) OI themes? Good question. I haven't used splash before so I'm not sure what controls the 'theme' part of it. I suspect it would be painless, since everything in OI is an add-on to TT rather than a replacement. Well, almost: OI overrides the foo::bar syntax for PROCESS/INCLUDE/WRAPPER for referring to package::template_name templates. If you could post a brief example of how splash works I'd probably have a better idea. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Steve S. <sap...@gs...> - 2003-05-04 17:31:52
|
Chris Winters wrote: > Good question. I haven't used splash before so I'm not sure what > controls the 'theme' part of it. I suspect it would be painless, since > everything in OI is an add-on to TT rather than a replacement. Well, > almost: OI overrides the foo::bar syntax for PROCESS/INCLUDE/WRAPPER for > referring to package::template_name templates. > > If you could post a brief example of how splash works I'd probably have > a better idea. Here's a simple one right from the tt2 examples directory: [% buttons = [ { link => 'buttons.html', text => 'Buttons' } { link => 'menus.html', text => 'Menus' } { link => 'tabs.html', text => 'Tabs' } ] %] [% PROCESS splash/menu %] Basically they're (I think) a lot like OI widgets. They package up a look/feel and wrapper around specific page elements. I haven't done a lot with them. I think OI may override the expected TT load paths, so I started by symlinking them to the OI doc root for starters. I got partial results -- missing images. Maybe the INCLUDE/PROCESS overrides OI has are getting in the way? Since I had (ahem) other problems, I'm not sure where this really stands now. I need to start my experimenting over and watch what I type. 8-) -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Steve S. <sap...@gs...> - 2003-05-04 18:04:17
|
Chris Winters wrote: > Good question. I haven't used splash before so I'm not sure what > controls the 'theme' part of it. I suspect it would be painless, since > everything in OI is an add-on to TT rather than a replacement. Well, > almost: OI overrides the foo::bar syntax for PROCESS/INCLUDE/WRAPPER > for referring to package::template_name templates. > > If you could post a brief example of how splash works I'd probably > have a better idea. I replied: > Here's a simple one right from the tt2 examples directory: > > [% buttons = [ > { link => 'buttons.html', text => 'Buttons' } > { link => 'menus.html', text => 'Menus' } > { link => 'tabs.html', text => 'Tabs' } > ] > %] > > [% PROCESS splash/menu %] I forgot you have to add this before the code above: [% PROCESS splash/config %] The config. has vaious overrides you can set. I got this to work by symlinking various pieces from my TT2 install to the OI directories. Are there master settings I can override instead? Basically, where outside of OI to look for images, templates, etc. Worst case the symlinks aren't too bad, except that they likely become hidden magic someone else misses on a reinstall. -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |
From: Chris W. <ch...@cw...> - 2003-05-05 23:41:39
|
Steve Sapovits wrote: > I got this to work by symlinking various pieces from my TT2 install > to the OI directories. Are there master settings I can override > instead? Basically, where outside of OI to look for images, templates, > etc. Worst case the symlinks aren't too bad, except that they likely > become hidden magic someone else misses on a reinstall. I sent a reply yesterday answering this question but in response to an earlier one of your emails. For some reason mozilla decided to flag this message as spam and I didn't see it until now. I just wanted to make sure you saw the earlier message. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Chris W. <ch...@cw...> - 2003-05-04 18:29:22
|
Steve Sapovits wrote: > Here's a simple one right from the tt2 examples directory: > > [% buttons = [ > { link => 'buttons.html', text => 'Buttons' } > { link => 'menus.html', text => 'Menus' } > { link => 'tabs.html', text => 'Tabs' } > ] > %] > > [% PROCESS splash/menu %] > > Basically they're (I think) a lot like OI widgets. They package > up a look/feel and wrapper around specific page elements. I haven't > done a lot with them. I think OI may override the expected TT > load paths, so I started by symlinking them to the OI doc root for > starters. There's a way to add TT configuration information programmatically -- you can define a custom initialization class to modify the configuration before it's passed to TT: [template_info] ... custom_init_class = My::CustomTTClass custom_init_method = process_config then you should be able to do something like this (untested): package My::CustomTTClass; sub process_config { my ( $class, $tt_config ) = @_; my $splash_dir = '/usr/local/tt/splash'; my $existing_path = $tt_config->{INCLUDE_PATH}; if ( ref $existing_path eq 'ARRAY' ) { push @{ $existing_path }, $splash_dir; } elsif ( $existing_path ) { $existing_path .= ":$splash_dir"; } else { $existing_path = $splash_dir; } $tt_config->{INCLUDE_PATH} = $existing_path; } > I got partial results -- missing images. Maybe the > INCLUDE/PROCESS overrides OI has are getting in the way? Are the URLs generated by splash looking for images under a particular path? Maybe you need to copy the splash images under your site's 'images/' directory, or add an Apache alias: Alias /images/splash /usr/local/tt/splash/images Good luck! Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Steve S. <sap...@gs...> - 2003-05-04 17:27:02
|
Chris Winters wrote: > That's the first time I've heard that phrase. Gotta store that for > future reference ;-) Oh, if you had worked with me you'd have heard it over and over again for the last 18 years ... 8-) -- Steve Sapovits GSI Commerce, Inc. http://www.gsicommerce.com Email: sap...@gs... |