Last modified: 2010-05-15 15:28:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T2636, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 636 - include_path not correct after install
include_path not correct after install
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.3.x
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-03 02:03 UTC by Peppone
Modified: 2010-05-15 15:28 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Peppone 2004-10-03 02:03:40 UTC
I just installed MediaWiki but when I had configured it I got this error message
when going to the root:

Warning: main(C:\apachefriends
mpp\htdocs\bastard/PHPTAL-NP-0.7.0/libs/GetText.php): failed to open stream:
Invalid argument in
C:\DOCUME~1\Peppone\LOCALS~1\Temp\tpl_0_7_0_b3cc3e673392338ec9834517ef3cca2f.php
on line 1

Fatal error: main(): Failed opening required 'C:\apachefriends
mpp\htdocs\bastard/PHPTAL-NP-0.7.0/libs/GetText.php'
(include_path='.;C:\apachefriends\xampp\htdocs\bastard;C:\apachefriends\xampp\htdocs\bastard/includes;C:\apachefriends\xampp\htdocs\bastard/languages')
in
C:\DOCUME~1\Peppone\LOCALS~1\Temp\tpl_0_7_0_b3cc3e673392338ec9834517ef3cca2f.php
on line 1

I can see that the paths are not correct (/) but haven't been able to change
them to the right ones.
I am running ApacheFriends XAMPP 1.4.5 on Windows XP (SP1).
Comment 1 JeLuF 2004-10-03 10:11:39 UTC
Those paths should be set in your LocalSettings.php,
about line 3 or so.
Comment 2 Peppone 2004-10-03 10:44:57 UTC
$IP = "C:\\apachefriends\\xampp\\htdocs\\bastard";
ini_set( "include_path", ".;$IP;$IP\includes;$IP\languages" );
require_once( "DefaultSettings.php" );

How do I change ini_set() to print \ instead of /? I've tried it with no luck.
(If I set $IP to "localhost/bastard" paths will be "correct" but the includes
don't work of course.)
Comment 3 JeLuF 2004-10-03 11:58:35 UTC
(In reply to comment #2)
> $IP = "C:\\apachefriends\\xampp\\htdocs\\bastard";
> ini_set( "include_path", ".;$IP;$IP\includes;$IP\languages" );
> require_once( "DefaultSettings.php" );

Make it:

ini_set( "include_path", ".;$IP;$IP\\includes;$IP\\languages" );

The character \ has a special meaning for PHP, one has to use \\ to get a
"normal" \ character.
Comment 4 Peppone 2004-10-04 23:56:43 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > $IP = "C:\\apachefriends\\xampp\\htdocs\\bastard";
> > ini_set( "include_path", ".;$IP;$IP\includes;$IP\languages" );
> > require_once( "DefaultSettings.php" );
> 
> Make it:
> 
> ini_set( "include_path", ".;$IP;$IP\\includes;$IP\\languages" );
> 
> The character \ has a special meaning for PHP, one has to use \\ to get a
> "normal" \ character.

I did that but didn't see that the error messages I got were different from the
first ones.

Warning: main(C:\apachefriends
mpp\htdocs\bastard/PHPTAL-NP-0.7.0/libs/GetText.php): failed to open stream:
Invalid argument in
C:\DOCUME~1\Peppone\LOCALS~1\Temp\tpl_0_7_0_b3cc3e673392338ec9834517ef3cca2f.php
on line 1

Fatal error: main(): Failed opening required 'C:\apachefriends
mpp\htdocs\bastard/PHPTAL-NP-0.7.0/libs/GetText.php'
(include_path='.;C:\apachefriends\xampp\htdocs\bastard;C:\apachefriends\xampp\htdocs\bastard\includes;C:\apachefriends\xampp\htdocs\bastard\languages')
in
C:\DOCUME~1\Peppone\LOCALS~1\Temp\tpl_0_7_0_b3cc3e673392338ec9834517ef3cca2f.php
on line 1
Comment 5 Brion Vibber 2004-12-05 21:03:17 UTC
Please test with 1.4beta.
Comment 6 Antoine "hashar" Musso (WMF) 2005-07-13 21:23:30 UTC
Closing old 1.3 bug, probably fixed since.

Please restest using lastest 1.4 stable, the bug is most probably fixed.
if not, please reopen the bug with full details.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links