4794 Posts in 1830 Topics by 1443 members
|Go to End|
6 July 2010 at 3:36am Last edited: 6 July 2010 3:53am
I have just discovered Silverstripe and have been really impressed with what I've seen so far.
I installed Silverstripe fine (the latest version) on our local test server (running Fedora and php 5.3.2) on Friday, but have been experiencing a few problems installing it on another the server (running Centos 5, php 5.2.13).
I have loaded up the installer and entered my mysql details fine - all checks pass ok, but then I get a fatal error in cms/_config.php on line 18. For some reason the class 'CMSMenu' is not found.
I have been tracing through the code all day but can't seem to get to the bottom of this one. I have printed get_required_files() to the screen and can see that a cached version of CMSMenu is included. This however is not the class file, but some data relating to class and its parents/interfaces. I can't seem to see how the actual class file is required?
Any help would be much appreciated!
I assume there is a php.ini change I need to make somewhere?
6 July 2010 at 9:58pm
I have now upgraded to php 5.3.2 but am still getting the same problem.
I've noticed that at the point where I get the fatal error, the database hasn't been created. Is this to be expected at this stage?
In order to solve the problem I really need to understand a bit more what is happening in ManifestBuilder. I can see that the code is traversing each directory within my installation and then creating a cache for it. A global variable is also built which has a map between the class and it's path. I just can't see how when CMSMenu is called Silverstripe knows where this is?
My cached files seem to be the same on my working version compared to my non working version..I just can't see what could be wrong with my server setup..
Any help would be much appreciated here - I'm really keen on using Silverstripe, but at the moment I'm really struggling..
6 July 2010 at 11:58pm
My fault - I have an auto prepend file that was requiring the Zend Autoloader class (not great on my part).. This was obviously causing a conflict with the Silverstripe autoloader.
|Go to Top|