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

php bin/magento setup:static-content:deploy ( gives an errors ) #1120

Closed
tukker01 opened this issue Oct 5, 2018 · 2 comments
Closed

php bin/magento setup:static-content:deploy ( gives an errors ) #1120

tukker01 opened this issue Oct 5, 2018 · 2 comments

Comments

@tukker01
Copy link

tukker01 commented Oct 5, 2018

Preconditions
Magento Version : 2.2.6

ElasticSuite Version : ElasticSuite 2.6.x

Environment : Ubuntu 16.04.3 LTS

php bin/magento setup:static-content:deploy gives the understage result

Compilation from source: /var/www/html/vendor/magento/theme-frontend-blank/web/css/styles-m.less
variable @autocomplete-item__border is undefined in file /var/www/html/var/view_preprocessed/pub/static/frontend/Solwin/shoptica/en_US/Smile_ElasticsuiteCore/css/source/_module.less in _module.less on line 32, column 38
30| border-bottom: 0;
31| }
32| .lib-css(border-top, @autocomplete-item__border);
33| cursor: default;
34| margin: 0;
35| padding: @indent__xs @indent__xl @indent__xs @indent__s;

[Magento\Framework\Exception\FileSystemException]
Cannot read contents from file "/var/www/html/pub/static/frontend/Solwin/shoptica/en_US/css/styles-m.css" Warning!file_get_contents(/var/www/html/pub/stati
c/frontend/Solwin/shoptica/en_US/css/styles-m.css): failed to open stream: No such file or directory

this has to do with our template, the developer of the template indicates that it is a problem ElasticSuite problem.

This is his anwser:
(The issue is in your custom module Smile_ElasticsuiteCore which you have installed from the GIT.

This is not Shoptica theme related issue.

I have found the line in which this issue occurs.

.lib-css(border-top, @autocomplete-item__border);

You should contact to the Smile support person. Because they have developed it and they know it better.
)

@sezio
Copy link

sezio commented Oct 10, 2018

Hello,

I was having the same issue and found the workaround here #91 (comment)

@romainruaud
Copy link
Collaborator

Yes, the workaround described by @sezio should do the trick.

Just to end the discussion : The @autocomplete-* variables are defined into the Luma theme, but also in the Blank theme.

So your theme should still have these custom variables since they come from the blank theme.

Anyone doing a theme from scratch and not inheriting the blank theme, or removing custom variable from it, is doing wrong.

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