PHP Fatal error: Uncaught Error: Class "DOMDocument" not found in /home/bumbinguglies/public_html/vendor/magento/framework/Config/Dom.php:449Stack trac about magento2 HOT 9 CLOSED

Hi @georgittanchev. 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:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

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.

from magento2.

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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. 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!

• Join Magento Community Engineering Slack and ask your questions in #github channel.

from magento2.

Hi @georgittanchev ,

Thanks for collaboration and contribution !

verified the issue 2.4-develop instance and the issue is not reproducible.

Kindly refer the below screenshots:

Steps to reproduce:
I.install magento install using composer command
2.Verify Front-end Luma theme working or not

We are getting luma theme after composer installation and issue is not reproducible.Kindly recheck the behaviour in 2.4-develop instance as well as kindly update your magento 2.3.5 with latest version and recheck the behaviour.

Let us know if are missing anything!

Thanks!

from magento2.

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

from magento2.

Hi @georgittanchev, here is your Magento Instance: https://af759bd424aeff5ab3fa72d4228440a2.instances-prod.magento-community.engineering
Admin access: https://af759bd424aeff5ab3fa72d4228440a2.instances-prod.magento-community.engineering/admin_d0d2
Login: ec53e00c
Password: c702747d3afc

from magento2.

The issue at hand pertains specifically to Magento 2.3.5, which is being run in conjunction with CloudLinux and WHM. I am uncertain as to where and why you have conducted your tests using version 2.4, considering that the problem arises from version 2.3.5. I am inclined to carry out an upgrade test for Magento via the terminal. However, I am impeded by the fact that I am unable to install it initially.

I would appreciate it if you could clarify on which operating system you are installing Magento 2.4 and delineate the exact commands you are employing. As it stands, there are servers where installation proceeds without a hitch. On this particular server, though, a particular issue arises. Despite the dom extension being enabled, Magento, for some reason, seems unable to locate or detect it, thus triggering a PHP Fatal error.

It is imperative to note that conducting tests on version 2.4 does not provide a resolution to our current drawback.

from magento2.

Hi @georgittanchev ,

Thanks for Contribution and collaboration!

Currently we are using magento 2.4 in Mac OS version 12.6.5 and we are using 2.4-develop branch because this is the latest development branch, and it might be possible the issue you mentioned is already been resolve in this branch.

Please try to reproduce the issue in 2.4-develop or latest stable version.

Thanks!

from magento2.

Hi @georgittanchev ,

Do you need Any further investigation in this issue ???,If it is kindly let me know.

Thanks!

from magento2.

Hi @georgittanchev ,

As we are not able to get the latest update on the issue. We are closing the issue for now. Please feel free to reopen it or ask us to reopen.

Thanks

from magento2.