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

2.2.2rc2 can't be installed.


Reply


6 Posts   1673 Views

Avatar
zee

Community Member, 7 Posts

26 March 2008 at 12:05pm

It always gives that error

Installing SilverStripe...

I am now running through the installation steps (this should take about 30 seconds)

If you receive a fatal error, refresh this page to continue the installation
# Creating 'mysite/_config.php'...
# Creating D:\web\root\dev\thecms/mysite/_config.php
# Creating '.htaccess' file...
# Creating D:\web\root\dev\thecms/.htaccess
# Building database schema...

Warning: require_once(D:\web oot\dev hecms/cms/_config.php) [function.require-once]: failed to open stream: Invalid argument in C:\Users\Administrator\AppData\Local\Temp\silverstripe-cacheD--web-root-dev-thecms\manifestD__web_root_dev_thecms_sapphire_main.php on line 282

Fatal error: require_once() [function.require]: Failed opening required 'D:\web oot\dev hecms/cms/_config.php' (include_path='.;D:\Utils\xampp\php\pear\;D:\web\root\dev\thecms/sapphire/parsers/') in C:\Users\Administrator\AppData\Local\Temp\silverstripe-cacheD--web-root-dev-thecms\manifestD__web_root_dev_thecms_sapphire_main.php on line 282

But no problem with 2.2.1

Avatar
zee

Community Member, 7 Posts

31 March 2008 at 8:19am

Any idea, i really need help about that problem.
I don't wanna go with 2.2.1.

2.2.2rc2 or ModX

Avatar
contigo

Community Member, 16 Posts

4 April 2008 at 3:06pm

I had 2.2.2-rc1 installed and working except for one bug. To fix I tried upgrading by replacing rc1's sapphire/, cms/, auth_openid/, jsparty/ files with those of 2.2.2-rc2. It worked. Not sure if this approach would work with 2.2.1->2.2.2-rc2.

-billy

Avatar
Blynx

Community Member, 20 Posts

7 April 2008 at 9:20pm

I've had the same error.
This happens when you install on Windows, because the ManifestBuilder.php does not escape the $baseDir when creating the "require(...)"-statements for the manifest (although it did in version 2.2.1). As Windows uses backslashes in filenames, this causes special characters like \t, \n, \r and so on to be created if your install path contains folders like i.e. \root or \dev.

Fix (or at least hack for the RC2):
add the following lines to the sapphire/core/ManifestBuilder.php:
- after line 91 ($baseDir = ereg_replace("/[^/]+/\\.\\.", "", $baseDir);)
--> add $baseDir = preg_replace("/\\\\/", "/", $baseDir);
- do the same after line 490 (should have the same content as above)

This rewrites the path to use forward slashes instead of backslashes which eliminates the special characters.

Avatar
Sam

Administrator, 685 Posts

7 April 2008 at 9:35pm

Thanks for the analysis; I've recorded this issue here: http://open.silverstripe.com/ticket/2384

Avatar
zee

Community Member, 7 Posts

8 April 2008 at 8:59am

Blynx: Works like magic :), thanks so much, that was what i need.