STS includes problems not addressed adequately

[jsbthree]

Warning: main(includes/filenames.php) [function.main]: failed to create stream: No such file or directory in /usr/hsphere/local/home/rustyw/rocksit.com/catalog/includes/application_top.php on line 53

 

Fatal error: main() [function.main]: Failed opening required 'includes/filenames.php' (include_path='.:/usr/local/lib/php') in /usr/hsphere/local/home/rustyw/rocksit.com/catalog/includes/application_top.php on line 53

 

Usually after reading the entire history of posts (all the way back to Sept) one can get at least a clear idea of what the problem is. This seems to have been croping up in one form or another over and over. There doesn't seem to be an answer or better put there are alot of answers which seem to be theories or quick fixes but no step by step definitive post. Why???

 

Am I missing a post somewhere that answers this?? If so I am not alone. Can someone point me the way.

 

I've tried this 20 times and have narrowed it down to this possibility: Something about the way Scripta (used to be Fantastico to some) installs OSC on Linux 8.2, 7.X, 9 causes the evaportation of includes/filenames.php even though it is in the OSC version being installed from CVS or according to the install script it is. So one must assume the Scripta is not telling the truth about which version or it is modifying the version without any documentation to that efffect.

 

This is my possible answer and I'd love to hear any kind of feedbadk or again, a pointer to the simple unified TRUE answer to the problem.

 

Many thanks. :huh: :D

[ozcsys]

I've tried this 20 times and have narrowed it down to this possibility:  Something about the way Scripta (used to be Fantastico to some) installs OSC on Linux 8.2, 7.X, 9 causes the evaportation of  includes/filenames.php even though it is in the OSC version being installed from CVS or according to the install script it is.  So one must assume the Scripta is not telling the truth about which version or it is modifying the version without any documentation to that efffect.

 

This is my possible answer and I'd love to hear any kind of feedbadk or  again, a pointer to the simple unified TRUE answer to the problem.

 

Many thanks. :huh:  :D

Instead of using something that comes with your hosting account I think you are better off using the version you can download from this site and install it yourself. I found that the ones included with my accounts was outdated and by a lot of the posts I have read it is very common.

 

I have been using STS on a couple of different sites and have not had any problems with it at all so it might well be a version problem.