3

I have installed latest magento version 2.1.5 and configured it.

It works fine but once we run the 

php bin/magento setup:static-content:deploy

Command, it doesn't create the version folder as expected.

I can see by viewing source that the content is being called via particular version like below:

http://127.0.0.1/magento215/pub/static/**version1489125606**/frontend/Magento/luma/en_US/css/styles-l.css

But in pub static the folder "version1489125606" is missing.

All the files are reside directly in pub/static folder. Is there any setting to get it update?

Improve this question
2

2 Answers 2

Reset to default
4

Hello Himmat log in admin

then go to store->configuartion->Advanced->Developer->Static File Setting

and Sign Static Files set values to no

Improve this answer
4
  • Sign Static Files set values to 'Yes` to create versionXXXX folder.
    – gelanivishal
    Commented Mar 10, 2017 at 6:17
  • Yes, it is not creating the versionxxxxxxx folder in 2.1.5, seems magento default issue. Anyways, thanks guys for your time..
    – Himmat Paliwal
    Commented Mar 10, 2017 at 6:29
  • You are always welcome @HimmatPaliwal :)
    – Murtuza Zabuawala ♦
    Commented Mar 10, 2017 at 6:33
  • 1
    It is not issue. This folder should not be created. Magento use rewrites to skip it.
    – KAndy
    Commented Mar 10, 2017 at 17:46
1

This folder should not be created. It is not the issue. Magento use rewrites to skip it. see https://github.com/magento/magento2/blob/2.1.5/nginx.conf.sample#L95 for nginx or https://github.com/magento/magento2/blob/2.1.5/pub/static/.htaccess#L16 for apache

Improve this answer
1
  • ok, but it is not getting skipped after static-content deploy.
    – Himmat Paliwal
    Commented Mar 11, 2017 at 5:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.