Changing app/design/frontend/Mytheme/default/etc/view.xml - gallery var does not clear the necessary cache

[amenk]

It clears block_html + full_page when I can

        <var name="nav">thumbs</var> <!-- Gallery navigation style (false/thumbs/dots) -->

to
dots

but I don't see an effect.

Clearing all caches helps :)

[Vinai]

Thanks for the report. There must be an additional cache that is used.
Unfortunately the \Magento\Framework\View\Config class doesn't follow the same pattern as most other config classes, where the caching is handled by them directly. I'll have to dig a little.

[Vinai]

I just tried it and changed

<var name="gallery">
            <var name="nav">thumbs</var> <!-- Gallery navigation style (false/thumbs/dots) -->

to

<var name="gallery">
            <var name="nav">dots</var> <!-- Gallery navigation style (false/thumbs/dots) -->

using the luma theme.
The cache watcher cleaned the block_html and luma caches, and that was enough to apply the change during reload.

Two questions to help nail this down:

• What version of Magento are you using (2.3.2 here)?
• Can you please post your cache configuration from the app/etc/env.php?

Thanks!

[amenk]

• 2.3.2-p1
• app/etc/env.php I have to check, but it should be pretty standard.

But I am not using luma (I did not know there is a luma cache), but the snowdog SASS theme as a base - probably that is the problem?

What is the luma cache?

[Vinai]

Um, there is no luma cache, I meant layout - sorry :D

If you are using the file system cache storage, I suspect you are running into the bug fixed by this PR: magento/magento2#22228

Since Magento 2.1 there is a bug that causes the full page cache records to be written to the var/cache directory instead of var/page_cache. This issue causes the cache cleaner behavior to be erratic, mostly by FPC cache cleans having no effect.
There is an easy workaround, namely removing all cache configuration from the default app/etc/env.php. The bug only affects the default config with the file system cache backend. Redis or Varnish are not affected. The bug will be fixed in the (currently upcoming) Magento 2.3.4 release.

As stated above, as a workaround you could remove the cache config from the app/etc/env.php or alternatively, here an example of a file cache backend config with a cache ID prefix:

    'cache' => [
        'frontend' => [
            'default' => [
                'id_prefix' => 'e74_'
            ],
            'page_cache' => [
                'id_prefix' => 'e74_',
                'backend_options' => [
                    'cache_dir' => 'page_cache'
                ]
            ]
        ]
    ],

If you are using redis or varnish, the issue must have a different cause and will require more info.

[Vinai]

@amenk Can you please check if the issue is related to the page cache backend configuration bug I described above?

[amenk]

cache-clean --version 1.0.15 = 1.0.15

my cache config in env.php

'cache' => [
    'frontend' => [
        'default' => [
            'id_prefix' => 'e4f_'
        ],
        'page_cache' => [
            'id_prefix' => 'e4f_'
        ]
    ]
],

view.xml edited -> no effect (but fpc and blockhtml is cleared)

            'backend_options' => [
                'cache_dir' => 'page_cache'
            ]

added

-> Works

So I guess you were right, thanks :-)