Skip to content
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

Invalid parameter configuration provided for $block argument upon no ACL permissions to the block #12660

Closed
Tomasz-Silpion opened this issue Dec 13, 2017 · 2 comments
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@Tomasz-Silpion
Copy link
Member

Tomasz-Silpion commented Dec 13, 2017

Preconditions

  1. Reproduced on clean magento 2.2.0, 2.2.1 and 2.2.2 (current develop branch)

Steps to reproduce

  1. Create new admin user role with customer tab permissions only
  2. Assign new admin user to the role
  3. Login as the user
  4. Try to create new customer

acl

Expected result

  1. New customer form is shown

Actual result

  1. Invalid parameter configuration provided for $block argument of Magento\Ui\Component\HtmlContent" exception is thrown

customer_form.xml addons restricted to selected ACL permissions such as Newsletter/view/base/ui_component/customer_form.xml prevent htmlContent block from being created causing boolean passed to Magento\Ui\Component\HtmlContent constructor which demands block to be an instance of BlockInterface

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Dec 13, 2017
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Dec 13, 2017
@magento-engcom-team
Copy link
Contributor

@Tomasz-Silpion, thank you for your report.
We've created internal ticket(s) MAGETWO-85576 to track progress on the issue.

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Dec 13, 2017
Tomasz-Silpion added a commit to lcbrq/magento2 that referenced this issue Dec 13, 2017
magento-team pushed a commit that referenced this issue Dec 13, 2017
…for argument #12661

 - Merge Pull Request #12661 from lcbrq/magento2:2.2-develop
 - Merged commits:
   1. c7abab1
@ishakhsuvarov ishakhsuvarov added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Dec 13, 2017
@ishakhsuvarov
Copy link
Contributor

Hi @Tomasz-Silpion
We are closing this issue now as the fix has been delivered with the commit 3839c0f and should be released with 2.2.4
Thank you.

magento-team pushed a commit that referenced this issue Dec 14, 2017
…tion provided for argument #12665

 - Merge Pull Request #12665 from lcbrq/magento2:2.3-develop
 - Merged commits:
   1. 9516978
magento-team pushed a commit that referenced this issue Dec 14, 2017
@okorshenko okorshenko added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Dec 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

4 participants