You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the plugin to generate several different feeds for the same pages. One is for standard feed readers, and several others are for cross-posting to other places. Each feed uses different fields for the URL and description depending on the purpose of the feed. (e.g. some feeds get the entire content of the page as the description, others get a shorter excerpt, etc.)
Since modifiedHashFromKeys() only factors in the snippet value and the modified dates from the pages, feeds that are populated from the same list of pages share the same cache key even if they output different fields. This means all the variations display the cached version of whichever feed is loaded first rather than rendering their own.
Would it be possible to include more of the options in the modified hash to ensure each variation gets its own entry in the cache? For my specific purposes, just the urlfield and textfield would be enough. But for more general use-cases, it might make sense to include others as well.
The text was updated successfully, but these errors were encountered:
New plugin v5 (matching the soon-to-be-release Kirby v5) has improved caching and takes the feed URL into account, which should be unique in your use case.
Despite being flagged as v5, you can use the plugin with k4.
Hi!
I'm using the plugin to generate several different feeds for the same pages. One is for standard feed readers, and several others are for cross-posting to other places. Each feed uses different fields for the URL and description depending on the purpose of the feed. (e.g. some feeds get the entire content of the page as the description, others get a shorter excerpt, etc.)
Since
modifiedHashFromKeys()
only factors in the snippet value and the modified dates from the pages, feeds that are populated from the same list of pages share the same cache key even if they output different fields. This means all the variations display the cached version of whichever feed is loaded first rather than rendering their own.Would it be possible to include more of the options in the modified hash to ensure each variation gets its own entry in the cache? For my specific purposes, just the
urlfield
andtextfield
would be enough. But for more general use-cases, it might make sense to include others as well.The text was updated successfully, but these errors were encountered: