cancel
Showing results for 
Search instead for 
Did you mean: 

Static content deploy error after upgrading to 2.3.2

SOLVED
Highlighted

Static content deploy error after upgrading to 2.3.2

Hi!

 

After updating from 2.3.1 to 2.3.2 

running

setup:static-content:deploy

returns an error

Compilation from source: /Users/miguel/Projects/_magento/vendor/magento/theme-frontend-blank/web/css/styles-m.less

variable @color-lighter-grayish is undefined in file /Users/miguel/Projects/_magento/var/view_preprocessed/pub/static/frontend/Magento/luma/ru_RU/Magento_Checkout/css/source/module/checkout/fields/_file-uploader.less in _file-uploader.less on line 18, column 39

16|

17|

18| @file-uploader-preview__border-color: @color-lighter-grayish;

 

I've located this file in 

vendor/magento/theme-frontend-luma/Magento_Checkout/web/css/source/module/checkout/fields/_file-uploader.less 

and hardcoded 

@file-uploader-preview__border-color: #ddd; 

trying to solve the issue, but without any luck. Did anyone have similar issue after update?

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Static content deploy error after upgrading to 2.3.2

Hi @Miguel_

Try once after adding undefined variable in your theme's _variable.less fine and declare there.

I managed to fix the problem, so static content is deployed. I had to add these to _variables.less (from luma theme)

@color-lighter-grayish: #cacaca;
@color-brownie: #514943;
@color-brownie-almost: #524d49;
@color-very-dark-gray: #666;
@color-brownie-light: #676056;
@color-very-dark-gray1: #777;
@color-brownie-vanilla: #736963;
@color-gray83: #d4d4d4;
@color-darker-gray: #8a837f;
@color-blue-dodger: #008bdb;

@icon-delete__content: '\e630';
@ICONS-admin__font-name: 'Admin Icons';
@icon-video__content: '\e641';
@icon-document__content: '\e649';
@icon-camera__content: '\e63c';
@icon-plus__content: '\e61d';


I hope it will help you!
----
Problem solved? Click Accept as Solution!

View solution in original post

6 REPLIES 6
Highlighted

Re: Static content deploy error after upgrading to 2.3.2

Hi @Miguel_

Try once after adding undefined variable in your theme's _variable.less fine and declare there.

I managed to fix the problem, so static content is deployed. I had to add these to _variables.less (from luma theme)

@color-lighter-grayish: #cacaca;
@color-brownie: #514943;
@color-brownie-almost: #524d49;
@color-very-dark-gray: #666;
@color-brownie-light: #676056;
@color-very-dark-gray1: #777;
@color-brownie-vanilla: #736963;
@color-gray83: #d4d4d4;
@color-darker-gray: #8a837f;
@color-blue-dodger: #008bdb;

@icon-delete__content: '\e630';
@ICONS-admin__font-name: 'Admin Icons';
@icon-video__content: '\e641';
@icon-document__content: '\e649';
@icon-camera__content: '\e63c';
@icon-plus__content: '\e61d';


I hope it will help you!
----
Problem solved? Click Accept as Solution!

View solution in original post

Highlighted

Re: Static content deploy error after upgrading to 2.3.2

Thanks, this solved my issue

Highlighted

Re: Static content deploy error after upgrading to 2.3.2

Glad to help you 😊
----
Problem solved? Click Accept as Solution!
Highlighted

Re: Static content deploy error after upgrading to 2.3.2

I had a similar problem, my mistake was to include only composer.json and composer.lock files into the version upgrade while the upgrade itself includes also lib files with less variables. My solution to the problem was to remove everything in vendor directory and run composer install again.
Highlighted

Re: Static content deploy error after upgrading to 2.3.2

rm -rf vendor/

 

then 

 

composer install

 

Fixed reported issue including missing lines from di.xml

Highlighted

Re: Static content deploy error after upgrading to 2.3.2

First remove vendor folder and running 

composer install

I suggest change your web folder and place files and folders 1 by 1