-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
Merge v19 -> v20 #2697
Merge v19 -> v20 #2697
Conversation
* Do not crash when shipment does not exist * Redirect to grid if shipment doesn't exist. Co-authored-by: Ng Kiat Siong <[email protected]>
…ndled" products edit page (#2701)
* Remove obsolete ACL resources from DB * Update app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.3-1.6.1.4.php Co-authored-by: Ng Kiat Siong <[email protected]>
* Bugfix to make exchange rate data with fixer.io work again * Added service URL to system config.xml * Use $_url property * Added $_url property to abstract class * Invalid closing tag Co-authored-by: Sven Reichel <[email protected]>
everything should be ok, 28 modified files, same as what you can see here: v19.4.19...1.9.4.x if we merge it we can do a quick hotfix release for the indexer typo |
sorry guys, I had to merge last PRs from today :-( and #2697 had some conficts I hope I merged correctly, these were the files:
expecially lib/Varien/Object.php was tricky, there were a lot of conflicts |
|
@sreichel that "phpVersion: 80000" line is included in the 1.9.4.x branch: https://github.com/OpenMage/magento-lts/blob/1.9.4.x/.github/phpstan.neon and in this PR: https://github.com/OpenMage/magento-lts/pull/2697/files, am I missing something? |
Sorry, i was on wrong branch. |
updated, didn't port #2745 since it's a backport from v20 |
@fballiano i've added a PR to your repo. |
@sreichel merged! |
…2759) * Remove properties accessed from the magic getter * Add properties to class phpdocs Co-authored-by: Sven Reichel <[email protected]>
merged the new ones, #2697 had conflicts, hope the merge is ok :-) |
@sreichel @kiatng question, these kind of PR should be merged with "create a merge commit" right? for sure they shouldn't be squashed, but what about "rebase and merge"? Also (calling @Flyingmana here too), I'd merge and do a release, since the 2 PRs that have been merged in 1.9.4.x are not really about the code but only about the workflows, is that ok? |
I'd merge them normaly to avoid differences between branches. (My next step would be to fix phpstan to work on both) |
Cherry picking from v19.4.19...1.9.4.x