[ic] catalog config error
Gert van der Spoel
gert at 3edge.com
Tue May 30 10:57:51 EDT 2006
Aaron Berg writes:
>
>> The only other thing I can think of is that you got the change regarding
>> ConfigParseComments in your development environment and that causes some
>> issues with your catalog.cfg ... Change as noted in the WHATSNEW:
>> Developer: jon
>> Date: 2006-01-30 17:44:11 GMT
>> Modified: debian interchange.cfg
>> Modified: dist interchange.cfg.dist
>> Modified: dist/standard catalog.cfg
>> Modified: lib/Vend Config.pm
>> Remove global and catalog directives "ConfigParseComments". Its "no"
>> behavior is now the only one. That means that #ifdef, #include, and
>> friends
>> are now never anything besides comments.
>>
>> Perhaps showing the catalog.cfg might help shed a light on things.
>>
>> CU,
>>
>> Gert
>
> Thanks for the suggestion. I tried changing the ConfigParseComments
> from 'No' to 'Yes' without any effect. I've done a new copy of the
> catalog, which still has issues. Originally I was getting the same
> error in theme.cfg, but removed the inline stylesheet (declared inside
> an ifdef) which resolved that. The theme.cfg error is as follows:
> ------
> In line 0 of the configuration file 'templates/foundation/theme.cfg':
>
> catalog_name config error: Failed to close #ifdef on line 18.
> In line 0 of the configuration file 'templates/foundation/theme.cfg':
> -----
>
> If I remove the content of this ifdef that theme.cfg error goes away
> and I'm given the catalog.cfg line 74 error. Line 74 of catalog.cfg
> includes dbconf/mysql/mysql.cfg. Oddly I get the same error if I
> delete the ifdef around line 74 and it's contents.
>
Btw if you have access to your interchange install, there is quite some
commented out Debug statements in lib/Vend/Config.pm which you could switch
on and perhaps follow easier where things start to break down.
CU,
Gert
More information about the interchange-users
mailing list