-
Notifications
You must be signed in to change notification settings - Fork 111
PHP7.2 getAllOptions() #139
Comments
hey there, thx for reporting. If you're looking for solution, please check develop branch, most of php 7.2 things is already resolved there https://github.com/Inchoo/Inchoo_PHP7/tree/develop |
Thanks! Is there a reason it's not released yet ? Something wrong, or missing ? |
Note : codePool has been moved from local to community, however the extension is still located to local folder.. |
🤦♂️ my bad, fixed 😅 thx for reporting We're currently working with Magento directly on the official 7.2 patch. This will include some changes and a lot of additional testing across versions. So, hopefully, v.3.0 of this extension won't be needed |
That's a great news, well done ! :) |
Well, It's not in yesterday release 1.9.3.9 :'( Do you have intel about ETA ? (: |
work in progress, sorry no dates yet |
@ivanweiler Any updates on this? |
Any updates ? |
@Nuranto , we're runningMagento 1.9.3.7 with Inchoo_PHP7 (v3 on the development branch) on PHP 7.1 and it works fine. If you can't wait until the new Magento 1 version, then I would suggest you just start patching your sites with the version that's currently on the development branch. |
The official Magento patch for PHP 7.2 landed yesterday, see: https://magento.com/tech-resources/download#download2240 |
It won't make 1.9.3.10 which is due on monday, but will be included in next release. |
That's great news. So that patch/1.9.3.10 will obsolete this extension I presume. Curious to know whether the fixes will have been implemented the same way. |
Already mentioned in #126 :
PHP Fatal error: Declaration of Mage_Customer_Model_Resource_Address_Attribute_Source_Country::getAllOptions() must be compatible with Mage_Eav_Model_Entity_Attribute_Source_Table::getAllOptions($withEmpty = true, $defaultValues = false) in magento/app/code/core/Mage/Customer/Model/Resource/Address/Attribute/Source/Country.php on line 0
There is actually several classes like this...
The text was updated successfully, but these errors were encountered: