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

Uncaught Error: Class 'DOMDocument' not found in Magento 2.4 CE #29387

Closed
5 tasks
TheRealHunzik opened this issue Aug 5, 2020 · 5 comments
Closed
5 tasks

Uncaught Error: Class 'DOMDocument' not found in Magento 2.4 CE #29387

TheRealHunzik opened this issue Aug 5, 2020 · 5 comments
Assignees
Labels
Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Reported on 2.4.0 Indicates original Magento version for the Issue report.

Comments

@TheRealHunzik
Copy link

Preconditions (*)

1.Magento 2.4 CE
2.Apache 2.4.41 (Ubuntu)
3.PHP 7.4.8 (cli)
4.mysql Ver 8.0.21 for Linux on x86_64 (MySQL Community Server - GPL)
5.Ubuntu 20.04 LTS
6.Installed PHP extensions

[PHP Modules]
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
FFI
fileinfo
filter
ftp
gd
gettext
hash
iconv
intl
json
libxml
mbstring
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
Phar
posix
readline
Reflection
session
shmop
SimpleXML
sockets
sodium
SPL
standard
sysvmsg
sysvsem
sysvshm
tokenizer
xml
xmlreader
xmlwriter
xsl
Zend OPcache
zip
zlib

[Zend Modules]
Zend OPcache

  1. i have tried to enable xml extension using phpenmod -v 7.4 xml

Steps to reproduce (*)

1.Download Latest version of Magento CE
2.Extract and copy to /var/www/html/magento24
3.Grant 777 permission usng command sudo chmod -R 777 magento24
4.Go to browser and submit url 'http://127.0.0.1/magento24/'

Expected result (*)

  1. Magento Installation Setup should Start

Actual result (*)

  1. Gave an error on
  2. enable display error found Fatal error: Uncaught Error: Class 'DOMDocument' not found in /var/www/html/magento24/vendor/magento/framework/Config/Dom.php:449

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

  • Severity: S0 - Affects critical data or functionality and leaves users without a 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 5, 2020

Hi @TheRealHunzik. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

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


⚠️ 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Aug 5, 2020
@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Aug 5, 2020

@TheRealHunzik seems like you don't have installed dom php extension.
You can see that there is dependency declared in composer.json.

"ext-dom": "*",

Also should should have such error in case if you'll run composer install.

In case if you don't have any errors during composer install - please restart apache and/or php-fpm services and try again.

@ihor-sviziev ihor-sviziev self-assigned this Aug 5, 2020
@m2-assistant
Copy link

m2-assistant bot commented Aug 5, 2020

Hi @ihor-sviziev. 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).

    DetailsIf 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 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!

  • 5. Add label Issue: Confirmed once verification is complete.

  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@sdzhepa
Copy link
Contributor

sdzhepa commented Aug 17, 2020

Hello @TheRealHunzik

Did you have a chance to check #29387 (comment) ?
Based on the description it seems some kind of configuration/env issue.

Could you please provide an update?

Also, be aware that Web Install Wizard has been removed from Magento starting from 2.4.0 release.
Now it can be installed only using CLI

@ihor-sviziev
Copy link
Contributor

Hi @TheRealHunzik,
As we didn't get any response for a long time - we'll close this issue due to inactivity.
Feel free to write any comments or re-open this issue if this it still not resolved for you.

@magento-engcom-team magento-engcom-team added the Reported on 2.4.0 Indicates original Magento version for the Issue report. label Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Reported on 2.4.0 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

4 participants