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

1300-talet

Image
Den här artikeln handlar om hundraårsperioden 1300–1399. För decenniet 1300–1309, se 1300-talet (decennium). .mw-parser-output .infobox{border:1px solid #aaa;background-color:#f9f9f9;color:black;margin:.5em 0 .5em 1em;padding:.2em;float:right;clear:right;width:22em;text-align:left;font-size:88%;line-height:1.6em}.mw-parser-output .infobox td,.mw-parser-output .infobox th{vertical-align:top;padding:0 .2em}.mw-parser-output .infobox caption{font-size:larger}.mw-parser-output .infobox.bordered{border-collapse:collapse}.mw-parser-output .infobox.bordered td,.mw-parser-output .infobox.bordered th{border:1px solid #aaa}.mw-parser-output .infobox.bordered .borderless td,.mw-parser-output .infobox.bordered .borderless th{border:0}.mw-parser-output .infobox-showbutton .mw-collapsible-text{color:inherit}.mw-parser-output .infobox.bordered .mergedtoprow td,.mw-parser-output .infobox.bordered .mergedtoprow th{border:0;border-top:1px solid #aaa;border-right:1px solid #aaa}.mw-parser-output ...
Read more

1300-talet

Image
Den här artikeln handlar om hundraårsperioden 1300–1399. För decenniet 1300–1309, se 1300-talet (decennium). .mw-parser-output .infobox{border:1px solid #aaa;background-color:#f9f9f9;color:black;margin:.5em 0 .5em 1em;padding:.2em;float:right;clear:right;width:22em;text-align:left;font-size:88%;line-height:1.6em}.mw-parser-output .infobox td,.mw-parser-output .infobox th{vertical-align:top;padding:0 .2em}.mw-parser-output .infobox caption{font-size:larger}.mw-parser-output .infobox.bordered{border-collapse:collapse}.mw-parser-output .infobox.bordered td,.mw-parser-output .infobox.bordered th{border:1px solid #aaa}.mw-parser-output .infobox.bordered .borderless td,.mw-parser-output .infobox.bordered .borderless th{border:0}.mw-parser-output .infobox-showbutton .mw-collapsible-text{color:inherit}.mw-parser-output .infobox.bordered .mergedtoprow td,.mw-parser-output .infobox.bordered .mergedtoprow th{border:0;border-top:1px solid #aaa;border-right:1px solid #aaa}.mw-parser-output ...
Read more

Display a custom attribute below product name in the front-end Magento 1.9.3.8

Image
0 I need to display a custom attribute bellow the product name and I don't know how can I call this attribute. I am editing the file /app/design/frontend/templatemela/MAG100219_1/template/catalog/product/view.phtml But how can I call this attribute in php? I tried calling a string echo with the name I put in the attribute, but it didn't work. Code is as below: <div class="page-title product-title"> <h1><?php echo $_helper->productAttribute($_product, $_product->getName(), 'name') ?></h1> </div> <div class="codigoinmetro"> <h2><?php echo $_helper->productAttribute($_product, $_product->getName(), 'registroinmetro') ?></h2> </div> php attrib...
Read more