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

EE: File resolving is broken #2485

Closed
vzubovich opened this issue Nov 23, 2015 · 8 comments
Closed

EE: File resolving is broken #2485

vzubovich opened this issue Nov 23, 2015 · 8 comments

Comments

@vzubovich
Copy link
Contributor

I got following error when I was trying to open Content -> Pages:
Cannot read contents from file "/var/www/magento2ee/magento2ce/var/www/magento2ee/magento2ee/app/code/Magento/VersionsCms/view/adminhtml/ui_component/cms_page_listing.xml" Warning!file_get_contents(/var/www/magento2ee/magento2ce/var/www/magento2ee/magento2ee/app/code/Magento/VersionsCms/view/adminhtml/ui_component/cms_page_listing.xml): failed to open stream: No such file or directory

@mazhalai
Copy link
Contributor

@vzubovich Have you set file and folder permissions as recommended here?

@vzubovich
Copy link
Contributor Author

@mazhalai :)
pls take a notice that requested file path is basically wrong - it has splitted path to CE and EE code pools
/var/www/magento2ee/magento2ce + /var/www/magento2ee/

@mazhalai
Copy link
Contributor

@vzubovich please open an issue via the support portal.

@vzubovich
Copy link
Contributor Author

@mazhalai What I have to do?

@mazhalai
Copy link
Contributor

@vzubovich if you have EE, you must have an account on the partner portal. Please login and create a support ticket.

@alankent
Copy link

The support portal has more dedicated staff etc.

But in general, please remember that EE is a set of additional packages you add to your project. There are no code pools in M2. The path you reported looks strange - like there are separate magento2ce and magento2ee directories. I am not sure where these came from. The overall directory structure for CE and EE are the same - if you use the EE product metapackage instead of the CE product metapackage, you end up with more packages in the 'vendor' directory. But there is no different subdirectory. The Support org can help you get this path problem sorted out - it sounds like confusion around how to get the directory tree right, rather than a bug (?).

@mazhalai
Copy link
Contributor

Closing, since this will be handled via partner portal.

@vzubovich
Copy link
Contributor Author

@mazhalai I didn't create any issue on other portals. You may handle this bug as you wish! :)

magento-team pushed a commit that referenced this issue Jun 27, 2018
[TSG] Backporting for 2.1 (pr53) (2.1.14)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants