Cannot Uninstall Luma theme #3650
Comments
|
@bsuresh Thank you for reporting, we have created MAGETWO-50182 to track and fix it. |
mazhalai
added
Issue: Ready for Work
|
You have to manually remove all /Luma/ directories and then run /bin/magento setup:upgrade and redeploy all static content! |
|
A part of the challenge is to make deployment simple, we have a composer metapackage that points at everything to download. This includes the Luma theme. For modules it is not a problem, because you can turn off modules (via config.php). But there currently is not a switch to turn of themes, causing problems like this. The sample data modules are optional and can be easily omitted, but the Luma theme itself is not. I suspect this is why the CLI uninstall theme command is not working - I don't think Luma is an additional optional theme added to the composer.json file, so the CLI command cannot remove it. Maybe that is the problem and solution - move the Luma theme to be an extra module, just like the sample data. Then its easy to make optional. |
|
Always keep in mind - Magento is owned by eBay :( |
|
and remove the reference entry in themes table in db |
|
Not sure what you meant by "Magento is owned by eBay" exactly, but to be clear - we are NOT owned by eBay since November last year. We are Magento Commerce, a separate company. We are still going through separation efforts, but company focus is now all about Magento. |
|
Nice, good to know! I just have person affection towards eBay. 👎 |
|
Closing since the author didn't answered |
|
This is still an issue. If you install Magento 2.1-rc1 (sorry, haven't had a chance to play with rc2), change the settings to use the 'blank' theme, and then try to remove the luma theme: $ php bin/magento theme:uninstall frontend/Magento/luma
Unable to uninstall. Please resolve the following issues:
frontend/Magento/luma has the following dependent package(s):
magento/product-community-editionAlthough I'm not sure if you should be able to remove themes which come with Magento 2 built-in, since this command is actually removing files (if I understand the docs correctly?). And this will probably cause issues, because a Magento upgrade will put those files back into place. So I don't think you should be able to remove built-in themes from Magento 2. If the Magento team agrees with this, you can keep the ticket closed. Otherwise, you'll have to re-open it :) |
|
still and issue in rc3. very annoying. |
|
Yeah, I'm with ClaudiuCreanga above, having to sit through the deployment of the Luma frontend every time I'm forced to re-deploy static after an upgrade, is very annoying. I can see why the frontend/Magento/blank would be a dependency, but can't see why the frontend/Magento/luma is a dependency. |
|
Hi guys! |
|
Hello @MomotenkoNatalia While you're at it. When we select the site language in the "Locale Options" in the system configurations to Locale "English (Australia)", it changes the site language to en_AU in the frontend but the admin is still in en_US. This means we need to deploy both en_AU and en_US, the en_AU for the frontend and the en_US for the backend. This takes along time, and if we can't change the backend language, why not only deploy the backend in en_US regardless of the locale setting. Also, when changing the developer settings to minimizes the css, the delopyment process does create the css with the filename .min.css, but when the site render the html in the page, it has the normal filename .css. This causes problems. |
|
Hello @slavvka Also as a side note, the upgrade/deployment/compilation process can take considerable time. For production systems that also compile the code, it's taking nearly/over an hour to complete. Can you make the deployment process to enter the developer mode rather than the maintenance mode, where the site can operated with the raw css/less and without the generated/compiled files while the deployment/compilation process is completing? Pulling down a production system for over an hour to update it is just too long. |
|
Any update on this? |
|
Yeah, still there in 2.1.6. Should we be following @viktor-zhuromskyy instructions for now? |
|
if someone still want to uninstall it,
the warning pique my interest, but when i re-run the command i got unknown theme. hopefully it leave no trace 😃 |
|
In 2.1.7 it returns following output when running the steps from @Zabanya update -> found a workaround: after this error
|
|
3 years later and this bug has still not bee fixed. Isn't it just a matter of removing the dependency and add the theme as a suggestion in composer.json? |
|
Still same issue, when we add product it create unnecessary copy of product images in cache because of that its create disk space. Execution time: 710.88578796387 |
|
@PsmIndia: product images have nothing to do with the static content deployment procedure, right? Also: what Magento version are you using? I'm pretty conviced that on the latest versions, Magento no longer generates resized product images for themes you don't use. |
|
i using magento 2.3.4[updated, move from m1], i have 50K products, when i try to do duplicate a products its take in infinite loop, until server crash, also its increase disk space, try to find solution but i am not, so setup it my local system and and i deleted all products, only keep 500 products, also i deleted all images too, now i try to make duplicate its successful, so now i add a product image, after than i check These million line in log file
|
|
For the duplicate issue, you are probably running into #9466 which is supposed to get fixed in Magento 2.4.0 You can ignore those lines in your log file, they have to do with cache invalidation which is expected and not a problem. The 18 or 19 resized images you are noticing probably come from the I'd strongly recommend to further look for help on https://magento.stackexchange.com/ or on https://community.magento.com/, because this issue you are having doesn't appear to be related to trying to remove the luma theme from a Magento installation. Good luck! 🙂 |
sdzhepa
added
the
Triage: Dev.Experience
ghost
removed
Issue: Clear Description
|
@magento I'm working on it |
|
@magento I’m working on this |
|
@magento I’m working on this |
|
@magento I am working on this |
gabrieldagama
added
Priority: P4
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Thank you for your contributions. |
m2-community-project
bot
added
Progress: done
and removed
Progress: ready for dev
labels
|
Untested, but you can probably remove the luma theme using a composer trick:
"replace": {
"magento/theme-frontend-luma": "*"
}
This might work, but as mentioned above, I haven't actually tested this. |
|
This is still an issue in Magento 2.4.3-p1 |
and others
We are in process of creating our base theme. We are looking at removing Luma theme followed the steps (http://devdocs.magento.com/guides/v2.0/install-gde/install/cli/install-cli-theme-uninstall.html)
We can't seem to un-install Luma theme, this is a fresh Magento installation on vagrant box.
`$ php bin/magento theme:uninstall frontend/Magento/luma
Unable to uninstall. Please resolve the following issues:
frontend/Magento/luma is a parent of physical theme. Parent themes cannot be uninstalled.
frontend/Magento/luma has the following dependent package(s):
magento/product-community-edition`
The text was updated successfully, but these errors were encountered: