Skip to content

Commit

Permalink
Merge pull request magento#5565 from drpayyne/issue-5179
Browse files Browse the repository at this point in the history
Resolved issue magento#5179
  • Loading branch information
dobooth authored Oct 14, 2019
2 parents 833bffe + 1531760 commit 42ce933
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 2 deletions.
5 changes: 4 additions & 1 deletion guides/v2.2/frontend-dev-guide/themes/theme-create.md
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,10 @@ To learn more about theme layouts, refer to the [Layout section]({{page.baseurl}

## Troubleshooting {#trouble}

When your theme changes are not visible even after clearing the cache, try redeploying your static files using `magento setup:static-content:deploy en_US` (replacing the language/locale as appropriate).
When your theme changes are not visible even after clearing the cache, try redeploying your static files using the `magento setup:static-content:deploy` command, or add the `-f` argument to force deploy static content in any deployment mode in case you are not in production mode.

{: .bs-callout-info }
Running this command with the `-f` argument can fix issues regarding deployment of static content, but it removes **all** symlinks and deploys the actual static content files.

## What's next {#next}

Expand Down
5 changes: 4 additions & 1 deletion guides/v2.3/frontend-dev-guide/themes/theme-create.md
Original file line number Diff line number Diff line change
Expand Up @@ -261,7 +261,10 @@ To learn more about theme layouts, refer to the [Layout section]({{page.baseurl}

## Troubleshooting {#trouble}

When your theme changes are not visible even after clearing the cache, try redeploying your static files using `magento setup:static-content:deploy en_US` (replacing the language/locale as appropriate).
When your theme changes are not visible even after clearing the cache, try redeploying your static files using the `magento setup:static-content:deploy` command, or add the `-f` argument to force deploy static content in any deployment mode in case you are not in production mode.

{: .bs-callout-info }
Running this command with the `-f` argument can fix issues regarding deployment of static content, but removes **all** symlinks and deploys the actual static content files.

## What's next {#next}

Expand Down

0 comments on commit 42ce933

Please sign in to comment.