New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP5.4 support #1041
Comments
I've got this setup locally, and it looks like there's a fair bit to fix. I know I've already spoken to @brendo about this, but there is some bad API design in here. Functions in subclasses that are overridden must match their parents, ie: symphony/lib/toolkit/class.administrationpage.php public function insertBreadcrumbs(array $values); No, no, no. Please don't do this. public function insertBreadcrumbs($page_id, $preserve_last = true); PHP 5.4 seems to enforce this now, so every instance where someone has decided that the original API didn't suit them and changed it in a subclass needs to be rewritten. saaad panda |
Don't want to sound like I'm moaning, but does this need to be a 2.3.0 priority if PHP5.4 was only released yesterday? Suggest it goes into 2.3.x. (Unless I'm reading the way we're using milestones incorrectly, if so, apologies and I'll go back into my box.) |
I had originally suggested 2.3 as the milestone as I wasn't aware of the number of warnings that PHP5.4 threw with Symphony (naive :(). Tony's work is a solid start, but I concur, not having this support won't block a 2.3 release. I have updated the milestone to reflect this. |
Ah, this is what is 'killing us'. @michael-e is an oracle ;) |
We need to address this, not just recommend changing the setting. Less sloppy code is a good thing. I'll hopefully have more time this afternoon to keep going. |
Ah, yes, sorry that I have never told you. LOL. |
@rowan-lewis got a copy of PHP5.4 today ran into similar warnings. After fixing a couple, we realised that it will be impossible (or very time consuming) to update the core so that it runs on PHP 5.4 (and 5.3) in This work is still important and I don't want to discourage it, but for the 2.3 final it is most likely that we will modify these lines to additionally exclude |
Beginnings of changes for PHP 5.4 support. RE: #1041
@allen, is there a publicly available fork available with the work on removing notices/errors for PHP 5.4 versions? Do you expect this work will be available in a 2.3.x release or will it require 2.4 because of PHP 5.2 support? |
Yep, @nils-werner is keeping a notices fork: https://github.com/nils-werner/symphony-2/tree/notices I've fixed up all the warnings and notices on my repo and am waiting for him to pull in my changes. The fixes can go into |
Ok, great to know. Would like to have these fixes added to the next release (which is more of a hotfix release than anything). I'm hopeful we can have this release out before 2012 is done so we can start fresh in the new year. |
(Just found this thread, sorry about the |
@allen I noticed the PR has been merged by @nils-werner. Are we ok to merge into |
Yes, I have merged what I got from @allen. I don't know if everything has been done, all I know is that the coredevkit extension-submodule has to be removed before you can merge this. |
Could you remove that submodule when you get the chance? I'm sure @allen will chime in here soon :) |
There are still a few more dynamic actions (creating events and data sources) that still triggers notices. Aside from that we're pretty much there. |
Nice work guys. |
Correcting notices and warnings for the greater good of man. RE: #1041
Everyone who has PHP5.4 installed and previously added the dirty little fix... I think we're now at the stage where we can undo this and start to fully test Symphony without it.
|
@brendo |
Just a heads up about the installer when running on
|
Sorry, forgot to ay, that's |
That can't be 2.3.2RC1, the |
Dammit, was just about to delete it in shame. I must learn to remember to checkout the integration branch |
I have been running PHP 5.4 with Symphony now on two servers and have had no issues at all. Can we say this is done? |
+1 I've got PHP 5.4 running locally (for quite a time now) with some 8 SCMS sites mostly updated to 2.3.2 and everything runs well. I did not tried out the latest |
Errors usually occur when the error reporting level is set to We too have most of our Symphony sites running locally on PHP5.4, and a couple in production too. |
Thanks. So we should test all the extensions? I am actually aiming for the 2.3.3 to be able to be released. |
Yeah testing extensions is a great help, especially when using |
Closing this as I don't get any errors now, and we're close to final release. |
I don't get any errors too. |
Just to check, that includes JIT images working, right? I've set up Symphony with PHP 5.4 for the first time today and ran into this image problem. |
Thats nasty :/ I am fine with JIT. |
@DavidOliver, can you log this on JIT's repo please. |
PHP 5.4 is now officially released as a result, Symphony should ensure that is it compatible ASAP.
A migration guide is available from 5.3 to 5.4. From a quick skim we should be OK, but it's better to be safe than sorry (We know for a fact that the
2.2.x
branch produces errors under 5.4).Related issues:
The text was updated successfully, but these errors were encountered: