Magento 2.2: Custom Theme Deployment Breaks at 95%












4















Just updated from Magento 2.1.10 to 2.2.2, and keep receiving the following when I deploy static content. Any insights on what the errors signify? 



#0 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(73): MagentoFrameworkViewAssetFile->getSourceFile()

#1 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(61): MagentoFrameworkAppViewAssetPublisher->publishAsset(Object(MagentoFrameworkViewAssetFile))

#2 /app/web/vendor/magento/module-deploy/Service/DeployStaticFile.php(89): MagentoFrameworkAppViewAssetPublisher->publish(Object(MagentoFrameworkViewAssetFile))

#3 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(189): MagentoDeployServiceDeployStaticFile->deployFile('css/style.less', Array)

#4 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(136): MagentoDeployServiceDeployPackage->processFile(Object(MagentoDeployPackagePackageFile), Object(MagentoDeployPackagePackage))

#5 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(107): MagentoDeployServiceDeployPackage->deployEmulated(Object(MagentoDeployPackagePackage), Array, false)

#6 [internal function]: MagentoDeployServiceDeployPackage->MagentoDeployService{closure}()

#7 /app/web/vendor/magento/framework/App/State.php(186): call_user_func_array(Object(Closure), Array)

#8 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(108): MagentoFrameworkAppState->emulateAreaCode('frontend', Object(Closure))

#9 /app/web/vendor/magento/module-deploy/Process/Queue.php(281): MagentoDeployServiceDeployPackage->deploy(Object(MagentoDeployPackagePackage), Array)

#10 /app/web/vendor/magento/module-deploy/Process/Queue.php(200): MagentoDeployProcessQueue->execute(Object(MagentoDeployPackagePackage))

#11 /app/web/vendor/magento/module-deploy/Process/Queue.php(162): MagentoDeployProcessQueue->assertAndExecute('frontend/CustomVendor/i...', Array, Array)

#12 /app/web/vendor/magento/module-deploy/Strategy/QuickDeploy.php(76): MagentoDeployProcessQueue->process()

#13 /app/web/vendor/magento/module-deploy/Service/DeployStaticContent.php(109): MagentoDeployStrategyQuickDeploy->deploy(Array)

#14 /app/web/setup/src/Magento/Setup/Console/Command/DeployStaticContentCommand.php(140): MagentoDeployServiceDeployStaticContent->deploy(Array)

#15 /app/web/vendor/symfony/console/Command/Command.php(242): MagentoSetupConsoleCommandDeployStaticContentCommand->execute(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#16 /app/web/vendor/symfony/console/Application.php(843): SymfonyComponentConsoleCommandCommand->run(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#17 /app/web/vendor/symfony/console/Application.php(193): SymfonyComponentConsoleApplication->doRunCommand(Object(MagentoSetupConsoleCommandDeployStaticContentCommand), Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#18 /app/web/vendor/magento/framework/Console/Cli.php(104): SymfonyComponentConsoleApplication->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#19 /app/web/vendor/symfony/console/Application.php(117): MagentoFrameworkConsoleCli->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#20 /app/web/bin/magento(23): SymfonyComponentConsoleApplication->run()

#21 {main}





  [MagentoFrameworkExceptionFileSystemException]                                                                           

  Cannot read contents from file "/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css" Warning!file_get_con  

  tents(/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css): failed to open stream: No such file or directory


Also, does anyone know if the js-translation.json are among the last to be deployed? They're not generated, so I'm assuming it happens at the end.



Thanks!






magento2.2.2 static-content-deploy







share|improve this question























  • Just figured out that I can get to work if I run: bin/magento setup:static-content:deploy en_US --no-css , so that allows the previously missing js-translation.json file to generate. But I'm still unsure what's wrong otherwise, as in why that style.min.css file is missing or why Magento is expecting it.

    – Brockfast Cowboy
    Jan 10 '18 at 18:35













  • have you tried running this after clearing the var/di folder? we got stuck on a similar problem and that cleaned up the issue for us. It also might be worth clearing the var/view_preprocess folder as well.

    – circlesix
    Jan 13 '18 at 18:34











  • You know, there actually isn't a var/di folder. Clearing var/view_preprocess and then running the deploy without the "no-css" option didn't work, either. Only solution so far is bin/magento setup:static-content:deploy en_US --no-css, which isn't exactly a solution.

    – Brockfast Cowboy
    Jan 16 '18 at 14:08











  • did anyone find a soultion to this yet ?

    – Sarasranglt
    Dec 17 '18 at 11:03
















4















Just updated from Magento 2.1.10 to 2.2.2, and keep receiving the following when I deploy static content. Any insights on what the errors signify? 



#0 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(73): MagentoFrameworkViewAssetFile->getSourceFile()

#1 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(61): MagentoFrameworkAppViewAssetPublisher->publishAsset(Object(MagentoFrameworkViewAssetFile))

#2 /app/web/vendor/magento/module-deploy/Service/DeployStaticFile.php(89): MagentoFrameworkAppViewAssetPublisher->publish(Object(MagentoFrameworkViewAssetFile))

#3 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(189): MagentoDeployServiceDeployStaticFile->deployFile('css/style.less', Array)

#4 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(136): MagentoDeployServiceDeployPackage->processFile(Object(MagentoDeployPackagePackageFile), Object(MagentoDeployPackagePackage))

#5 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(107): MagentoDeployServiceDeployPackage->deployEmulated(Object(MagentoDeployPackagePackage), Array, false)

#6 [internal function]: MagentoDeployServiceDeployPackage->MagentoDeployService{closure}()

#7 /app/web/vendor/magento/framework/App/State.php(186): call_user_func_array(Object(Closure), Array)

#8 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(108): MagentoFrameworkAppState->emulateAreaCode('frontend', Object(Closure))

#9 /app/web/vendor/magento/module-deploy/Process/Queue.php(281): MagentoDeployServiceDeployPackage->deploy(Object(MagentoDeployPackagePackage), Array)

#10 /app/web/vendor/magento/module-deploy/Process/Queue.php(200): MagentoDeployProcessQueue->execute(Object(MagentoDeployPackagePackage))

#11 /app/web/vendor/magento/module-deploy/Process/Queue.php(162): MagentoDeployProcessQueue->assertAndExecute('frontend/CustomVendor/i...', Array, Array)

#12 /app/web/vendor/magento/module-deploy/Strategy/QuickDeploy.php(76): MagentoDeployProcessQueue->process()

#13 /app/web/vendor/magento/module-deploy/Service/DeployStaticContent.php(109): MagentoDeployStrategyQuickDeploy->deploy(Array)

#14 /app/web/setup/src/Magento/Setup/Console/Command/DeployStaticContentCommand.php(140): MagentoDeployServiceDeployStaticContent->deploy(Array)

#15 /app/web/vendor/symfony/console/Command/Command.php(242): MagentoSetupConsoleCommandDeployStaticContentCommand->execute(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#16 /app/web/vendor/symfony/console/Application.php(843): SymfonyComponentConsoleCommandCommand->run(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#17 /app/web/vendor/symfony/console/Application.php(193): SymfonyComponentConsoleApplication->doRunCommand(Object(MagentoSetupConsoleCommandDeployStaticContentCommand), Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#18 /app/web/vendor/magento/framework/Console/Cli.php(104): SymfonyComponentConsoleApplication->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#19 /app/web/vendor/symfony/console/Application.php(117): MagentoFrameworkConsoleCli->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#20 /app/web/bin/magento(23): SymfonyComponentConsoleApplication->run()

#21 {main}





  [MagentoFrameworkExceptionFileSystemException]                                                                           

  Cannot read contents from file "/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css" Warning!file_get_con  

  tents(/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css): failed to open stream: No such file or directory


Also, does anyone know if the js-translation.json are among the last to be deployed? They're not generated, so I'm assuming it happens at the end.



Thanks!






magento2.2.2 static-content-deploy







share|improve this question























  • Just figured out that I can get to work if I run: bin/magento setup:static-content:deploy en_US --no-css , so that allows the previously missing js-translation.json file to generate. But I'm still unsure what's wrong otherwise, as in why that style.min.css file is missing or why Magento is expecting it.

    – Brockfast Cowboy
    Jan 10 '18 at 18:35













  • have you tried running this after clearing the var/di folder? we got stuck on a similar problem and that cleaned up the issue for us. It also might be worth clearing the var/view_preprocess folder as well.

    – circlesix
    Jan 13 '18 at 18:34











  • You know, there actually isn't a var/di folder. Clearing var/view_preprocess and then running the deploy without the "no-css" option didn't work, either. Only solution so far is bin/magento setup:static-content:deploy en_US --no-css, which isn't exactly a solution.

    – Brockfast Cowboy
    Jan 16 '18 at 14:08











  • did anyone find a soultion to this yet ?

    – Sarasranglt
    Dec 17 '18 at 11:03














4












4








4


1






Just updated from Magento 2.1.10 to 2.2.2, and keep receiving the following when I deploy static content. Any insights on what the errors signify? 



#0 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(73): MagentoFrameworkViewAssetFile->getSourceFile()

#1 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(61): MagentoFrameworkAppViewAssetPublisher->publishAsset(Object(MagentoFrameworkViewAssetFile))

#2 /app/web/vendor/magento/module-deploy/Service/DeployStaticFile.php(89): MagentoFrameworkAppViewAssetPublisher->publish(Object(MagentoFrameworkViewAssetFile))

#3 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(189): MagentoDeployServiceDeployStaticFile->deployFile('css/style.less', Array)

#4 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(136): MagentoDeployServiceDeployPackage->processFile(Object(MagentoDeployPackagePackageFile), Object(MagentoDeployPackagePackage))

#5 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(107): MagentoDeployServiceDeployPackage->deployEmulated(Object(MagentoDeployPackagePackage), Array, false)

#6 [internal function]: MagentoDeployServiceDeployPackage->MagentoDeployService{closure}()

#7 /app/web/vendor/magento/framework/App/State.php(186): call_user_func_array(Object(Closure), Array)

#8 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(108): MagentoFrameworkAppState->emulateAreaCode('frontend', Object(Closure))

#9 /app/web/vendor/magento/module-deploy/Process/Queue.php(281): MagentoDeployServiceDeployPackage->deploy(Object(MagentoDeployPackagePackage), Array)

#10 /app/web/vendor/magento/module-deploy/Process/Queue.php(200): MagentoDeployProcessQueue->execute(Object(MagentoDeployPackagePackage))

#11 /app/web/vendor/magento/module-deploy/Process/Queue.php(162): MagentoDeployProcessQueue->assertAndExecute('frontend/CustomVendor/i...', Array, Array)

#12 /app/web/vendor/magento/module-deploy/Strategy/QuickDeploy.php(76): MagentoDeployProcessQueue->process()

#13 /app/web/vendor/magento/module-deploy/Service/DeployStaticContent.php(109): MagentoDeployStrategyQuickDeploy->deploy(Array)

#14 /app/web/setup/src/Magento/Setup/Console/Command/DeployStaticContentCommand.php(140): MagentoDeployServiceDeployStaticContent->deploy(Array)

#15 /app/web/vendor/symfony/console/Command/Command.php(242): MagentoSetupConsoleCommandDeployStaticContentCommand->execute(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#16 /app/web/vendor/symfony/console/Application.php(843): SymfonyComponentConsoleCommandCommand->run(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#17 /app/web/vendor/symfony/console/Application.php(193): SymfonyComponentConsoleApplication->doRunCommand(Object(MagentoSetupConsoleCommandDeployStaticContentCommand), Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#18 /app/web/vendor/magento/framework/Console/Cli.php(104): SymfonyComponentConsoleApplication->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#19 /app/web/vendor/symfony/console/Application.php(117): MagentoFrameworkConsoleCli->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#20 /app/web/bin/magento(23): SymfonyComponentConsoleApplication->run()

#21 {main}





  [MagentoFrameworkExceptionFileSystemException]                                                                           

  Cannot read contents from file "/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css" Warning!file_get_con  

  tents(/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css): failed to open stream: No such file or directory


Also, does anyone know if the js-translation.json are among the last to be deployed? They're not generated, so I'm assuming it happens at the end.



Thanks!






magento2.2.2 static-content-deploy







share|improve this question














Just updated from Magento 2.1.10 to 2.2.2, and keep receiving the following when I deploy static content. Any insights on what the errors signify? 



#0 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(73): MagentoFrameworkViewAssetFile->getSourceFile()

#1 /app/web/vendor/magento/framework/App/View/Asset/Publisher.php(61): MagentoFrameworkAppViewAssetPublisher->publishAsset(Object(MagentoFrameworkViewAssetFile))

#2 /app/web/vendor/magento/module-deploy/Service/DeployStaticFile.php(89): MagentoFrameworkAppViewAssetPublisher->publish(Object(MagentoFrameworkViewAssetFile))

#3 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(189): MagentoDeployServiceDeployStaticFile->deployFile('css/style.less', Array)

#4 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(136): MagentoDeployServiceDeployPackage->processFile(Object(MagentoDeployPackagePackageFile), Object(MagentoDeployPackagePackage))

#5 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(107): MagentoDeployServiceDeployPackage->deployEmulated(Object(MagentoDeployPackagePackage), Array, false)

#6 [internal function]: MagentoDeployServiceDeployPackage->MagentoDeployService{closure}()

#7 /app/web/vendor/magento/framework/App/State.php(186): call_user_func_array(Object(Closure), Array)

#8 /app/web/vendor/magento/module-deploy/Service/DeployPackage.php(108): MagentoFrameworkAppState->emulateAreaCode('frontend', Object(Closure))

#9 /app/web/vendor/magento/module-deploy/Process/Queue.php(281): MagentoDeployServiceDeployPackage->deploy(Object(MagentoDeployPackagePackage), Array)

#10 /app/web/vendor/magento/module-deploy/Process/Queue.php(200): MagentoDeployProcessQueue->execute(Object(MagentoDeployPackagePackage))

#11 /app/web/vendor/magento/module-deploy/Process/Queue.php(162): MagentoDeployProcessQueue->assertAndExecute('frontend/CustomVendor/i...', Array, Array)

#12 /app/web/vendor/magento/module-deploy/Strategy/QuickDeploy.php(76): MagentoDeployProcessQueue->process()

#13 /app/web/vendor/magento/module-deploy/Service/DeployStaticContent.php(109): MagentoDeployStrategyQuickDeploy->deploy(Array)

#14 /app/web/setup/src/Magento/Setup/Console/Command/DeployStaticContentCommand.php(140): MagentoDeployServiceDeployStaticContent->deploy(Array)

#15 /app/web/vendor/symfony/console/Command/Command.php(242): MagentoSetupConsoleCommandDeployStaticContentCommand->execute(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#16 /app/web/vendor/symfony/console/Application.php(843): SymfonyComponentConsoleCommandCommand->run(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#17 /app/web/vendor/symfony/console/Application.php(193): SymfonyComponentConsoleApplication->doRunCommand(Object(MagentoSetupConsoleCommandDeployStaticContentCommand), Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#18 /app/web/vendor/magento/framework/Console/Cli.php(104): SymfonyComponentConsoleApplication->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#19 /app/web/vendor/symfony/console/Application.php(117): MagentoFrameworkConsoleCli->doRun(Object(SymfonyComponentConsoleInputArgvInput), Object(SymfonyComponentConsoleOutputConsoleOutput))

#20 /app/web/bin/magento(23): SymfonyComponentConsoleApplication->run()

#21 {main}





  [MagentoFrameworkExceptionFileSystemException]                                                                           

  Cannot read contents from file "/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css" Warning!file_get_con  

  tents(/app/web/pub/static/frontend/CustomVendor/custom/en_US/css/style.min.css): failed to open stream: No such file or directory


Also, does anyone know if the js-translation.json are among the last to be deployed? They're not generated, so I'm assuming it happens at the end.



Thanks!






magento2.2.2 static-content-deploy




magento2.2.2 static-content-deploy






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 10 '18 at 16:05









Brockfast CowboyBrockfast Cowboy

17415




17415













  • Just figured out that I can get to work if I run: bin/magento setup:static-content:deploy en_US --no-css , so that allows the previously missing js-translation.json file to generate. But I'm still unsure what's wrong otherwise, as in why that style.min.css file is missing or why Magento is expecting it.

    – Brockfast Cowboy
    Jan 10 '18 at 18:35













  • have you tried running this after clearing the var/di folder? we got stuck on a similar problem and that cleaned up the issue for us. It also might be worth clearing the var/view_preprocess folder as well.

    – circlesix
    Jan 13 '18 at 18:34











  • You know, there actually isn't a var/di folder. Clearing var/view_preprocess and then running the deploy without the "no-css" option didn't work, either. Only solution so far is bin/magento setup:static-content:deploy en_US --no-css, which isn't exactly a solution.

    – Brockfast Cowboy
    Jan 16 '18 at 14:08











  • did anyone find a soultion to this yet ?

    – Sarasranglt
    Dec 17 '18 at 11:03



















  • Just figured out that I can get to work if I run: bin/magento setup:static-content:deploy en_US --no-css , so that allows the previously missing js-translation.json file to generate. But I'm still unsure what's wrong otherwise, as in why that style.min.css file is missing or why Magento is expecting it.

    – Brockfast Cowboy
    Jan 10 '18 at 18:35













  • have you tried running this after clearing the var/di folder? we got stuck on a similar problem and that cleaned up the issue for us. It also might be worth clearing the var/view_preprocess folder as well.

    – circlesix
    Jan 13 '18 at 18:34











  • You know, there actually isn't a var/di folder. Clearing var/view_preprocess and then running the deploy without the "no-css" option didn't work, either. Only solution so far is bin/magento setup:static-content:deploy en_US --no-css, which isn't exactly a solution.

    – Brockfast Cowboy
    Jan 16 '18 at 14:08











  • did anyone find a soultion to this yet ?

    – Sarasranglt
    Dec 17 '18 at 11:03

















Just figured out that I can get to work if I run: bin/magento setup:static-content:deploy en_US --no-css , so that allows the previously missing js-translation.json file to generate. But I'm still unsure what's wrong otherwise, as in why that style.min.css file is missing or why Magento is expecting it.

– Brockfast Cowboy
Jan 10 '18 at 18:35







Just figured out that I can get to work if I run: bin/magento setup:static-content:deploy en_US --no-css , so that allows the previously missing js-translation.json file to generate. But I'm still unsure what's wrong otherwise, as in why that style.min.css file is missing or why Magento is expecting it.

– Brockfast Cowboy
Jan 10 '18 at 18:35















have you tried running this after clearing the var/di folder? we got stuck on a similar problem and that cleaned up the issue for us. It also might be worth clearing the var/view_preprocess folder as well.

– circlesix
Jan 13 '18 at 18:34





have you tried running this after clearing the var/di folder? we got stuck on a similar problem and that cleaned up the issue for us. It also might be worth clearing the var/view_preprocess folder as well.

– circlesix
Jan 13 '18 at 18:34













You know, there actually isn't a var/di folder. Clearing var/view_preprocess and then running the deploy without the "no-css" option didn't work, either. Only solution so far is bin/magento setup:static-content:deploy en_US --no-css, which isn't exactly a solution.

– Brockfast Cowboy
Jan 16 '18 at 14:08





You know, there actually isn't a var/di folder. Clearing var/view_preprocess and then running the deploy without the "no-css" option didn't work, either. Only solution so far is bin/magento setup:static-content:deploy en_US --no-css, which isn't exactly a solution.

– Brockfast Cowboy
Jan 16 '18 at 14:08













did anyone find a soultion to this yet ?

– Sarasranglt
Dec 17 '18 at 11:03





did anyone find a soultion to this yet ?

– Sarasranglt
Dec 17 '18 at 11:03










1 Answer
1






active

oldest

votes


















0














Since I posted this, I noticed that deleting the empty styles.less file in my custom theme's css folder sometimes fixes issues similar to this one.



I can't recall if it was the fix for this particular issue, but if you have an empty styles.css file then it would be worth a shot.






share|improve this answer



















  • 1





    Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

    – Tofandel
    Jul 18 '18 at 14:49













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f208926%2fmagento-2-2-custom-theme-deployment-breaks-at-95%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Since I posted this, I noticed that deleting the empty styles.less file in my custom theme's css folder sometimes fixes issues similar to this one.



I can't recall if it was the fix for this particular issue, but if you have an empty styles.css file then it would be worth a shot.






share|improve this answer



















  • 1





    Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

    – Tofandel
    Jul 18 '18 at 14:49


















0














Since I posted this, I noticed that deleting the empty styles.less file in my custom theme's css folder sometimes fixes issues similar to this one.



I can't recall if it was the fix for this particular issue, but if you have an empty styles.css file then it would be worth a shot.






share|improve this answer



















  • 1





    Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

    – Tofandel
    Jul 18 '18 at 14:49
















0












0








0







Since I posted this, I noticed that deleting the empty styles.less file in my custom theme's css folder sometimes fixes issues similar to this one.



I can't recall if it was the fix for this particular issue, but if you have an empty styles.css file then it would be worth a shot.






share|improve this answer













Since I posted this, I noticed that deleting the empty styles.less file in my custom theme's css folder sometimes fixes issues similar to this one.



I can't recall if it was the fix for this particular issue, but if you have an empty styles.css file then it would be worth a shot.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 18 '18 at 14:27









Brockfast CowboyBrockfast Cowboy

17415




17415








  • 1





    Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

    – Tofandel
    Jul 18 '18 at 14:49
















  • 1





    Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

    – Tofandel
    Jul 18 '18 at 14:49










1




1





Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

– Tofandel
Jul 18 '18 at 14:49







Sometimes the error on why the compilation failed disappears because of that 'Cannot read contents from file' error. If you relaunch the deploy static content command, you will see the error message appear (usually it's due to a variable that is not defined in less or another less error so the style.less compilation failed and that's why it couldn't find the style.min.css)

– Tofandel
Jul 18 '18 at 14:49




















draft saved

draft discarded




















































Thanks for contributing an answer to Magento Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f208926%2fmagento-2-2-custom-theme-deployment-breaks-at-95%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

An IMO inspired problem

Image
14 4 This problem from IMO 1988 is said to be one of the most elegant ones in functional equations. Problem : The function $f$ is defined on the set of all positive integers as follows: begin{align} f(1) = 1, f(3) &= 3, f(2n) = f(n), \ f(4n+1) &= 2f(2n+1) - f(n), \ f(4n+3) &= 3 f(2n+1) - 2f(n) end{align} Find the number of $n$ with $f(n) = n, 1 leq n leq 1988$. The main idea towards the solution is realizing that these conditions stand for the fact that $f(n)$ just reverses the digits in the binary representation of the number $n$. So, essentially the solution is finding the number of binary pallindromes $leq 1988_{10}$. My question is the following : How to reformulate the problem so that $f(n)$ reverses the digits of $n$ in its ternary representation. Or even better, can we reformulate it for a
Read more

Management

Image
Management From Wikipedia, the free encyclopedia Jump to navigation Jump to search "Manager" redirects here. For other uses, see Management (disambiguation) and Manager (disambiguation). An organization chart for the United States Coast Guard shows the hierarchy of managerial roles in that organization. Business administration Management of a business Accounting Management accounting Financial accounting Financial audit Business entities Cooperative Corporation Limited liability company Partnership Sole proprietorship State-owned enterprise Corporate governance Annual general meeting Board of directors Supervisory board Advisory board Audit committee Corporate law Commercial law Constitutional documents Contract Corporate crime Corporate liability Insolvency law International trade law Mergers and acquisitions Economics Commodity Pu
Read more

Has there ever been an instance of an active nuclear power plant within or near a war zone?

Image
36 3 The question Has there ever been a military combat going on around an active (running or in outage but not decommissioned) commercial nuclear power plant? Or dangerously near it? If yes, how did the plant and its personnel fare in such situation? Why I ask Let's assume for the scope of this question modern commercial nuclear power plants (CANDU, PWR, BWR of generation II plus all of gen III and newer) are usually reasonably safe to operate given that the engineering has been done right and there is a whole cohort of very well trained personnel on-site at all times, well rested and with considerable resources on their hands. Things hard to get with an armed conflict like the recent Syrian war raging around. I can't seem to find any reference or a comprehensive article about this, hence this question.
Read more