magento2: Update to 2.0.4: The specified value "{{currentPage}}" is not a valid number.
Steps to reproduce
- Install Magento 2.0.2.
- In admin panel, open “System” > “Web Setup Wizard” and select “System Upgrade”
Expected result
- Upgrade wizard
Actual result
UI error:
“Sorry, we can’t take that action right now.”
Console warning:
“The specified value “{{currentPage}}” is not a valid number. The value must match to the following regular expression: -?(\d+|\d+.\d+|.\d+)([eE][-+]?\d+)?”
Which comes from angular.js:8581:
if ( ((startIndex = text.indexOf(startSymbol, index)) != -1) &&
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 25 (16 by maintainers)
Commits related to this issue
- MAGETWO-52439: [Github] Update to 2.0.4: The specified value "{{currentPage}}" is not a valid number. #3977 — committed to magento/magento2 by shiftedreality 8 years ago
- Merge pull request #3977 from magento-mpi/MC-15427 [MPI] Delivery of PaypalCaptcha module — committed to magento/magento2 by viktym 5 years ago
Hi @ktomk, hi @hostep. Thank you guys for caring and for the timely response. That’s a lot more than I see from occasional raids by Magento, Inc. employees 😉
Seen the commit, however: I happen to use a composer-installed version and I have no intent to patch any files in
vendordirectly. It makes me sad that cherry-picking those patches has became the new norm. Especially seeing that are approximately hundreds of such small bugfixes. I think it’s infuriating that one has to collect, apply, and test these fixes manually (making the Magento’s multi-step QA process useless completely). In my opinion, timely (each week) patches would do more good.I do not understand how is this year-old bug still present in 2.1.7 (which is latest released version) and all @veloraven cares about is that it’s fixed on
developbranch. Hooray!All I want is for the fixes to get released by Magento, Inc. in a timely matter. Is that too much to ask?