Before this, I had been trying in vain to get SSI and especially SSI calling a script to work (see this topic). My .shtml page worked fine including the results of the script. However, I couldn't check the .phtml page because Windows foiled me again! I assume it's fine. BTW, it's a simple script, just another version of "Hello, world".
TO SUM UP:
- I did remember to stop and start Apache with XAMPP Control after making the changes (SEE PREVIOUS POST).
- SSI would NOT show output of a script in an .shtml or .phtml page.
- Windows problem shut Apache down.
- XAMPP Control showed Apache still running after disk stopped churning, so I clicked "Stop" there, then "Start".
- The page I was able to view now shows the output of the script. (It didn't before.)
- Windows shuts Apache down again (and keeps doing it).
There is mention in the Apache docs that setting "MaxRequestsPerChild" can be useful to guard against memory leaks taking over all your memory, and right now it is set to "0" (UNLIMITED), the default. Maybe I should set it...what would be a good value? (This is not a production server, but I have a tendency to view pages multiple times in my browser...Firefox, except for fine-tuning CSS) while editing. Do you think this could be a memory-leak problem causing random errors?
BTW...I just now tried using a port other than 80, though I can't think of any software that would be using that port. It didn't help, just in case anyone was thinking of throwing that suggestion out. I used 8080 and still there is a problem with the server.
In fact, Windows just supposedly stopped Apache, twice. It still showed in XAMPP Control that Apache was still running, so I stopped it there so I wouldn't keep getting alerts that Apache needs to close. Once I get the alert, I can't access anything on localhost, seeming to indicate the server is indeed stopped, but the control program says otherwise.This is very, very strange.