Deploy Static files - backend only or specific module #4398
Comments
alex-parra
changed the title
|
The GitHub issue tracker is intended for technical issues only. Please refer to the Community Forums or Magento Stack Exchange site for technical questions. In your case, the programming questions forum is likely the most appropriate. Feel free to reopen this issue if you think you have encountered a bug in Magento 2. |
taskula
pushed a commit
to Hypernova-Oy/magento2
that referenced
this issue
Jun 24, 2019
- fixed "[GitHub] catalog:images:resize = getimagesize(): Read error! in vendor/magento/module-catalog/Model/Product/Image.php on line 410 if an image is 0 bytes magento#8204" - fixed "CMS page of the second website with same URL key as first website, show content of the First website instead of second website content." - fixed "Error appears when a restricted user tries to add a new category from the product page" - fixed "Product attribute cannot be edited if the attribute was created with 2 same values" - fixed "Invalid join condition in Product Flat Indexer" - fixed "Fatal error on Import/Export page if deleted category ids exist in category path"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First time here, so apologies if not the right place for this.
I've search and could not find a way to deploy static files for the backend only.
Is this possible, planned or would cause issues?
Or is it possible to deploy static files for a specific module?
When we run bin/magento setup:static-content:deploy it goes through all themes.
And it takes too long (about 2 minutes) considering the only files that need updating are two from one module and backend only.
I've read that it's supposed to create symlinks in developer mode but that's not happening in my case.
Or I'm missing something?
Thanks
The text was updated successfully, but these errors were encountered: