Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Resolved issue #5179 #5565

Merged
merged 8 commits into from
Oct 14, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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