Have followed instructions to disable cache for development but it's still cachingCache remains stale for...

Paradox regarding phase transitions in relativistic systems

Plausibility and performance of a composite longbow

Are there any instances in Tanach of Lashon Hara said purely for non-constructive purposes?

What was the deeper meaning of Hermione wanting the cloak?

What's the benefit of prohibiting the use of techniques/language constructs that have not been taught?

Madrid to London w/ Expired 90/180 days stay as US citizen

Is this adjustment to the Lucky feat underpowered?

What's the word for a student who doesn't register but goes to a class anyway?

Should I inform my future product owner that there is a good chance that a team member will leave the company soon?

Is a global DNS record a security risk for phpMyAdmin?

How do you determine which representation of a function to use for Newton's method?

Amiga 500 OCS/ECS vs Mega Drive VDP

When would open interest equal trading volume?

Why do things cool off?

Delete empty subfolders, keep parent folder

Minimize taxes now that I earn a living wage

All numbers in a 5x5 Minesweeper grid

Problem of Induction: Dissolved

Can I separate garlic into cloves for storage?

What happens when I use Drawmij's Instant Summons on Dimensional Shackles?

Can one guy with a duplicator trigger a nuclear apocalypse?

Is Zack Morris's 'time stop' ability in "Saved By the Bell" a supernatural ability?

What is the word for a person who destroys monuments?

As an employer, can I compel my employees to vote?



Have followed instructions to disable cache for development but it's still caching


Cache remains stale for custom blocks after editingCustom cache context confusionWhat is the correct way to set cache contexts on custom blocks?Proper debugging of REST Resource due to cacheCache max-age doesn't correctly expire at midnightHow to discard unsaved changes to a view when editing it leads to a WSOD?Hide fields in Paragraphs conditionally using Form API #states






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I have followed all the instructions here https://www.drupal.org/node/2598914



I'm developing a module with a block, and when I went to the Block Layout page and clicked "Place Block", the list of blocks did not come up due to an error in my code. I edited the code and was sure it was correct, yet it still didn't work. So I tried doing "drush cr" just in case the cache wasn't really disabled ... and that made it work.



So it seems to me that the cache has not been disabled by following those instructions. Is there something missing?



Edit: This has happened again when I have made new changes, even after the plugin has successfully loaded. It happens when when I make any changes to src/Plugin/Derivative/Foo.php (inside my module). Those changes aren't picked up until I manually cache rebuild










share|improve this question

































    2















    I have followed all the instructions here https://www.drupal.org/node/2598914



    I'm developing a module with a block, and when I went to the Block Layout page and clicked "Place Block", the list of blocks did not come up due to an error in my code. I edited the code and was sure it was correct, yet it still didn't work. So I tried doing "drush cr" just in case the cache wasn't really disabled ... and that made it work.



    So it seems to me that the cache has not been disabled by following those instructions. Is there something missing?



    Edit: This has happened again when I have made new changes, even after the plugin has successfully loaded. It happens when when I make any changes to src/Plugin/Derivative/Foo.php (inside my module). Those changes aren't picked up until I manually cache rebuild










    share|improve this question





























      2












      2








      2








      I have followed all the instructions here https://www.drupal.org/node/2598914



      I'm developing a module with a block, and when I went to the Block Layout page and clicked "Place Block", the list of blocks did not come up due to an error in my code. I edited the code and was sure it was correct, yet it still didn't work. So I tried doing "drush cr" just in case the cache wasn't really disabled ... and that made it work.



      So it seems to me that the cache has not been disabled by following those instructions. Is there something missing?



      Edit: This has happened again when I have made new changes, even after the plugin has successfully loaded. It happens when when I make any changes to src/Plugin/Derivative/Foo.php (inside my module). Those changes aren't picked up until I manually cache rebuild










      share|improve this question
















      I have followed all the instructions here https://www.drupal.org/node/2598914



      I'm developing a module with a block, and when I went to the Block Layout page and clicked "Place Block", the list of blocks did not come up due to an error in my code. I edited the code and was sure it was correct, yet it still didn't work. So I tried doing "drush cr" just in case the cache wasn't really disabled ... and that made it work.



      So it seems to me that the cache has not been disabled by following those instructions. Is there something missing?



      Edit: This has happened again when I have made new changes, even after the plugin has successfully loaded. It happens when when I make any changes to src/Plugin/Derivative/Foo.php (inside my module). Those changes aren't picked up until I manually cache rebuild







      8 blocks caching






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 5 hours ago







      naomi

















      asked 8 hours ago









      naominaomi

      3933 silver badges18 bronze badges




      3933 silver badges18 bronze badges

























          1 Answer
          1






          active

          oldest

          votes


















          3
















          You've disabled the render, dynamic_page_cache, and page cache bins; plugin discovery is stored in a different bin (discovery). You probably don't want to disable that bin, as it's likely to slow the site down appreciably (the project will be scanned for plugins on every request).



          If you just keep in mind that you need to rebuild caches manually when you add a plugin, implement a hook, or add/change a .yml file in the module's root, you'll be able to work a lot faster.






          share|improve this answer




























          • Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

            – naomi
            5 hours ago













          • In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

            – Clive
            5 hours ago











          • Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

            – 4k4
            4 hours ago














          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "220"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });















          draft saved

          draft discarded
















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdrupal.stackexchange.com%2fquestions%2f286425%2fhave-followed-instructions-to-disable-cache-for-development-but-its-still-cachi%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3
















          You've disabled the render, dynamic_page_cache, and page cache bins; plugin discovery is stored in a different bin (discovery). You probably don't want to disable that bin, as it's likely to slow the site down appreciably (the project will be scanned for plugins on every request).



          If you just keep in mind that you need to rebuild caches manually when you add a plugin, implement a hook, or add/change a .yml file in the module's root, you'll be able to work a lot faster.






          share|improve this answer




























          • Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

            – naomi
            5 hours ago













          • In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

            – Clive
            5 hours ago











          • Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

            – 4k4
            4 hours ago
















          3
















          You've disabled the render, dynamic_page_cache, and page cache bins; plugin discovery is stored in a different bin (discovery). You probably don't want to disable that bin, as it's likely to slow the site down appreciably (the project will be scanned for plugins on every request).



          If you just keep in mind that you need to rebuild caches manually when you add a plugin, implement a hook, or add/change a .yml file in the module's root, you'll be able to work a lot faster.






          share|improve this answer




























          • Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

            – naomi
            5 hours ago













          • In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

            – Clive
            5 hours ago











          • Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

            – 4k4
            4 hours ago














          3














          3










          3









          You've disabled the render, dynamic_page_cache, and page cache bins; plugin discovery is stored in a different bin (discovery). You probably don't want to disable that bin, as it's likely to slow the site down appreciably (the project will be scanned for plugins on every request).



          If you just keep in mind that you need to rebuild caches manually when you add a plugin, implement a hook, or add/change a .yml file in the module's root, you'll be able to work a lot faster.






          share|improve this answer















          You've disabled the render, dynamic_page_cache, and page cache bins; plugin discovery is stored in a different bin (discovery). You probably don't want to disable that bin, as it's likely to slow the site down appreciably (the project will be scanned for plugins on every request).



          If you just keep in mind that you need to rebuild caches manually when you add a plugin, implement a hook, or add/change a .yml file in the module's root, you'll be able to work a lot faster.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 5 hours ago

























          answered 7 hours ago









          CliveClive

          151k15 gold badges258 silver badges295 bronze badges




          151k15 gold badges258 silver badges295 bronze badges
















          • Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

            – naomi
            5 hours ago













          • In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

            – Clive
            5 hours ago











          • Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

            – 4k4
            4 hours ago



















          • Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

            – naomi
            5 hours ago













          • In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

            – Clive
            5 hours ago











          • Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

            – 4k4
            4 hours ago

















          Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

          – naomi
          5 hours ago







          Thanks. I've since worked out that the time I need to manually rebuild it is when I make a change to src/Plugin/Derivative/Foo.php. So it is not one of the scenarios you mention. Is that also to be expected do you think?

          – naomi
          5 hours ago















          In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

          – Clive
          5 hours ago





          In principle no, but it's difficult to say without more context. I should have mentioned those scenarios are probably just the most common, cache can be complicated. What are you changing in the derivative class that needs a cache clear afterwards?

          – Clive
          5 hours ago













          Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

          – 4k4
          4 hours ago





          Plugin derivatives need a rebuilt of the plugin cache, too. You can instruct the plugin manager of that specific plugin type to do this, if you don't want to clear all caches and so save some cpu cycles: Drupal::service('plugin.manager.block')->clearCachedDefinitions();, which is by the way what core does when saving a custom block to update the block plugin definitions derived from the database content.

          – 4k4
          4 hours ago



















          draft saved

          draft discarded



















































          Thanks for contributing an answer to Drupal Answers!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdrupal.stackexchange.com%2fquestions%2f286425%2fhave-followed-instructions-to-disable-cache-for-development-but-its-still-cachi%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Hudson River Historic District Contents Geography History The district today Aesthetics Cultural...

          The number designs the writing. Feandra Aversely Definition: The act of ingrafting a sprig or shoot of one...

          Ayherre Geografie Demografie Externe links Navigatiemenu43° 23′ NB, 1° 15′ WL43° 23′ NB, 1°...