Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Magento 2 certain version compatibility changes within days #1040

Closed
anujeetphj opened this issue Feb 15, 2017 · 16 comments
Closed

Magento 2 certain version compatibility changes within days #1040

anujeetphj opened this issue Feb 15, 2017 · 16 comments
Labels
Not DevDocs Issue/PR belongs in different forum; not DevDocs related

Comments

@anujeetphj
Copy link

Feedback on page: /guides/v2.1/install-gde/system-requirements-tech.html

I'm using Magento 2.1.3 version . My reason to choose the latest version was to have all the patches to the issues fixed till now. But it's been just a month that I've started using this in my project suddenly on the requirements page I see that that my Magento version requires different php version though it ws not mentioned on the day I installed it!

Don't you think you should resolve issues other than giving a list of supported versions that even changes within days.

Completely dissatisfied with Magento 2.1

@ghost ghost self-assigned this Feb 15, 2017
@ghost
Copy link

ghost commented Feb 15, 2017

System requirements weren't changed; can you clarify where you saw the PHP version originally? You say "suddenly" you see a different PHP version than you saw "the day you installed it". I'm not sure where the discrepancy is coming from. Thanks!

@anujeetphj
Copy link
Author

anujeetphj commented Feb 15, 2017 via email

@ghost
Copy link

ghost commented Feb 15, 2017

Please provide these details:

  • PHP version (do you have more than one installed?)
  • Error message text

Thanks

@anujeetphj
Copy link
Author

anujeetphj commented Feb 15, 2017 via email

@anujeetphj
Copy link
Author

anujeetphj commented Feb 15, 2017 via email

@ghost
Copy link

ghost commented Feb 15, 2017

Magento does not support PHP 7.1. Did the system requirements page confuse you on that point?

We're considering changing that page. I apologize for the confusion it caused.

@anujeetphj
Copy link
Author

anujeetphj commented Feb 15, 2017 via email

@ghost
Copy link

ghost commented Feb 15, 2017

Assuming you want to stay with PHP 7:

All 2.1.x versions support: 7.0.2, 7.0.6–7.0.x

Not supported by any 2.1.x version:

PHP 7.1
PHP 5.5

@ghost
Copy link

ghost commented Feb 15, 2017

Even though PHP 7.1 is not supported, I suggest you raise an issue in the Magento 2 GitHub because it doesn't seem like you should have been able to install Magento in the first place.

@anujeetphj
Copy link
Author

anujeetphj commented Feb 15, 2017 via email

@ghost
Copy link

ghost commented Feb 15, 2017

PHP documentation

@anujeetphj
Copy link
Author

anujeetphj commented Feb 15, 2017 via email

@ghost
Copy link

ghost commented Feb 15, 2017

I'm not sure, I'm sorry. You can ask this on stackexchange or the Magento 2 GitHub.

@ghost ghost added the Not DevDocs Issue/PR belongs in different forum; not DevDocs related label Feb 15, 2017
@orlangur
Copy link

Hi again, @anujeetphj,

can you please explain why I'm getting the warnings from today?

This happened because of PHP configuration change on your side as explained here.

Will skipping warnings for deprecated functions can solve the issue once
or the compatibility issue may cause other problems in the future as well?
if I will override the file in which I'm getting errors with my
own custom file and use replacements for deprecated functions. Will it
work?

Skipping warnings in general cannot cause any troubles by itself. In particular, deprecated mcrypt_* functions work in PHP 7.1 just like in PHP 7.0, only trigger E_DEPRECATED notice. So, if you suppress these warnings it should work fine until PHP 7.2, where these functions will be removed.

Note that there are other backward incompatible changes between PHP 7.0 and 7.1 which may cause malfunction of your Magento instance in some scenarios. So, you may use PHP 7.1 with some tweaks like E_DEPRECATED suppressing for development purposes but you shall not use it in production until PHP 7.1 is officially supported.

Hope it makes situation completely clear to you.

@tanberry
Copy link

Thanks @orlangur !!

@ghost
Copy link

ghost commented Mar 5, 2017

No comments or info for >14 days, closing. Feel free to open another issue if there's something we can help you with.

@ghost ghost closed this as completed Mar 5, 2017
magento-cicd2 pushed a commit that referenced this issue Jul 31, 2017
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Not DevDocs Issue/PR belongs in different forum; not DevDocs related
Projects
None yet
Development

No branches or pull requests

3 participants