Closed riconeitzel closed 3 years ago
Hi @riconeitzel. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
Hi @riconeitzel, Actual result is not understandable , Request to provide clear steps to get actual results.Hence added label 'Needs Update'
Thanks
@engcom-Delta What exactly is not understandable?
The cause of the issue is:
In the di.xml of the salesarchive module is a hardcoded reference to the sygnifyd_case table … but that table doesn't exists as the module was never installed. This kind of hard dependency breaks the pluggability of modules.
Hi @riconeitzel, Kindly help me in understanding @step 3 "rebuild the sales_order_archive_grid table".How to do it please?
Thanks
I don't see Signifyd in SalesArchive's di.xml in 2.4.2-p1
Check if your version of SalesArchive's composer.json requires magento/module-signifyd. If so, this is not a bug - you've told composer that Signifyd is installed (via "replace") so the necessary code could not be pulled in.
@navarr no, it's just in the "suggest" section
"suggest": {
"magento/module-signifyd": "100.3.*"
},
I will verify with 2.4.2-p1 once I have time to download a copy.
Hi @riconeitzel,
Any update on this ticket please ?
Thanks
Dear @riconeitzel,
We have noticed that this ticket has not been updated for a period of more than 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.
Regards
Preconditions (*)
Magento Commerce Edition, 2.3 and 2.4
To prevent the installation of not required modules we used composer's "replace" feature to strip out unnecessary core modules from the magento meta package. This should improve performance as not required functionality is not even installed.
Steps to reproduce (*)
Expected result (*)
Actual result (*)
here you can see the two
LEFT JOIN signifyd_case
which are the result of the following entry invendor/magento/module-sales-archive/etc/di.xml