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

Design configuration (2.1.0) does not save #5666

Closed
kurtjmeyoung opened this issue Jul 15, 2016 · 25 comments

Comments

Projects
None yet
@kurtjmeyoung
Copy link

commented Jul 15, 2016

Hello,
thank you for the effort you are making.
i have issue in Content -> Desing -> Configuration in 2.1.0 version.

Steps to reproduce

Browse Content -> Design -> Configuration.
Click Edit Global.
Change any value and then Save Configuration.
Expected result

Save and refresh the page
Actual result

dose not save and show error: Cannot read contents from file "path/to/magento/" Warning!file_get_contents(path/to/magento/): failed to open stream: No such file or directory
web server info:

Magento 2.1.0
XAMPP 3.2.2 (Apache 2.4.18)
Windows 7

and also

Magento 2.1.0
XAMPP 3.2.2 (Apache 2.4.17)
Windows 10

thank you.

@JDavidVR

This comment has been minimized.

Copy link
Contributor

commented Jul 15, 2016

Hi @kurtjmeyoung, you probably have permission problem, it works on linux.
And magento doesn't support officially windows, you can check here: http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements.html

@developer-lindner

This comment has been minimized.

Copy link

commented Jul 15, 2016

@JDavidVR It's not a windows issue nor a permission problem.

@southerncomputer

This comment has been minimized.

Copy link
Contributor

commented Jul 15, 2016

I've definitely checked this out using 2.1.0 under centos 7 /nginx/apache/php-fpm stack and it works quite fine, unless you are using a non magento2 theme that has issues!

@vivek201

This comment has been minimized.

Copy link
Contributor

commented Jul 16, 2016

Yes, this is definitely an issue. The previous Magento 2.0.7 was working perfectly fine.
Has anyone found a solution to this?

@akacemy

This comment has been minimized.

Copy link

commented Jul 16, 2016

Hello,
i had this problem and i already create ticket for that #5288

and did't found solution yet.

@pboisvert

This comment has been minimized.

Copy link

commented Jul 16, 2016

closing as duplicate of #5288

@pboisvert pboisvert closed this Jul 16, 2016

@vivek201

This comment has been minimized.

Copy link
Contributor

commented Jul 17, 2016

@pboisvert
I still think that this is an issue and that it needs to be handled.
So far, I've found that this happens when the default email template is being loaded in the file magento2/app/code/Magento/Email/Model/AbstractTemplate.php in the function loadDefault($templateId) and the $templateId being passed is design_email_header_template.

In my understanding, the $templateFile variable in that function should hold the absolute path of the template file but instead it is coming out empty.

Also, saying that Windows is not supported is definitely not a solution.

Any help is appreciated, Thanks.

@vivek201

This comment has been minimized.

Copy link
Contributor

commented Jul 17, 2016

Hello,
I have found a workaround for this issue. Copy the folder \vendor\magento\module-email\view\frontend\email to \vendor\magento\module-email\view\adminhtml\email\.
After copying the folder, I can now save the configuration. Don't really know why.
It would be really helpful if someone can explain why.
Thanks.

@devDomM

This comment has been minimized.

Copy link

commented Jul 18, 2016

wait? why was this closed when the "already closed duplicated" #5288 mentions "ey please create a new issue!"

anyway we noticed something important:

  • before you make changes to the design configuration you have to choose between "Global", the Websites you created, and also the Store-Views
  • changes done in Global result with the explained error
  • changes done in a created Website can be saved without an error

TL;DR: To prevent the error save your configuration on the Website-Level, not Global

and btw thanks @vivek201 for the workaround! will also try that.

@stamster

This comment has been minimized.

Copy link

commented Jul 18, 2016

You really should not use Windows for development. If you can't afford dedicated Linux box on your own, you can run it inside Windows via VirtualBox or similar non bare-metal hypervisor software. Save yourself some headache.

Magento is a large project where there are plenty of issues already, so you don't need another layer to worry about such as 'video games' OS.

Bottom line: officially Magento does not support M$ Windows, but only Operating systems (Linux x86-64)

@vivek201

This comment has been minimized.

Copy link
Contributor

commented Jul 18, 2016

@devDomM Thanks, that actually works! Should've tried that before doing anything else.
@stamster Yeah, you're definitely right about the headaches. Just finished setting up a VirtualBox environment with Ubuntu. Hope, it works there.
Thanks guys.

@pboisvert

This comment has been minimized.

Copy link

commented Jul 19, 2016

reopening issue as #5288 was requested to have a new ticket opened and i closed this as a duplicate of that ticket. Hence this one should still be active.

@nanda1990

This comment has been minimized.

Copy link

commented Jul 27, 2016

i want to add wordpress blog in magento-2 sub folder but it is showing 404 not found error. I am using nginx web server and also define location bt still not showing. and my nginx confile is nginx.sample.conf file

@stamster

This comment has been minimized.

Copy link

commented Jul 27, 2016

You have't configured nginx then to route url to your wp phy path.
Pay attention to php location blocks as well.

@Joe-Whitehead

This comment has been minimized.

Copy link

commented Feb 23, 2017

Still getting this issue in Magento 2.1.5.
Solution provided by @vivek201 still works but can this fix be pulled in to a Magento release?

@orlangur

This comment has been minimized.

Copy link
Contributor

commented Mar 3, 2017

@Joe-Whitehead, there is no reason to use Windows for development purposes thus it is not supported by Magento as already mentioned multiple times in this thread. Did you try some Docker-based or Ubuntu/CentOS in VirtualBox development environment on your Windows machine?

There is no reason to pull any fix until Windows compatibility is officially declared by Magento.

Most likely good pull requests from community members which introduce Windows compatibility not breaking other environment cases would be accepted. But such compatibility could be broken with any next change without CI enforcement.

@tamount

This comment has been minimized.

Copy link

commented Jun 12, 2017

HELLO
i want try the workaround . "Copy the folder \vendor\magento\module-email\view\frontend\email to \vendor\magento\module-email\view\adminhtml\email." but i don ' thave this folders in my root directory, i have magento 2.1.5, php5.6
In my folder " C:\xampp\htdocs\magento2\vendor\magento " i have: "Compose", "magento-composer-installer" and "zendframwork1",
Can you help me what to do? pleaaaaaz

@IlnitskiyArtem

This comment has been minimized.

Copy link

commented Jun 29, 2017

@kurtjmeyoung, Thanks for the feedback.
Unfortunately, I could not reproduce the issue in 2.1.7 , 2.1-develop, 2.2.0(develop)
May please let me know if this issue relevant for latest release of Magento 2?

@korostii

This comment has been minimized.

Copy link

commented Jun 29, 2017

Hi @IlnitskiyArtem, the fix seems to be present on branch develop only, so the issue should still be present on both 2.1.7 and 2.1-develop

@xAvarice

This comment has been minimized.

Copy link

commented Jul 7, 2017

So now we're saying its Windows fault because Magento can't load a template yet works for everything else? This framework is becoming more concerning every day.

@korostii

This comment has been minimized.

Copy link

commented Jul 10, 2017

Well, they're saying they owe you no support for Windows since the Magento, Inc. didn't ever promise that Magento CE will be working on Windows out of the box (it just so happens that it does, treat as a pleasant coincidence).

It's a convenient excuse to ignore the bugs that cannot be reproduced on a Linux machine (which is, of course, a bit off-putting to say the least, considering that PHP itself is cross-platform).

However, this issue doesn't happen to be one of those.

@orlangur

This comment has been minimized.

Copy link
Contributor

commented Jul 14, 2017

@xAvarice working with any framework it is a good thing to learn system requirements and follow them.

I would not say "Windows fault", this is more like inconsistency with Linux in this aspect. It would be fixed & enforced by core team if it was ever needed. Microsoft introduced Ubuntu bash shell support in Windows 10, probably, at some point Windows will have enough compatibility by itself without any code change from Magento side.

Not sure why there is still no check similar to PHP version which would forbid running Magento under unsupported Windows OS. It would really eliminate a lot of confusion and similar "issue" reports.

@stamster

This comment has been minimized.

Copy link

commented Jul 14, 2017

While officially there is no support for Windows systems (and it shouldn't matter as no one will run that in a production anyways) and honestly today we have loads of options for development - virtual box to start with. So anyone can happily still run it's Windows' but with only difference being running server for those products like Magento inside of VM.
Waiting for M$ to support something from Linux natively feels like a fairy tale to me, and it could take years to have it polished etc.

So on this I agree with @orlangur - simply add check for OS during app startup / installation and eventually at least those kinds of odd OS bugs will be avoided.

@likemusic

This comment has been minimized.

Copy link
Contributor

commented Dec 23, 2017

Windows 7 + nginx 1.12 + php-fpm + Magento v2.2.2 - bug still exists.

Fortunately workaround still work too - #5666 (comment)

@davidbrandastic

This comment has been minimized.

Copy link

commented Mar 7, 2018

Affects 2.2.3 + Windows + Apache as well unless saving at a store view level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.