| Troubleshooting | ||
|---|---|---|
 |
 |
|
| Troubleshooting | ||
|---|---|---|
| |
|
|
Your first Interchange page should have displayed in your browser as we described. If it didn't, you need to figure out what went wrong. Most of the time, overlooked details are the problem. Double-checking your typing is a good habit to get into.
Here's also the troubleshooting checklist to use when you run into problems:
Have you created directories with the proper names in the proper locations?
Have you misspelled any file names or put them in the wrong directories? Are the files and parent directories readable by the interchange user? Double-check with the ls command.
Did you type letters in the proper case? Remember that both Unix and Interchange are case-sensitive, and for the most part you may not switch upper- and lower-case letters.
Did you type all punctuation, ITL tags, and HTML tags correctly?
Did you restart Interchange if you changed anything in interchange.cfg or catalog.cfg, or if you're in a high-traffic mode?
Check your catalog error log, error.log in your tutorial catalog directory, to see if Interchange reported any errors.
Check the Interchange server error log, error.log in the Interchange software directory, to see if it had problems configuring the catalog in the first place.
View the HTML source of any catalog pages that are loading incorrectly to check for a coding error. The problem may reveal itself when you see what HTML the browser is getting.
The key pseudo-troubleshooting technique that solves 99% of the problems with minimal effort is log file monitoring. Before proceeding, open up a new terminal and run the following (with root privileges): tail -f /var/log/{apache*,interchange}/*log.
Once you have the logs monitored, restart Interchange and visit the catalog's index.html. Any problems should be reported in the logs.
| |
|
|
| Page Templates |
|
Product Display |