Closed springimport closed 7 years ago
I'm getting this same exact error and nothing I try fixes it, I'm completely stuck. It just started out of nowhere.
I'm facing the same error, and now I'm completely sucked and unable to do any work in development mode. Any solutions?
Same issue with magento 2.1.7.
If I go into production mode it is fine, but now developer mode only displays the above error.
Was working fine for days, ran setup:upgrade
and then it appeared.
@springimport In actual result I see you use OpenServer Web server (Windows) Magento does not support your operating system. Please confirm that the issue reproduces on some supported system as well. Please see Magento technology stack requirements for more information.
@IlnitskiyArtem, what makes you think there is any relation between the operation system and XML validation in Magento, whatsoever?
apache resart fixes it.
@stuseek, you've just saved me hours of debugging. Thank you!
Duplicate of https://github.com/magento/magento2/issues/8542, mentioned as solved in 2.1.5 and YES it is Windows-specific.
Another possible solution: https://magento.stackexchange.com/a/134473
Please use Magento Stack Exchange for questions, especially regarding unsupported operating systems.
and YES it is Windows-specific.
I still don't see what do you base that assumption on. Could be purely coincidental (unless you know exactly why the error was happening and how it got fixed).
Please use Magento Stack Exchange for questions, especially regarding unsupported operating systems.
I wouldn't go that far. Magento is supposedly open-source. Even if the core team doesn't feel like investing any resources into portability (other than that via that devbox thing done using a docker container), I don't see anything wring if the Community wants to keep the Magento cross-platform and is prepared to put some effort in that.
As such, I would suggest marking such issues as up for grabs
in the future (this issue is a duplicate report of a bug already solved, so it doesn't really matter in this particular case anymore), instead of dismissing them completely.
The question
tag is completely inappropriate here. There aren't any questions (or even question marks, for that matter) in this issue report.
Preconditions
Steps to reproduce
Actual result
The following doesn't help:
But it has solved the problem:
I would like that developers check this place in the code, may be it a bug.