update to 2.1.1 can not deploy content files

[knidie]

update to 2.1.1 can not deploy static content because missing deployed_version.txt,

[UnexpectedValueException]
Unable to retrieve deployment version of static files from the file system.

[UnexpectedValueException]
Unable to retrieve deployment version of static files from the file system.

[Magento\Framework\Exception\FileSystemException]
Cannot read contents from file "/var/www/html/magento2/pub/static/deployed_version.txt" Warning!file_get_contents(/var/www/html
/magento2/pub/static/deployed_version.txt): failed to open stream: No such file or directory

[ihor-sviziev]

I also had this issue.
@knidie as temporary solution you could just create empty file in following path: /var/www/html/magento2/pub/static/deployed_version.txt

[knidie]

thanks, it works great!!

[hostep]

Indeed, I noticed this too: magento/devdocs#419 (comment)

Since you can resolve it by creating an empty file, this feels like a regression bug which crept into the 2.1.1 release. Maybe you should reopen the bug and let the Magento devs comment on this if this was an intentional change or not...

[bery]

I do not think that creating a blank file is a solution - more like an ugly workaround for incorrect functional logic. Would it be possible to get rid of this messages and change the behavior to

• check if the file exists, if yes read the version and see what needs to be done
• if the file does not exist, continue with the deploy (e.g. clean, fresh deploy)

[knidie]

It worked for me, this file must be there, if not system stops to deploy files , as temporary solution it's just fine.

weikai chen

在 2016年9月12日，下午2:58，bery notifications@github.com 写道：

I do not think that creating a blank file is a solution - more like an ugly workaround for incorrect functional logic. Would it be possible to get rid of this messages and change the behavior to

check if the file exists, if yes read the version and see what needs to be done
if the file does not exist, continue with the deploy (e.g. clean, fresh deploy)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

[hostep]

@knidie: I think it's best if you re-open this ticket, since it's new and unexpected behavior introduced in Magento 2.1.1
I'm pretty sure the change in behavior was also unintentional so we can probably call it a new bug.
Even though there is a temporary workaround, that's not really enough to call this bug "fixed".
Do you agree?

Let's include some Magento support people in here, maybe they can verify this with the developers if this is a new bug or if this was actually intentional (which I don't really believe).
/cc @veloraven, @piotrekkaminski, @pboisvert, @mazhalai, ...

Thanks!

[eug123]

Hi @knidie,
This issue was fixed in the scope of the MAGETWO-56915 and delivered to the develop branch.
Please check if the issue is still reproducible for you on the develop branch.
Thank you