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

UI Component forms not related with any model throw fatal error #13573

Open
mgarciaebo opened this issue Feb 8, 2018 · 8 comments
Open

UI Component forms not related with any model throw fatal error #13573

mgarciaebo opened this issue Feb 8, 2018 · 8 comments
Assignees
Labels
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 Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR Created Indicates that Pull Request has been created to fix issue 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 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@mgarciaebo
Copy link

mgarciaebo commented Feb 8, 2018

It seems that it's impossible to create stand-alone forms using UI Components. I mean, simple forms, not attached to a collection (like the standard import-export forms), because Magento expects for a collection in order to apply filters, and a bunch of other things.

Those kind of forms can still be inserted using blocks and layout injection, as usual, but you encourage us to use UI Components. Actually, classes as Backend\Block\Widget\Form and Backend\Block\Widget\Form\Generic, has been deprecated in favor of UI Component implementation, so it makes no sense that this doesn't work.

Preconditions

  1. Magento 2.2.2; 2.3-develop
  2. Standard LAMP environment - PHP 7.1 - MySQL 5.6

Steps to reproduce

  1. Starting from a vanilla Magento, download, install and enable your own sample Form UI Component, following the instructions given at: https://github.com/magento/magento2-samples/tree/master/sample-module-form-uicomponent
  2. Go to the URL provided by the extension, which is [magento2-admin-url]/sampleform

Expected result

  1. The following sample form should be displayed:
    sample_form

Actual result

  1. A fatal error is thrown as shown here:
    admin_sampleform_index_index_key_f145dba12a93d0ec1e0bdfa0632d6f8e1fbe34d83a0f36d60001f3293f41610d_
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Feb 8, 2018
@magento-engcom-team
Copy link
Contributor

@mgarciaavz, thank you for your report.
We've acknowledged the issue and added to our backlog.

@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 Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Feb 14, 2018
@mgarciaebo
Copy link
Author

I'm working on this #distributed-cd

@magento-engcom-team
Copy link
Contributor

@mgarciaavz thank you for joining. Please accept team invitation here and self-assign the issue.

@magento-engcom-team magento-engcom-team added the Event: distributed-cd Distributed Contribution Day label Mar 24, 2018
@mgarciaebo mgarciaebo self-assigned this Mar 24, 2018
@sidolov sidolov removed the Event: distributed-cd Distributed Contribution Day label Apr 14, 2018
@mgarciaebo
Copy link
Author

Hi @sidolov,

this issue is fixed here: #13574

Regards!

@engcom-Delta engcom-Delta self-assigned this Aug 2, 2019
@m2-assistant
Copy link

m2-assistant bot commented Aug 2, 2019

Hi @engcom-Delta. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.


@engcom-Delta engcom-Delta added the Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release label Aug 2, 2019
@engcom-Delta engcom-Delta removed their assignment Aug 2, 2019
@ghost ghost assigned mgarciaebo and unassigned mgarciaebo Oct 30, 2019
@sdzhepa sdzhepa added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Jun 2, 2020
@VladimirZaets VladimirZaets added Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. labels Jul 24, 2020
@m2-community-project m2-community-project bot added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Sep 3, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Sep 24, 2020
@magedad
Copy link

magedad commented Mar 31, 2022

@magento give me 2.3.7-p2 instance

@magento-deployment-service
Copy link

Hi @magedad. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

Hi @magedad, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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 Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR Created Indicates that Pull Request has been created to fix issue 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 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
None yet
Development

No branches or pull requests

7 participants