XAMPP 1.7.3 using buggy PHP

[Read Only]

http://www.mediawiki.org/wiki/Download

Warning: PHP 5.3.1 has a bug in it and is not supported by MediaWiki. You should use PHP 5.3.0 or PHP 5.3.2 instead.

And XAMPP is using PHP 5.3.1 precisely

http://bugs.php.net/bug.php?id=50394

Code: Select all

Description:
------------
This is a regression in the [b]PHP 5.3.1[/b] release. When you call a __call() function with a reference parameter, it is silently converted to a value, by the time it reaches the second argument to __call().

This breaks MediaWiki and has no obvious workaround.

If it breaks one of the most used web software then it's a reason good enough to patch XAMPP.

[Altrea]

So XAMPP can not run one of the most used web software... Isn't that a reason good enough to update fix XAMPP?

XAMPP can run Mediawiki. XAMPP 1.7.3 is not the only available version of XAMPP.
The next official stable XAMPP release will be released when its stable.

- Be patient
- or use an earlier version of XAMPP
- or use a different AMP-package
- or install all components seperately

but stop bugging this forum with your unimportant problems.
(maybe you want to discuss your mediawiki problems on a mediawiki related board)

[Read Only]

but stop bugging this forum with your unimportant problems.
(maybe you want to discuss your mediawiki problems on a mediawiki related board)

Can you stop acting like a petulant child?

It's an XAMPP problem if php 5.3.1 is buggy, not a mediawiki problem, proof is bug didn't exist in php 5.3.0 and was fixed in php 5.3.2

So XAMPP is not stable as it is and doesn't support the latest version of the most used wiki software.

[Altrea]

It's an XAMPP problem if php 5.3.1 is buggy, not a mediawiki problem

It's not a XAMPP problem. The __call bug in PHP 5.3.1 was reported in december 2009 when XAMPP was already on the way for the next stable release 1.7.3.
If XAMPP would only include 100% bugfree components it will never be released, because no software is absolutely bugfree.

It is a PHP problem. But more than that it is YOUR problem. You have the choice which software you want to install.
You have the choice if you want to use XAMPP or not. If you want to, then you can only get what is released.
Maybe you come to the opinion, that XAMPP is not the right software package for you. Thats okay, XAMPP can't fit all the needs all over the world.
If you don't want to install an older version of XAMPP you don't have to. Noone forces you to do.

Can you stop acting like a petulant child?

I gave you enough choices how to solve your problems. But it seems you don't want to. Thats not my problem.

So XAMPP is not stable as it is and doesn't support the latest version of the most used wiki software.

boohoo

[Read Only]

boohoo

OK now it's obvious you're just a troll, GTFO of my threads.

[JonB]

Read Only -

Your mouth is way big, and your knowledge is miniscule (and that is being generous).

Just SO the all-important YOU understands - XAMPP's developers have nothing to do wth creating PHP - read that - N-O-T-H-I-N-G. The source code for ALL PHP versions - comes from PHP.ORG. That source code is untampered with by XAMPP, then compiled for a Win32, thread-safe, VisualC 6 version - so all the PHP bugs stay in 'by version'. What the XAMPP developers do is get it all to work together on FOUR different platforms - much more work that a tiny brain like yours can envision obviously.

SO IF YOU WANT TO WAIL ABOUT BUGGY PHP - go wail at php.org

OR - as I said in the other thread - install it all separately yourself.

At the moment, BTW, we are waiting on a PHP fix (by the PHP folks, NOT US) for a new XAMMP, but 'we' can't fix that - just like 'we' can't fix MySQL, Mercury or any of the other components. THEY ALL COME FROM OUTSIDE SOURCES -

[Read Only]

Read Only -

Your mouth is way big, and your knowledge is miniscule (and that is being generous).[/u]

Thanks for you generosity. IMO you're the one who is stupid and I am a bit generous by saying so.
Did I ever imply XAMPP was coding PHP? No I didn't.
Did you even read OP:

Warning: PHP 5.3.1 has a bug in it and is not supported by MediaWiki. You should use PHP 5.3.0 or PHP 5.3.2 instead.

In other words the bug is already fixed in php 5.3.2 and last version of php is 5.3.3, you talked as if 5.3.1 currently used in XAMPP was the last version.

http://bugs.php.net/bug.php?id=50394

Code: Select all

Description:
------------
This is a regression in the PHP 5.3.1 release. When you call a __call() function with a reference parameter, it is silently converted to a value, by the time it reaches the second argument to __call().

This breaks MediaWiki and has no obvious workaround.

If it breaks one of the most used web software then it's a reason good enough to patch XAMPP.

BTW This thread is for XAMPP devs, not a lowlife like you.

[Altrea]

If it breaks one of the most used web software then it's a reason good enough to patch XAMPP.

No it's not.
But you don't want to hear the solutions. You just want to say that the developers of XAMPP had to do these or do that.
They have to do nothing! They do all this work for free (just like the little helpers here in the board like JonB or me).

If you think, you can do this work better, then do so. Work on your own "every time up to date and as portable as XAMPP" AMP package.
The more i read from you, the more i think you are the troll of us.

I don't think that you get any more help from anyone here.
I'm out here. I wish you good luck

[JonB]

good luck, you don't have to worry about me responding any longer

please do whatever you think is the right thing.

[john585]

This bickering is quite frustrating for us bystanders sharing the problem. Perhaps the post title or some of the contents are inflammatory, but can we please not take the bait, and make an empirical response to the actual issue at hand.

I understand there are some solutions. Here is the efficient solution I am wondering about:

Is there a way to upgrade (or downgrade) the version of PHP once XAMPP is installed?

I am about to resort to this, but I have to accept the risk of dinging something in xampp. If I do this, I will post my findings to try to help others in the support forums.

My original (and safer) thought was to downgrade to a previous version of XAMPP with a mediawiki-compatible version of php, but I cannot seem to find a place to download older XAMPP versions.

/sheesh/

[Altrea]

My original (and safer) thought was to downgrade to a previous version of XAMPP with a mediawiki-compatible version of php, but I cannot seem to find a place to download older XAMPP versions.

You can download all the old XAMPP versions here at sourceforge

[john585]

Thanks for that link- I will do that.

My test of simply downloading the latest php, extracting it, placing it in the C:\xampp folder and renaming it php (after renaming the origonal php to something else) did not work- as I had low expectations in the first place

[JonB]

I am about to resort to this, but I have to accept the risk of dinging something in xampp. If I do this, I will post my findings to try to help others in the support forums.

Without getting technical, you will almost assuredly break your installation due to the fact that PHP (as it is configured in XAMPP) is dead-tied (like in a death-grip-embrace) with the Apache webserver - they are effectively a 'co-compile'. There is no real pracrical way to do this, even if you were expert. The only correct 'mix and match' solution for PHP and Apache is to perform standalone installations - this goes for WAMP as well as XAMPP. I'll post the techie's whys and wherefore of my statement (and why OpenSource doesn't 'patch') on the Ecruciatingly Correct Guide this weekend probably.

I'm posting this mostly to emphasize and clarify a bit why this is such a big deal, as I see you intend to back-track to a Wiki-friendly PHP.

Good Luck with your project.