| 
      
      
      From: Chris W. <ch...@cw...> - 2002-02-15 14:40:33
      
     | 
| On Fri, 2002-02-15 at 08:42, John Sequeira wrote: > Oops - my intent was to use server.ini. I didn't realize the files were > redundant. I thought the latter was generated to validate the former, but > obviously I didn't think about it too hard. > > Anyway, conf/base.conf points to the ini file that I've correctly (AFAIK) > set up. But I'm still getting the "Fundamental part of OpenInteract > (themes) not functioning" error. > > Is there a way to validate or troubleshoot the ini file or otherwise figure > out why the apache startup is carping? Or do I want to look somewhere else? There's no validation for the ini file. The 'Fundamental part of OpenInteract...' error in pre 1.37 versions used to point to a database misconfiguration error. In 1.37 I changed the Apache handler (OpenInteract.pm) to first check whether it could connect to the database. If not, it should report that error rather than the themes error. One thing to check: see whether removing 'SPOPS::Secure' from the 'theme' key in base_theme-x.xx/conf/spops.perl (then restarting the server) makes things work. If so, then there's something fishy about fetching information from the security table for the theme. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |