Re: [cobalt-users] I give up - revisited

[Lew Mark-Andrews <lew.ml@xxxxxxxxxxxxx>]

>Well, in a last ditch effort to "not give up" I went in and made one change
>and now instead of "unable to connect to database" error I am apparently
>connecting and getting "warning, unable to write to ..." errors.
>
>www.kbionline.net/catalog/default.php

Hey, don't give up!

Somewhat selfish reason: I've also had an interest in osCommerce, but
besides downloading the files and having a leisurely look at how it's put
together, I don't expect to be able jump into it for another two weeks or
so at the earliest, and then to do it as a Japanese language version. Was
lurking and hoping to see your detailed success notes in the archive. :-)

But, anyway, thought I'd give a shot at least at the error you mentioned.

I see most of the "write to" errors on your default.php page are:
"Warning: error_log: Unable to write to
/usr/local/apache/logs/exchange/parse_time_log in
/home/sites/home/web/catalog/includes/functions/database.php on line 24"
(similar on other lines)

So, it can't write to a log (exchange/parse_time_log) it's expecting to be
at that location upon a function call from "database.php." Hmm, sure sounds
like permissions, if the file exists. FWIW, both the path to the log file
and the option to log the "time it takes to parse" are in
"includes/application_top.php" which IIRC is the same file you were making
settings in a few messages back, in here:
  define('STORE_PAGE_PARSE_TIME', 0); // store the time it takes to parse a
page
  define('STORE_PAGE_PARSE_TIME_LOG', DIR_FS_LOGS . 'exchange/parse_time_log');

But in fact, further searching around showed an answer right in the FAQ
file that's included in the tep-pr2.1 Folder:
## 06 ##
q. I receive an error of not being able to write to the parse_time_log file.
a. This file needs to have the correct write permissions for the apache
user to be able to write to it. If you continue to get this error, create a
0 byte file with the right permissions.

So, there you have it. One down. Keep going. If you don't give up, guess
you've got to dig around a bit more and get a better overview of what's
where, and what files are being include'd where, so you can debug this
stuff from here on out.

Do you have the PDF + Word doc guides available from the OSCdox Project at
<http://www.oscdox.com/>?

Good luck,
Lew