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

fatal error when trying to install sample data #132

Closed
GerardKetuma opened this issue Mar 26, 2017 · 3 comments
Closed

fatal error when trying to install sample data #132

GerardKetuma opened this issue Mar 26, 2017 · 3 comments

Comments

@GerardKetuma
Copy link

GerardKetuma commented Mar 26, 2017

Setting the config option install_sample_data to 1 gives a fatal error in CE after I run m-switch-to-ce -f. Then I reran install script init_project.sh -fc but still get the same error.

Fatal error: Uncaught Magento\Framework\Exception\LocalizedException: Invalid Document Element 'type', attribute 'name': [facet 'pattern'] The value '\Magento\Framework\Mail\TransportInterface' is not accepted by the pattern '([a-zA-Z_�-ÿ][a-zA-Z0-9_�-ÿ]*)(\\[a-zA-Z_�-ÿ][a-zA-Z0-9_�-ÿ]*)*'. Line: 9 Element 'type', attribute 'name': '\Magento\Framework\Mail\TransportInterface' is not a valid value of the atomic type 'phpClassName'. Line: 9 Element 'type', attribute 'name': Warning: No precomputed value available, the value was either invalid or something strange happend. Line: 9 in /Volumes/Vagrant/magento_projects/vagrant-magento/magento2ce/lib/internal/Magento/Framework/Config/Reader/Filesystem.php on line 160

@paliarush
Copy link
Owner

It is possible that you are using incompatible versions of sample data and Magento (branch names should be the same).

This error is caused by one of the latest accepted PRs to the Magento dev branch magento/magento2#8743 and is not related to current vagrant box.
Please report the issue there.

@GerardKetuma
Copy link
Author

@paliarush Yes I finally resolved the issue by specifying the release (::2.1) and also same thing for the sample data in the config.yml file. Running it without specifying a release gets a dev branch of Magento CE and there wasn't any corresponding sample data.
Maybe an improvement will be to set a release for both Magento CE and sample data as a default which will help resolve this issue for others.

@paliarush
Copy link
Owner

@GerardKetuma Could you please provide the git section of the config which was causing the problem for you?
All branches should contain code related to the same Magento version, e.g. develop/2.1/2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants