-
Notifications
You must be signed in to change notification settings - Fork 455
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
concrete5 version 8 with PHP version 7.3 #7138
Comments
Thinking a bit more about this, I'd prefer this third option: |
What is the nature of the bug and the change that we would have to support? |
concrete5 stops running, showing this error message (I don't remember exactly when):
|
if the fix is really just switching Incidentally, I think if concrete5 is going to continue to use dependencies which force latest and greatest versions of PHP there should be some kind of standard plan for handling these sorts of things in place. Because concrete5 is closer to the end user than many libraries are and backward compatibility / longevity is important it would be good to have a standardized approach I think. |
I agree. I think we ought to fork it and fix it and lock to that specific version. Then get back into their doctrine in version 9. I think this ought to be our standard plan. |
Ok. So, what about forking https://github.com/doctrine/doctrine2 to https://github.com/concrete5/doctrine2? If you do that and give me write access to it, I can apply the patch to that fork. |
PS: for example, we can't even install concrete5: we have this error:
|
It seems that PHP 7.3 has a breaking change when parsing regular expressions (bug report), and the |
It’s worth mentioning that we have the concrete5-forks organization, we should use that if we fork Sent with GitHawk |
If you fork https://github.com/doctrine/doctrine2 and https://github.com/sunra/php-simple-html-dom-parser to https://github.com/concrete5-forks and give me temporary write access to them, I can patch them. |
Done 👍 |
We also need to fork |
Done. I added a comment on that issue, it seems reasonable that their 2.7 version is EOL and so they will not make changes to it. What are we actually using that dependency for? I'd bet |
@krebbi concrete5 version 8.5 is the first version that's compatible with PHP 7.3. |
If you upgrade your php version for an existing composer installation of concrete5 please be aware, that you have to update your composer.json: In particular for my case: Additional dependency: IN the "extra" section of your composer.json file:
The current composer.json can be found at: |
what a shame. current release (announched to work with php7) but most of its themes, addons will fail while using php7.4. force the addon development to php7 .. cutoff the compatiblity to php < 7.x to ensure the use with current php. most "out-of-the-box" hoster does not support php5 anymore. |
@dvorpahl ? We run version 8.5.x on PHP 7.4 without issues. |
concrete5 version 8 won't run on PHP 7.3.
The reason is that concrete5 uses Doctrine ORM version 2.5, which is not compatible with PHP 7.3. We'd need to update ORM to the upcoming 2.6.3, but it requires PHP 7.1+ whereas concrete5 version 8 still supports PHP 5.5.9 (see doctrine/orm#7325 ).
I don't think that Doctrine 2.5 will be fixed, so we have 2 options:
I'd go with 2...
The text was updated successfully, but these errors were encountered: