Status
Not open for further replies.

DReade83

Well-Known Member
Oct 20, 2006
196
0
166
Cheshire, UK
You are pointing to old version.

PHP Bugs: Search
No, I am not. PHP 5.2.10 is NOT in EA3, 5.2.9 is the current version everyone is using that uses EA3, and according to the PHP site there are over 100 bugs in the version we're all using compared to 70 odd in PHP 5.3, which I'm sure you'll agree is a lot less.

So again, are you really going to base you decision on a list of bugs, even though there are more in the current version than the new one?

Which version are you using?
 

DjiXas

Well-Known Member
Feb 10, 2007
294
0
166
No, I am not. PHP 5.2.10 is NOT in EA3, 5.2.9 is the current version everyone is using that uses EA3, and according to the PHP site there are over 100 bugs in the version we're all using compared to 70 odd in PHP 5.3, which I'm sure you'll agree is a lot less.

So again, are you really going to base you decision on a list of bugs, even though there are more in the current version than the new one?

Which version are you using?
It doesn't matter what build EA got.
You miss the point, those are the bugs for NOT PUBLIC release, I mena they were found by small % of users who were testing it. PHP 5.2 is being used by millions of people.

Millions of people report 100 bugs in 5.2.9
1000 people report same 100 bugs in 5.3.0

Got my point?
 

Spiral

BANNED
Jun 24, 2005
2,018
8
193
Millions of people report 100 bugs in 5.2.9
1000 people report same 100 bugs in 5.3.0
As you will see earlier in this thread, I have made several posts
regarding how ridiculously easy it is to upgrade to PHP 5.2.10
and that there is no major problems to report.

Now regarding PHP 5.3.0, that's a totally different story entirely ...

PHP 5.3.0 has a number of still yet unresolved compatibility issues
and is not at the point I would say is stable enough to safely use in a
production environment and has a lot of issues with cPanel servers
in particular in our initial testing.

Currently at this time, we do not recommend going to PHP 5.3.0

However, we *DO* recommend immediate upgrade to PHP 5.2.10
as discussed in detail in our previous posts in this thread above as this
is a very good version with no major problems of significance to report!
 
Last edited:

DReade83

Well-Known Member
Oct 20, 2006
196
0
166
Cheshire, UK
cPanel haven't released PHP 5.2.10 because of compatibility issues with a number of scripts and additional modules, such as IonCube. I don't know why you're recommending upgrading to 5.2.10 when clearly it's not stable enough itself?!
 

carluk

Well-Known Member
Sep 2, 2003
161
0
166
> PHP 5.3.0 has a number of still yet unresolved compatibility issues

Such as?
 

Spiral

BANNED
Jun 24, 2005
2,018
8
193
cPanel haven't released PHP 5.2.10 because of compatibility issues with a number of scripts and additional modules, such as IonCube. I don't know why you're recommending upgrading to 5.2.10 when clearly it's not stable enough itself?!
You don't know why we are recommending PHP v5.2.10? :D

That would be because PHP v5.2.10 is very stable and we have been
testing it for quite some time since it's ealiest original builds well before
and including the current official release and cPanel often (as now again)
doesn't have the slightest clue what they are doing half of the time
for things like this often attibuting what they think are issues to entirely
the wrong causes many times. Long story :rolleyes:

In reality though, we have extensively tested 5.2.10 and we can
say with full and good confidence from our own tests ...

There are no major issues with any scripts or any problems noted with
PHP 5.2.10 and we cannot duplicate the source of any other complaints!
(This actually does in fact say a lot in itself if you read on below)

There are no problems with IonCube which actually works flawlessly
without any issues whatsoever under PHP v5.2.10 and that has been
tested and re-tested and tested again and we are still not certain
where the IonCube association comes into play because it works fine!

If cPanel is running into issues in these areas then they are doing something
wrong in building their test environments which clearly has nothing to do
with PHP version 5.2.10 itself as that version works very well indeed.
We don't disagree with cPanel being prudent with extensive testing but
we do advise caution about making wrong assumptions and attributing
problems where no problems actually occur.

We extensively tested PHP 5.2.10 on a great many servers in hundreds
of different configurations at many different locations and been running it
in full production first hand ourselves for quite some time and were unable to
observe anything to suggest any issues outside of what you might otherwise
already observe in 5.2.8 and 5.2.9. In fact a few items that had minor
bugs in the older recent versions actually work better running under the
newer PHP 5.2.10 in some cases.

Point in fact, what you were told about 5.2.10 is obviously flat wrong!

Carluk said:
> PHP 5.3.0 has a number of still yet unresolved compatibility issues

Such as?
PHP makes a number of functional and structural revisions in PHP v5.3.0
that differs it from PHP v5.2 series enough to break backward compatibility
compliance sufficient enough to be concerned about the operation of
some scripts as many will need some revisions and will require many script
authors to, in some cases, to release minor version updates to their own
respective programs to be more PHP v5.3.0 compatible.

PHP: Backward Incompatible Changes - Manual

While most scripts will generally run well under the newer v5.3.0 without
modifications in many cases, there is no guarantee that will hold true the
majority of cases and there is still a significant enough percentage of
widely used scripts on the open market that we used on test servers that
will haveto be patched or re-written by their respective code authors
to operate correctly after upgrading to v5.3.0

PHP: Migrating from PHP 5.1.x to PHP 5.2.x - Manual
 

carluk

Well-Known Member
Sep 2, 2003
161
0
166
Oh, I already know of those changes as I read the announcement. I thought you had other issues other than those.
 

Spiral

BANNED
Jun 24, 2005
2,018
8
193
Oh, I already know of those changes as I read the announcement. I thought you had other issues other than those.
Actually we do! In our testing, we have noted a few additional bugs with
PHP v5.3.0 which we subsequently reported to PHP along with possible fix
resolutions but as of this time, those items do not yet appear on the buglist.

The bigger concern at the moment for PHP v5.3.0 is not the list of bugs
as much as the changes effecting backwards compatibility as these are
the items that are going to cause extra work for programmers and server
administrators to get the new PHP v5.3.0 deployed and those particular items
have indeed been documented to the migration manual for PHP v5.3.0.

If you want to skip the headaches for a moment, just go to PHP v5.2.10
as this version has deployed very well in our test environments and doesn't
have any of the new compatibility issues introduced with PHP v5.3.0.
 

carluk

Well-Known Member
Sep 2, 2003
161
0
166
PHP 5.3.0 looks fine to me with regards to it's changes, I don't have any problems with the backwards compatibility issues as listed in the documentation.
 

jdlightsey

Perl Developer III
Staff member
Mar 6, 2007
126
2
243
Houston Texas
cPanel Access Level
Root Administrator
Point in fact, what you were told about 5.2.10 is obviously flat wrong!
It's good to head PHP 5.2.10 has worked seamlessly on your systems, but I assure you the problems I mentioned in my last message are real.

Problems #1 and #2 have been reported by others. #1 only happens when curlwrappers is enabled and might also require the use of a recent version of libcurl. #2 only happens when PEAR is being initially installed (remove the .registry and .channels directories.) You can find other reports of these two issues here:

PHP Bugs: #48603: Installing PHP with PEAR support causes installation error

PHP Bugs: #48625: cannot open phar "/path/php-5.2.10/pear/install-pear-nozlib.phar"

PHP Bugs: #48650: pear broken in 5.2.10

Bug #16366 :: compiling 5.2.10 leads to non-functioning pear

Problem #3 with IonCube was "a flaw in the cPanel code that installed the Ioncube loader". The IonCube loader itself works fine with 5.2.10, this issue simply prevented it from being installed via EasyApache.

As I mentioned, #1, #2 and #3 are already addressed.

Problem #4 is the only issue still holding up PHP 5.2.10 in EasyApache. Until Release and Stable are republished, it's impossible to enable 5.2.10 in the WHM->Service Configuration->Apache Configuration->PHP And Suexec interface on those systems.
 

Spiral

BANNED
Jun 24, 2005
2,018
8
193
It's good to head PHP 5.2.10 has worked seamlessly on your systems, but I assure you the problems I mentioned in my last message are real.
Apparently you did not read my posts careful enough as your statement
above fully illustrates my whole original point that you, and not necessarily
you specifically but others in general, are far too often making quick
wrong assumptions about bugs ideas and perceived issues often thinking
them to be a result of a new recent software release instead of really
digging into the issue and finding out for certain whether an issue really

A) exists or not (or is even a problem).
B) is actually caused by what you think.

On that side note, I never said that you don't have any problems ---

I DID SAY WHAT YOU LISTED IT IS NOT CAUSED BY PHP 5.2.10 THOUGH!

You said it was great that "our systems were working" but that too is
an assumption again assuming that our systems were somehow different
than anybody elses along with the blanket assumption that multiple people
reporting an issue make it necessarily so.

When we test any software release, we locate every conceivable
possible whisper of any problem and learn the real cause and the
real solutions to those problems without any bias or quick assumptions
as you get from 99.9% of the administrator population out there many
often generally too quick to jump the gun to report bugs and attribute
issues to causes for which they cannot even be certain of any
association to the causes they think in the first place.

Problems #1 and #2 have been reported by others. #1 only happens when curlwrappers is enabled and might also require the use of a recent version of libcurl. #2 only happens when PEAR is being initially installed (remove the .registry and .channels directories.) You can find other reports of these two issues here:
Being reported "by others" just simply means you are all equally clueless :D

*** Muffled Tone of Sarcasm ***

On a more serious note though, these aren't PHP upgrade issues and
each of the items you listed below have all been carefully reviewed by
us well before any of my posts above and are all ridiculously easy to correct.
As mentioned briefly above, none of these are actually PHP 5.2.10 issues.

In fact, each of these particular items we had first originally noted along
with other additional items you failed to list when working with the
PHP 5.2.7 code base loaded as the base and yet we still able to replicate
each of those same items again namely those with curlwrappers, curl,
PEAR, and related as you just described and those listed in the not so
accurate bug report logs even when used with 5.2.7, 5.2.8, 5.2.9,
and 5.2.10 which by itself should tell you up front these issues don't
have anything to do with 5.2.10 even before running more detailed
diagnostics which we did diagnose and review all of those in detail.

The quick summary on these without sitting down itemizing every last
tidbit is basically in a nutshell in random order wrong file permissions,
missing library file, folder permission issues, and incorrect configuration
parameters passed installing support library to each of these items
respectively. None of them had anything to do with PHP being upgraded
in and of itself nor the version of PHP being used.

Problem #3 with IonCube was "a flaw in the cPanel code that installed the Ioncube loader". The IonCube loader itself works fine with 5.2.10, this issue simply prevented it from being installed via EasyApache.
Correct. The Ioncube loader works fine with all of the tested versions of
PHP loaded either as a PHP.INI module or as a dynamically loaded module
at runtime both without any problems those whatsoever.

This main issue regarding Ioncube (as you just said yourself) belongs to
Cpanel directly and deals only with their EasyApache code and little to
nothing to do with PHP itself which actually works just fine when Ioncube is
loaded either as an installed module or loaded from script file.

You just need to setup Ioncube manually and that is probably the easiest
of all things to load since there is really nothing to compile or setup and
configuring is as simple as adding a single line to your PHP.INI or script files!

As I mentioned, #1, #2 and #3 are already addressed.
Actually everything is already addressed and beyond. Whether it is PHP,
Apache, or anything else, we generally don't make recommendations on
any software updates or releases unless we've reviewed every possible
potential issue in detail and already know all the real actual causes of
any reports and all the solutions before we even mention anything and
we are always willing to step in and help anyone that needs help and
are not going to leave anyone left standing there scratching their heads
trying to figure out what we already know. ;)
Problem #4 is the only issue still holding up PHP 5.2.10 in EasyApache. Until Release and Stable are republished, it's impossible to enable 5.2.10 in the WHM->Service Configuration->Apache Configuration->PHP And Suexec interface on those systems.
Actually that is not true! That screen works just fine with PHP 5.2.10
right now at this very moment and there is no problem setting the
PHP configurations for your server with PHP 5.2.10 from within the
PHP and Suexec" Apache configuration menu in WHM you mentioned.

What you cannot do at the moment is initially selecting "PHP 5.2.10" to
compile from EasyApache just simply because Cpanel has not added it
to the build list yet but once it has been added to the server (manually),
it can in fact be managed by WHM the same as any other and is also
fully recognized by the Cpanel interface and scripts as well without
any notable problems.

As far as upgrading goes, the best way to do this at the moment until
Cpanel updates their internal build lists is to set EasyApache to build
and compile for PHP 5.2.9 and then simply run a manual compile for
PHP 5.2.10 and manually upgrade that to the new version which
only takes a few minutes and is very easy to do. Hopefully, it won't
take Cpanel long to catch up because PHP 5.2.10 is very nice and
it is not fair that some people have to wait while the rest of us
can go ahead and upgrade now immediately.
 

DReade83

Well-Known Member
Oct 20, 2006
196
0
166
Cheshire, UK
Actually we do! In our testing, we have noted a few additional bugs with
PHP v5.3.0 which we subsequently reported to PHP along with possible fix
resolutions but as of this time, those items do not yet appear on the buglist.

The bigger concern at the moment for PHP v5.3.0 is not the list of bugs
as much as the changes effecting backwards compatibility as these are
the items that are going to cause extra work for programmers and server
administrators to get the new PHP v5.3.0 deployed and those particular items
have indeed been documented to the migration manual for PHP v5.3.0.

If you want to skip the headaches for a moment, just go to PHP v5.2.10
as this version has deployed very well in our test environments and doesn't
have any of the new compatibility issues introduced with PHP v5.3.0.
You've been testing PHP 5.3 final though right, even though it's only be released for a day? I personally have managed to install PHP 5.3 on a separate box without problems, and run the current version of our company website on that box, with 5.3, no problem! No segmentation faults, no problems found - it just seems to work! So on that note I'm sure that will be the exact same situation for many other people. I just don't understand how you've managed to do all these tests when the final version of 5.3 has only been out a day or so?!
 

cPanelKenneth

cPanel Development
Staff member
Apr 7, 2006
4,607
79
458
cPanel Access Level
Root Administrator
You've been testing PHP 5.3 final though right, even though it's only be released for a day? I personally have managed to install PHP 5.3 on a separate box without problems, and run the current version of our company website on that box, with 5.3, no problem! No segmentation faults, no problems found - it just seems to work! So on that note I'm sure that will be the exact same situation for many other people. I just don't understand how you've managed to do all these tests when the final version of 5.3 has only been out a day or so?!
Spiral mentioned earlier that he tests the pre-release versions.
 
Status
Not open for further replies.