Magento2 – Custom Module’s _module.less File Not Updating

cachefrontendlessmagento2

In a custom module I've created I'm using a _module.less file in it. At first it worked but any changes I make to it are not updating on the frontend.

I think it must be a cache issue but so far everything I've tried to fix it has not worked:

php bin/magento setup:upgrade; php bin/magento setup:di:compile;
php bin/magento cache:clean; php bin/magento setup:static-content:deploy;
rm -rf var/cache/; rm -rf var/generation/

I'm working in developer mode.

Any ideas?

UPDATE

I checked Less files in custom modules but unfortunately this does not answer my question. It explains how to use LESS in a custom module but not how to troubleshoot the issue I am having with the cache other than what I've tried already (see above).

Best Answer

Try:

$ rm -rf var/cache/* var/full_page/* var/generation/* var/view_preprocessed/* pub/static/*

This way Magento recompiles less files and also deploy all needed files again.

Related Solutions

Magento 2 – Error When Running bin/magento setup:upgrade After Creating Module

Simple, try the following commands. I have encountered this error, and I have overcome.

rm -rf var/di/* 
rm -rf pub/static/_cache/* 
rm -rf pub/static/frontend/*
rm -rf var/generation/* 
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf var/view_preprocessed/*

In magento 2

var/di has been replaced by generated/metadata

var/generation has been replaced by generated/code

I switched to Developer Mode, and deleted the below files.

rm -rf generated/metadata/* 
rm -rf pub/static/_cache/* 
rm -rf pub/static/frontend/*
rm -rf generated/code/* 
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf var/view_preprocessed/*

never delete pub/static/.htaccess. putting star *at the end does not delete .htaccess file in the folder.

you may also need to run setup di compile to optimize and regenerate magento2 file system.

bin/magento setup:di:compile
bin/magento indexer:reindex

Magento – Cannot install module in Magento 2

If you have access to the DB of the site, take a look at the setup_module table to see if your module is showing up there. It should have the name and the current module version. If it's not showing up in that table, then your configuration files are incorrect. A module only requires two files to be registered:

app/code/{{vender_name}}/{{module_name}}/etc/module.xml

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Module/etc/module.xsd">
    <module name="{{vender_name}}_{{module_name}}" setup_version="0.0.1"/>
</config>

and

app/code/{{vender_name}}/{{module_name}}/registration.php

<?php
    \Magento\Framework\Component\ComponentRegistrar::register(
        \Magento\Framework\Component\ComponentRegistrar::MODULE,
        '{{vender_name}}_{{module_name}}',
        __DIR__
    );

If your module is registered correctly, then your next step is de-bugging the module's code. I would recommend looking at the layout xml files and the controller files that should be hitting, as this is the first step in any module's life cycle.

Best Answer

Related Solutions

Magento 2 – Error When Running bin/magento setup:upgrade After Creating Module

Magento – Cannot install module in Magento 2

Related Topic