View Issue Details

IDProjectCategoryView StatusLast Update
0014012mantisbtbugtrackerpublic2012-05-24 18:50
Reporterrfoster Assigned Tograngeway  
PrioritynormalSeverityblockReproducibilityhave not tried
Status closedResolutionno change required 
Platform3rd Party Hosting ProviderOSWindows OS VersionServer 2008 R2
Product Version1.2.9 
Summary0014012: Internal Server Error 500 caused by realpath returning false in core.php
Description

After installing on a hosted windows 8 server I received the dreaded 500 Internal Server error. The hosting provider support supplied the following log entry from the server:

PHP Warning: require_once(utf8/utf8.php) [function.require-once]: failed to open stream: No such file or directory in C:\HostingSpaces\xxx\xxx.xxx.com.au\wwwroot\core.php on line 131 PHP Fatal error: require_once() [function.require]: Failed opening required 'utf8/utf8.php' (include_path='C:\HostingSpaces\xxx\xxx.xxx.com.au\wwwroot\core\;\library;.;C:\php5\pear') in C:\HostingSpaces\xxx\xxx.xxx.com.au\wwwroot\core.php on line 131

after some investigation I found that the line:

define ( 'BASE_PATH' , realpath( dirname(FILE) ) );
on line 90 of core.php

was returning false.

changing it to

define ( 'BASE_PATH' , realpath( dirname(FILE) ) ? realpath( dirname(FILE) ) : '.' );

resolved the issue.

Steps To Reproduce

insufficient information on hosting provider's environment.

Additional Information

PHP Version 5.2.8

Configure Command:

cscript /nologo configure.js "--enable-snapshot-build" "--enable-debug-pack" "--with-snapshot-template=d:\php-sdk\snap_5_2\vc6\x86\template" "--with-php-build=d:\php-sdk\snap_5_2\vc6\x86\php_build" "--disable-zts" "--disable-isapi" "--disable-nsapi" "--with-pdo-oci=D:\php-sdk\oracle\instantclient10\sdk,shared" "--with-oci8=D:\php-sdk\oracle\instantclient10\sdk,shared"

TagsNo tags attached.

Relationships

related to 0012341 closedjreese missing php librarys 

Activities

grangeway

grangeway

2012-05-12 18:15

reporter   ~0031823

The code in question has been rewritten post the 1.2.x releases [i.e. in our dev releases]

Seeing as this looks specific to your hosting environment. you've work-around it, and the code has been changed - making as resolved - no change required