Frontend styling has disappeared, and I can't get it back Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Magento2 - pub static css not foundMagento 2: Overiding Admin Theme not working in Production Mode with CDN [SOLVED]Is there a fast way to flush cache and empty static folders using putty commands?Css file not loading after static content flush in Magento 2.1.82.2 Faster way to regenerate css in developer modemagento2 - how do I show css updates in production mode?error magento 2: FilesystemIterator::__construct(/var/www/html/pub/static/_requirejs/frontend/Magento): failed to open dir: Permission deniedMagento2 css images deploy static files languageMagento 2.2.4 Backend menu issue not working except catalog>Category page and shows 2 errorsMagento 2 Error: Product disappeared on frontend, one store view only

My admission is revoked after accepting the admission offer

How long can a nation maintain a technological edge over the rest of the world?

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

Why I cannot instantiate a class whose constructor is private in a friend class?

Determinant of a matrix with 2 equal rows

Is a self contained air-bullet cartridge feasible?

Is Bran literally the world's memory?

Married in secret, can marital status in passport be changed at a later date?

Does Prince Arnaud cause someone holding the Princess to lose?

Will I be more secure with my own router behind my ISP's router?

Has a Nobel Peace laureate ever been accused of war crimes?

How would it unbalance gameplay to rule that Weapon Master allows for picking a fighting style?

Why doesn't the university give past final exams' answers?

What happened to Viserion in Season 7?

What to do with someone that cheated their way though university and a PhD program?

Getting AggregateResult variables from Execute Anonymous Window

Is it appropriate to mention a relatable company blog post when you're asked about the company?

Was there ever a LEGO store in Miami International Airport?

Was Objective-C really a hindrance to Apple software development?

In search of the origins of term censor, I hit a dead end stuck with the greek term, to censor, λογοκρίνω

What is the evidence that custom checks in Northern Ireland are going to result in violence?

RIP Packet Format

Is it OK if I do not take the receipt in Germany?

Suing a Police Officer Instead of the Police Department



Frontend styling has disappeared, and I can't get it back



Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Magento2 - pub static css not foundMagento 2: Overiding Admin Theme not working in Production Mode with CDN [SOLVED]Is there a fast way to flush cache and empty static folders using putty commands?Css file not loading after static content flush in Magento 2.1.82.2 Faster way to regenerate css in developer modemagento2 - how do I show css updates in production mode?error magento 2: FilesystemIterator::__construct(/var/www/html/pub/static/_requirejs/frontend/Magento): failed to open dir: Permission deniedMagento2 css images deploy static files languageMagento 2.2.4 Backend menu issue not working except catalog>Category page and shows 2 errorsMagento 2 Error: Product disappeared on frontend, one store view only



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















Disclaimer: I'm new to Magento 2 development as of Nov 2018, and new to development generally as of mid-2017. So I'm new to asking development-help questions too. Most of the time I can figure it out on my own. Please forgive me for anything I do that is something I should know not to do.



My problem:
All styling is gone from my frontend (admin is fine).



When the problem started:
When I was trying to add a custom font via an '_extend.less' file. (Creating this file and using it to make changes was the method that was being used in a tutorial I was following to make custom styling changes.)



(I have Magento set to Developer Mode.)



I have set everything back to the way it was before trying to add the custom font (as best I can tell), but the problem still remains. Around the time I was trying to add the custom font, I remember using the command cache:disable, and maybe this messed something up? I've since used cache:enable, but the CLI responds with There is nothing to change in cache status.



I have searched online over the course of 3 days for a total of around 10 hours for a solution. Just so you know I've really tried to figure this out on my own, the following are some things I have tried many (many!) times, and in many variations as to their order and combination (I'm pretty sure new developers do this a lot!):



  • indexer:reindex

  • cache:clean

  • setup:upgrade

  • setup:static-content:deploy -f


  • deploy:mode:set production



    (The idea here was apparently setting it to Production Mode would clear things in a certain way, and then I was supposed to set it back to Developer Mode, and this would fix the problem. But I get an error part way through setting it to Production Mode when it tries to deploy static content, and it shows a message in bright red: Command returned non-zero exit code. Plus above that there's a line that reads: Something went wrong while deploying static content. See the error log for details. Is the error file it's talking about in 'var > log'? Because all the files in there have a 'Date modified' showing 8 days ago, which is way before this problem started. What log file is this referring to?)



  • using the 'Flush Static Files Cache' button (In Admin: System > Cache Management)


  • using the 'Flush JavaScript/CSS Cache' button (In Admin: System > Cache Management)

  • using the bright orange 'Flush Magento Cache' button (In Admin: System > Cache Management)

  • setting directory and file permissions (pretty much to 777 every time)

  • rm -rf view_preprocessed/*

  • rm -rf static/*

  • rm -rf var/cache,di,generation,page_cache,view_preprocessed

  • and I couldn't begin to tell you how many times I've hit 'Shift+F5' to refresh the storefront page

'No styling' seems like such a simple issue, but I can't figure this one out. Any help would be greatly appreciated!



I'm on Apache, all served from Google Cloud Platform (static IP), Bitnami stack.



Edit: screenshots added



browser view - no styling issue



console view - no styling issue










share|improve this question
























  • Hi, please attach a screenshot of the front end with console logs. Are you on Apache or Nginx?

    – B G Kavinga
    Dec 2 '18 at 3:07











  • Kudos for a well written and well researched question...

    – Haim
    Dec 2 '18 at 5:48

















1















Disclaimer: I'm new to Magento 2 development as of Nov 2018, and new to development generally as of mid-2017. So I'm new to asking development-help questions too. Most of the time I can figure it out on my own. Please forgive me for anything I do that is something I should know not to do.



My problem:
All styling is gone from my frontend (admin is fine).



When the problem started:
When I was trying to add a custom font via an '_extend.less' file. (Creating this file and using it to make changes was the method that was being used in a tutorial I was following to make custom styling changes.)



(I have Magento set to Developer Mode.)



I have set everything back to the way it was before trying to add the custom font (as best I can tell), but the problem still remains. Around the time I was trying to add the custom font, I remember using the command cache:disable, and maybe this messed something up? I've since used cache:enable, but the CLI responds with There is nothing to change in cache status.



I have searched online over the course of 3 days for a total of around 10 hours for a solution. Just so you know I've really tried to figure this out on my own, the following are some things I have tried many (many!) times, and in many variations as to their order and combination (I'm pretty sure new developers do this a lot!):



  • indexer:reindex

  • cache:clean

  • setup:upgrade

  • setup:static-content:deploy -f


  • deploy:mode:set production



    (The idea here was apparently setting it to Production Mode would clear things in a certain way, and then I was supposed to set it back to Developer Mode, and this would fix the problem. But I get an error part way through setting it to Production Mode when it tries to deploy static content, and it shows a message in bright red: Command returned non-zero exit code. Plus above that there's a line that reads: Something went wrong while deploying static content. See the error log for details. Is the error file it's talking about in 'var > log'? Because all the files in there have a 'Date modified' showing 8 days ago, which is way before this problem started. What log file is this referring to?)



  • using the 'Flush Static Files Cache' button (In Admin: System > Cache Management)


  • using the 'Flush JavaScript/CSS Cache' button (In Admin: System > Cache Management)

  • using the bright orange 'Flush Magento Cache' button (In Admin: System > Cache Management)

  • setting directory and file permissions (pretty much to 777 every time)

  • rm -rf view_preprocessed/*

  • rm -rf static/*

  • rm -rf var/cache,di,generation,page_cache,view_preprocessed

  • and I couldn't begin to tell you how many times I've hit 'Shift+F5' to refresh the storefront page

'No styling' seems like such a simple issue, but I can't figure this one out. Any help would be greatly appreciated!



I'm on Apache, all served from Google Cloud Platform (static IP), Bitnami stack.



Edit: screenshots added



browser view - no styling issue



console view - no styling issue










share|improve this question
























  • Hi, please attach a screenshot of the front end with console logs. Are you on Apache or Nginx?

    – B G Kavinga
    Dec 2 '18 at 3:07











  • Kudos for a well written and well researched question...

    – Haim
    Dec 2 '18 at 5:48













1












1








1








Disclaimer: I'm new to Magento 2 development as of Nov 2018, and new to development generally as of mid-2017. So I'm new to asking development-help questions too. Most of the time I can figure it out on my own. Please forgive me for anything I do that is something I should know not to do.



My problem:
All styling is gone from my frontend (admin is fine).



When the problem started:
When I was trying to add a custom font via an '_extend.less' file. (Creating this file and using it to make changes was the method that was being used in a tutorial I was following to make custom styling changes.)



(I have Magento set to Developer Mode.)



I have set everything back to the way it was before trying to add the custom font (as best I can tell), but the problem still remains. Around the time I was trying to add the custom font, I remember using the command cache:disable, and maybe this messed something up? I've since used cache:enable, but the CLI responds with There is nothing to change in cache status.



I have searched online over the course of 3 days for a total of around 10 hours for a solution. Just so you know I've really tried to figure this out on my own, the following are some things I have tried many (many!) times, and in many variations as to their order and combination (I'm pretty sure new developers do this a lot!):



  • indexer:reindex

  • cache:clean

  • setup:upgrade

  • setup:static-content:deploy -f


  • deploy:mode:set production



    (The idea here was apparently setting it to Production Mode would clear things in a certain way, and then I was supposed to set it back to Developer Mode, and this would fix the problem. But I get an error part way through setting it to Production Mode when it tries to deploy static content, and it shows a message in bright red: Command returned non-zero exit code. Plus above that there's a line that reads: Something went wrong while deploying static content. See the error log for details. Is the error file it's talking about in 'var > log'? Because all the files in there have a 'Date modified' showing 8 days ago, which is way before this problem started. What log file is this referring to?)



  • using the 'Flush Static Files Cache' button (In Admin: System > Cache Management)


  • using the 'Flush JavaScript/CSS Cache' button (In Admin: System > Cache Management)

  • using the bright orange 'Flush Magento Cache' button (In Admin: System > Cache Management)

  • setting directory and file permissions (pretty much to 777 every time)

  • rm -rf view_preprocessed/*

  • rm -rf static/*

  • rm -rf var/cache,di,generation,page_cache,view_preprocessed

  • and I couldn't begin to tell you how many times I've hit 'Shift+F5' to refresh the storefront page

'No styling' seems like such a simple issue, but I can't figure this one out. Any help would be greatly appreciated!



I'm on Apache, all served from Google Cloud Platform (static IP), Bitnami stack.



Edit: screenshots added



browser view - no styling issue



console view - no styling issue










share|improve this question
















Disclaimer: I'm new to Magento 2 development as of Nov 2018, and new to development generally as of mid-2017. So I'm new to asking development-help questions too. Most of the time I can figure it out on my own. Please forgive me for anything I do that is something I should know not to do.



My problem:
All styling is gone from my frontend (admin is fine).



When the problem started:
When I was trying to add a custom font via an '_extend.less' file. (Creating this file and using it to make changes was the method that was being used in a tutorial I was following to make custom styling changes.)



(I have Magento set to Developer Mode.)



I have set everything back to the way it was before trying to add the custom font (as best I can tell), but the problem still remains. Around the time I was trying to add the custom font, I remember using the command cache:disable, and maybe this messed something up? I've since used cache:enable, but the CLI responds with There is nothing to change in cache status.



I have searched online over the course of 3 days for a total of around 10 hours for a solution. Just so you know I've really tried to figure this out on my own, the following are some things I have tried many (many!) times, and in many variations as to their order and combination (I'm pretty sure new developers do this a lot!):



  • indexer:reindex

  • cache:clean

  • setup:upgrade

  • setup:static-content:deploy -f


  • deploy:mode:set production



    (The idea here was apparently setting it to Production Mode would clear things in a certain way, and then I was supposed to set it back to Developer Mode, and this would fix the problem. But I get an error part way through setting it to Production Mode when it tries to deploy static content, and it shows a message in bright red: Command returned non-zero exit code. Plus above that there's a line that reads: Something went wrong while deploying static content. See the error log for details. Is the error file it's talking about in 'var > log'? Because all the files in there have a 'Date modified' showing 8 days ago, which is way before this problem started. What log file is this referring to?)



  • using the 'Flush Static Files Cache' button (In Admin: System > Cache Management)


  • using the 'Flush JavaScript/CSS Cache' button (In Admin: System > Cache Management)

  • using the bright orange 'Flush Magento Cache' button (In Admin: System > Cache Management)

  • setting directory and file permissions (pretty much to 777 every time)

  • rm -rf view_preprocessed/*

  • rm -rf static/*

  • rm -rf var/cache,di,generation,page_cache,view_preprocessed

  • and I couldn't begin to tell you how many times I've hit 'Shift+F5' to refresh the storefront page

'No styling' seems like such a simple issue, but I can't figure this one out. Any help would be greatly appreciated!



I'm on Apache, all served from Google Cloud Platform (static IP), Bitnami stack.



Edit: screenshots added



browser view - no styling issue



console view - no styling issue







magento2 css frontend less-css styles






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 19 at 10:56









Muhammad Anas

8031322




8031322










asked Dec 2 '18 at 2:57









devbikerdevbiker

62




62












  • Hi, please attach a screenshot of the front end with console logs. Are you on Apache or Nginx?

    – B G Kavinga
    Dec 2 '18 at 3:07











  • Kudos for a well written and well researched question...

    – Haim
    Dec 2 '18 at 5:48

















  • Hi, please attach a screenshot of the front end with console logs. Are you on Apache or Nginx?

    – B G Kavinga
    Dec 2 '18 at 3:07











  • Kudos for a well written and well researched question...

    – Haim
    Dec 2 '18 at 5:48
















Hi, please attach a screenshot of the front end with console logs. Are you on Apache or Nginx?

– B G Kavinga
Dec 2 '18 at 3:07





Hi, please attach a screenshot of the front end with console logs. Are you on Apache or Nginx?

– B G Kavinga
Dec 2 '18 at 3:07













Kudos for a well written and well researched question...

– Haim
Dec 2 '18 at 5:48





Kudos for a well written and well researched question...

– Haim
Dec 2 '18 at 5:48










3 Answers
3






active

oldest

votes


















1














Please check in your frontend store language. If frontend store language is different then you need to setup:static-content:deploy -f lanug_code.



Like, If your frontend store in Germany then run below command.




setup:upgrade

setup:static-content:deploy -f de_DE en_US

cache:clean

Give full permission to var/ and pub/ folder



de_DE use for frontend store and en_US for backend side.




I hope so it's work for you.






share|improve this answer























  • Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

    – devbiker
    Dec 2 '18 at 19:13


















0














Check followings (Suppose you are in developer mode),



  • Make sure .htaccess file is present under pub/static folder with correct contents. https://github.com/magento/magento2/blob/2.3-develop/pub/static/.htaccess

  • Make sure apache mod_rewrite is installed and enabled

  • Make sure .htaccess can alter

  • Delete caches. rm -rf var/cache var/page_cache generated var/generation var/view_processed

  • Restart varnish if exists

To troubleshoot the static content deployment issue



  • Try to compile blank theme. php bin/magento setup:static-content:deploy -t Magento/blank





share|improve this answer























  • .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

    – devbiker
    Dec 2 '18 at 19:51












  • Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

    – B G Kavinga
    Dec 3 '18 at 16:53


















0














Well, I came up with a solution: start a new custom theme.



No, that's not the solution I was hoping for. But sometimes the best thing to do is abandon something if it's not working and start over. In my case, fortunately, I wasn't too far along with the first theme, and it didn't take long to get back to where I left off. So I can confirm everything behind the scenes is still working fine. There's just something with what I was doing before that broke, and I couldn't fix it. I don't like that, because if whatever caused the problem happens again, I'm right back at the same place again. I really don't want a recurring solution of 'start over' every time. But I feel I spent enough time trying to figure it out, so let's just move forward, and cross that [broken] bridge if we come to it again.



Thanks to everyone for taking your time to try to help.






share|improve this answer























    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%2f252099%2ffrontend-styling-has-disappeared-and-i-cant-get-it-back%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Please check in your frontend store language. If frontend store language is different then you need to setup:static-content:deploy -f lanug_code.



    Like, If your frontend store in Germany then run below command.




    setup:upgrade

    setup:static-content:deploy -f de_DE en_US

    cache:clean

    Give full permission to var/ and pub/ folder



    de_DE use for frontend store and en_US for backend side.




    I hope so it's work for you.






    share|improve this answer























    • Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

      – devbiker
      Dec 2 '18 at 19:13















    1














    Please check in your frontend store language. If frontend store language is different then you need to setup:static-content:deploy -f lanug_code.



    Like, If your frontend store in Germany then run below command.




    setup:upgrade

    setup:static-content:deploy -f de_DE en_US

    cache:clean

    Give full permission to var/ and pub/ folder



    de_DE use for frontend store and en_US for backend side.




    I hope so it's work for you.






    share|improve this answer























    • Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

      – devbiker
      Dec 2 '18 at 19:13













    1












    1








    1







    Please check in your frontend store language. If frontend store language is different then you need to setup:static-content:deploy -f lanug_code.



    Like, If your frontend store in Germany then run below command.




    setup:upgrade

    setup:static-content:deploy -f de_DE en_US

    cache:clean

    Give full permission to var/ and pub/ folder



    de_DE use for frontend store and en_US for backend side.




    I hope so it's work for you.






    share|improve this answer













    Please check in your frontend store language. If frontend store language is different then you need to setup:static-content:deploy -f lanug_code.



    Like, If your frontend store in Germany then run below command.




    setup:upgrade

    setup:static-content:deploy -f de_DE en_US

    cache:clean

    Give full permission to var/ and pub/ folder



    de_DE use for frontend store and en_US for backend side.




    I hope so it's work for you.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Dec 2 '18 at 6:19









    Sweety MasmiyaSweety Masmiya

    1458




    1458












    • Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

      – devbiker
      Dec 2 '18 at 19:13

















    • Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

      – devbiker
      Dec 2 '18 at 19:13
















    Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

    – devbiker
    Dec 2 '18 at 19:13





    Thanks for the suggestion. I'm using 'en_US' only. I've never enabled any other languages.

    – devbiker
    Dec 2 '18 at 19:13













    0














    Check followings (Suppose you are in developer mode),



    • Make sure .htaccess file is present under pub/static folder with correct contents. https://github.com/magento/magento2/blob/2.3-develop/pub/static/.htaccess

    • Make sure apache mod_rewrite is installed and enabled

    • Make sure .htaccess can alter

    • Delete caches. rm -rf var/cache var/page_cache generated var/generation var/view_processed

    • Restart varnish if exists

    To troubleshoot the static content deployment issue



    • Try to compile blank theme. php bin/magento setup:static-content:deploy -t Magento/blank





    share|improve this answer























    • .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

      – devbiker
      Dec 2 '18 at 19:51












    • Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

      – B G Kavinga
      Dec 3 '18 at 16:53















    0














    Check followings (Suppose you are in developer mode),



    • Make sure .htaccess file is present under pub/static folder with correct contents. https://github.com/magento/magento2/blob/2.3-develop/pub/static/.htaccess

    • Make sure apache mod_rewrite is installed and enabled

    • Make sure .htaccess can alter

    • Delete caches. rm -rf var/cache var/page_cache generated var/generation var/view_processed

    • Restart varnish if exists

    To troubleshoot the static content deployment issue



    • Try to compile blank theme. php bin/magento setup:static-content:deploy -t Magento/blank





    share|improve this answer























    • .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

      – devbiker
      Dec 2 '18 at 19:51












    • Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

      – B G Kavinga
      Dec 3 '18 at 16:53













    0












    0








    0







    Check followings (Suppose you are in developer mode),



    • Make sure .htaccess file is present under pub/static folder with correct contents. https://github.com/magento/magento2/blob/2.3-develop/pub/static/.htaccess

    • Make sure apache mod_rewrite is installed and enabled

    • Make sure .htaccess can alter

    • Delete caches. rm -rf var/cache var/page_cache generated var/generation var/view_processed

    • Restart varnish if exists

    To troubleshoot the static content deployment issue



    • Try to compile blank theme. php bin/magento setup:static-content:deploy -t Magento/blank





    share|improve this answer













    Check followings (Suppose you are in developer mode),



    • Make sure .htaccess file is present under pub/static folder with correct contents. https://github.com/magento/magento2/blob/2.3-develop/pub/static/.htaccess

    • Make sure apache mod_rewrite is installed and enabled

    • Make sure .htaccess can alter

    • Delete caches. rm -rf var/cache var/page_cache generated var/generation var/view_processed

    • Restart varnish if exists

    To troubleshoot the static content deployment issue



    • Try to compile blank theme. php bin/magento setup:static-content:deploy -t Magento/blank






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Dec 2 '18 at 5:27









    B G KavingaB G Kavinga

    1,136410




    1,136410












    • .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

      – devbiker
      Dec 2 '18 at 19:51












    • Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

      – B G Kavinga
      Dec 3 '18 at 16:53

















    • .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

      – devbiker
      Dec 2 '18 at 19:51












    • Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

      – B G Kavinga
      Dec 3 '18 at 16:53
















    .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

    – devbiker
    Dec 2 '18 at 19:51






    .htaccess is present (permissions are 777), and has the same content as the one you linked to... apart from something about 'moxieplayer' in the linked one which I've ignored. I tried to delete caches as you suggested, but get 'Permission denied' for all files even though permissions are 777 recursively. I used sudo /opt/bitnami/ctlscript.sh restart for both apache and varnish. I get varnish started at port 80 and httpd started at port 81(apache). Should the ports match? Compiled blank theme... still getting ''static content' error. In httpd.conf, changed AllowOverride to All from None

    – devbiker
    Dec 2 '18 at 19:51














    Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

    – B G Kavinga
    Dec 3 '18 at 16:53





    Seems you have a file permission issue. Try running static content deploy as root user. sudo php bin/magento setup:static-content:deploy -t Magento/blank The ports shouldn't be the same. Hope you have updated the varnish vcl.

    – B G Kavinga
    Dec 3 '18 at 16:53











    0














    Well, I came up with a solution: start a new custom theme.



    No, that's not the solution I was hoping for. But sometimes the best thing to do is abandon something if it's not working and start over. In my case, fortunately, I wasn't too far along with the first theme, and it didn't take long to get back to where I left off. So I can confirm everything behind the scenes is still working fine. There's just something with what I was doing before that broke, and I couldn't fix it. I don't like that, because if whatever caused the problem happens again, I'm right back at the same place again. I really don't want a recurring solution of 'start over' every time. But I feel I spent enough time trying to figure it out, so let's just move forward, and cross that [broken] bridge if we come to it again.



    Thanks to everyone for taking your time to try to help.






    share|improve this answer



























      0














      Well, I came up with a solution: start a new custom theme.



      No, that's not the solution I was hoping for. But sometimes the best thing to do is abandon something if it's not working and start over. In my case, fortunately, I wasn't too far along with the first theme, and it didn't take long to get back to where I left off. So I can confirm everything behind the scenes is still working fine. There's just something with what I was doing before that broke, and I couldn't fix it. I don't like that, because if whatever caused the problem happens again, I'm right back at the same place again. I really don't want a recurring solution of 'start over' every time. But I feel I spent enough time trying to figure it out, so let's just move forward, and cross that [broken] bridge if we come to it again.



      Thanks to everyone for taking your time to try to help.






      share|improve this answer

























        0












        0








        0







        Well, I came up with a solution: start a new custom theme.



        No, that's not the solution I was hoping for. But sometimes the best thing to do is abandon something if it's not working and start over. In my case, fortunately, I wasn't too far along with the first theme, and it didn't take long to get back to where I left off. So I can confirm everything behind the scenes is still working fine. There's just something with what I was doing before that broke, and I couldn't fix it. I don't like that, because if whatever caused the problem happens again, I'm right back at the same place again. I really don't want a recurring solution of 'start over' every time. But I feel I spent enough time trying to figure it out, so let's just move forward, and cross that [broken] bridge if we come to it again.



        Thanks to everyone for taking your time to try to help.






        share|improve this answer













        Well, I came up with a solution: start a new custom theme.



        No, that's not the solution I was hoping for. But sometimes the best thing to do is abandon something if it's not working and start over. In my case, fortunately, I wasn't too far along with the first theme, and it didn't take long to get back to where I left off. So I can confirm everything behind the scenes is still working fine. There's just something with what I was doing before that broke, and I couldn't fix it. I don't like that, because if whatever caused the problem happens again, I'm right back at the same place again. I really don't want a recurring solution of 'start over' every time. But I feel I spent enough time trying to figure it out, so let's just move forward, and cross that [broken] bridge if we come to it again.



        Thanks to everyone for taking your time to try to help.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 3 '18 at 15:48









        devbikerdevbiker

        62




        62



























            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%2f252099%2ffrontend-styling-has-disappeared-and-i-cant-get-it-back%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

            Sum ergo cogito? 1 nng

            三茅街道4182Guuntc Dn precexpngmageondP