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

Commit 42ce933

Browse files
authored
Merge pull request #5565 from drpayyne/issue-5179
Resolved issue #5179
2 parents 833bffe + 1531760 commit 42ce933

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

guides/v2.2/frontend-dev-guide/themes/theme-create.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -260,7 +260,10 @@ To learn more about theme layouts, refer to the [Layout section]({{page.baseurl}
260260

261261
## Troubleshooting {#trouble}
262262

263-
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).
263+
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.
264+
265+
{: .bs-callout-info }
266+
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.
264267

265268
## What's next {#next}
266269

guides/v2.3/frontend-dev-guide/themes/theme-create.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,10 @@ To learn more about theme layouts, refer to the [Layout section]({{page.baseurl}
261261

262262
## Troubleshooting {#trouble}
263263

264-
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).
264+
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.
265+
266+
{: .bs-callout-info }
267+
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.
265268

266269
## What's next {#next}
267270

0 commit comments

Comments
 (0)