Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, biapar, Willr, Ingo, simon_w

Manifest File error...


Reply


6 Posts   2334 Views

Avatar
TCJeter

Community Member, 17 Posts

16 April 2007 at 1:25pm

Just as I have found in this topic (http://www.silverstripe.com/general-discussion/flat/333), I am having problems with the installation page giving an error that is stated in this manner:

Warning: fopen(C:\WINDOWS/manifestC_\PHP_dev_server\www\SilverStripe_sapphire_main.php) [function.fopen]: failed to open stream: No such file or directory in C:\PHP_dev_server\www\SilverStripe\sapphire\core\ManifestBuilder.php on line 105
Cannot write manifest file! Check permissions of C:\WINDOWS/manifestC_\PHP_dev_server\www\SilverStripe_sapphire_main.php

Obviously there was no resolution to the above post either; can someone help? It's taken me quite a while to get this far and I'm hoping it will be worth the effort.

Thanks,
-TC

Avatar
Ingo

Forum Moderator, 801 Posts

16 April 2007 at 6:32pm

looks like the manifest-file has invalid characters (backslashes).
can you try replacing this line in the manifestbuilder? i added an issue in our bugtracker to validate this behaviour as well.

sapphire/core/ManifestBuilder.php:14
-define("MANIFEST_FILE", TEMP_FOLDER . "/manifest" . str_replace(array("/",":"),"_", $_SERVER['SCRIPT_FILENAME']));
+define("MANIFEST_FILE", TEMP_FOLDER . "/manifest" . str_replace(array(' ','\\','/',':'),"_", $_SERVER['SCRIPT_FILENAME']));

just in case: can you check that your tmp-path is correctly set in php.ini (and writeable by the webserver-user)?

Avatar
TCJeter

Community Member, 17 Posts

17 April 2007 at 6:48pm

Ingo-

Thanks for the information. That got me one step closer; I'm thinking that I don't have the php.ini squared away as the error I receive after the insallation is done is:

Not Found

The requested URL /SilverStripe/home/successfullyinstalled was not found on this server.

So, what would the (explicit) line within the php.ini be that controls the tmp-path? I couldn't find anything except for the tmp notations for upload_tmp_dir and session.save_path.

I have this setup as a development server on my local machine. Everything in the installation checklist is there and it generates the appropriate db tables. If this is a PHP or Apache issue I can appreciate that it's not necessarily in the scope of your support (or these forums).

Thanks for your time,
-TC

Avatar
Ingo

Forum Moderator, 801 Posts

17 April 2007 at 10:15pm

sorry, wrong lead - the temp-path php uses is actually an environment-variable (not stored in php.ini). see http://www.php.net/tempnam

so you fixed the permission-problem? your last error looks like an .htaccess/mod_rewrite-problem - can you check your access/error/phperror-logs and confirm that you allow htaccess-redirects in your apache-config?

Avatar
TCJeter

Community Member, 17 Posts

18 April 2007 at 4:18pm

Edited: 18/04/2007 4:20pm

Ingo-

Yes - in fact I had overlooked the fact that I has had a second go at installing Apache and had overwritten the previously edited config file. That was the issue.

It is operational now. The AllowOverride rule was set to 'None' rather than 'All'

Thanks for your help,
-TC

Avatar
KDB9000

Community Member, 1 Post

9 May 2007 at 1:30am

Edited: 09/05/2007 1:31am

I am having the same problem. Half of it has to do with my OS I think. It is called SME Server and it is built on Cent OS 4 (linux). I made the change in the Manifest but is still messed up. It wants to put it in:

/tmp/manifest_home_e-smith_files_ibays_silverstripe_html_sapphire_main.php

The home e-smith files and all that I the path to to the main.php file. The tmp is there and writable but it is on the system itself and not in the par were all my web files are. Anyone have any ideas oh to fix this? Was also having rewrite problem when I did get it going, and i have the module and everything, it was calling a file that wasn't there.