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

when upgrade magento version 2.3.4-p1 to 2.4.6-p1 then its give error #37819

Closed
5 tasks
nishthaparmar26 opened this issue Aug 1, 2023 · 11 comments
Closed
5 tasks
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.6-p1 Indicates original Magento version for the Issue report.

Comments

@nishthaparmar26
Copy link

nishthaparmar26 commented Aug 1, 2023

Preconditions and environment

Magento Version 2.4.6-p1

update_error1

Steps to reproduce

updating magento version

Expected result

its give me error

Actual result

update_error1

Additional information

please help me to solve this issue

Release note

this error appearing after updating magento version

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant
Copy link

m2-assistant bot commented Aug 1, 2023

Hi @nishthaparmar26. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@m2-assistant
Copy link

m2-assistant bot commented Aug 1, 2023

Hi @engcom-Dash. 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: 👇

    1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
    1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
    1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- 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!

@engcom-Dash engcom-Dash added the Reported on 2.4.6-p1 Indicates original Magento version for the Issue report. label Aug 1, 2023
@hostep
Copy link
Contributor

hostep commented Aug 1, 2023

This has been reported a couple of times before:

To me it doesn't sound like a bug in Magento, but as a missing php extension sodium that's not installed on your machine (maybe only for php-cli?).

@nishthaparmar26
Copy link
Author

thank you for your replay
but i have enable sodium extension in wamp server and this extension show in phpinfo file
but still gating this error

@engcom-Dash
Copy link
Contributor

engcom-Dash commented Aug 1, 2023

Hi @nishthaparmar26 ,

Thanks @hostep for given inputs.
Seems like the Error occurs due to Sodium PHP extension Missing in your system,Kindly recheck with following mentioned comment.
Kindly go through with this 37454 and If you any clarifications,Kindly Let us know.

Regards!

@nishthaparmar26
Copy link
Author

nishthaparmar26 commented Aug 1, 2023

Thank you sir
but still geting error please help me

my magento version is 2.4.6-p1
php version 8.1.0

@hostep
Copy link
Contributor

hostep commented Aug 1, 2023

Make sure sodium is also enabled for php on the command line, usually the command line uses separate php.ini file(s).
See this comment: #35419 (comment)

@nishthaparmar26
Copy link
Author

yes sir in my system sodium extension is enable

@hostep
Copy link
Contributor

hostep commented Aug 1, 2023

Then I'm afraid you'll need to try to figure it out yourself, this is an environmental problem, not a bug in Magento, sorry! So this issue can be closed in my opinion.

Also be aware that Windows isn't supported by Magento, you'd better switch to Linux (or that subsystem Windows has these days for Linux, WSL or something like that it's called ...)

@nishthaparmar26
Copy link
Author

okay thank you

@engcom-Dash engcom-Dash added the Issue: needs update Additional information is require, waiting for response label Aug 2, 2023
@engcom-Dash
Copy link
Contributor

Hi @nishthaparmar26 ,

Seams like issue is not from core magento and its environmental issue,Hence we are closing this issue.Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.6-p1 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

3 participants