Cache not cleared for Custom Categories associated with Custom Post Types #693
Comments
Was not able to reproduce what the customer had experienced. Steps Taken:
|
@renzms If you cache a Custom Post Type Category archive view, and then edit a published post that belongs to that Custom Post Type category, does the CPT Category archive cache get cleared automatically? |
Yes, under Auto Cache Clearing → Auto-Clear "Custom Post Type Archives" Too?, it's set to |
@renzms writes...
Did you get a Dashboard notification indicating that the associated Category cache was cleared? It shouldn't take "a few moments"; it should happen instantly, as soon as the post is updated, and there should be a Dashboard notification indicating that cache file was cleared. (A screenshot of what you see would be helpful.) |
Notice appears after editing. Cache is auto cleared.
I verified the Cache was actually clear by checking the directory via FTP, which is probably why it took a few moments but the notice was instant. |
@renzms Thank you. So it sounds like there is no issue here after all. Could you please post the code that you used to register the CPT and the CPT categories? |
I actually used this plugin to save some time and created multiple CPT categories: https://wordpress.org/plugins/custom-post-type-ui/ |
EDIT: See next comment; there is no bug. Steps to reproduce the problem
|
Well, scratch that. There is no bug. (But it was fun being an Actor in a Movie.)I remembered there was a setting in Comet Cache → Plugin Options → Automatic Cache Clearing → Auto-Clear "Custom Post Type Archives" Too? and when I checked that I found that it was disabled. Once I enabled that, the automatic clearing of Custom Term Archives worked perfectly: So the primary issue here is that the default for Automatically Clearing Custom Term Archives is disabled, which leads to confusion when users try to test it. I'm removing the @jaswsinc any opposition to that change? |
Referencing where this default is set to disabled: |
Nope. That sounds like a great idea to me also. |
@renzms The next step here would be to alter the default value here; changing it from |
Next Release Changelog:
|
Comet Cache v160521 has been released and includes changes from this GitHub Issue. See the v160521 announcement for further details.This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#693). |
A user writes...
I have not tested or reproduced this yet, so this needs to be tested.
Related: #399
The text was updated successfully, but these errors were encountered: