Closed (outdated)
Project:
Flag
Version:
7.x-3.x-dev
Component:
Flag core
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
31 Dec 2011 at 00:52 UTC
Updated:
18 Aug 2025 at 10:55 UTC
Jump to comment: Most recent
Comments
Comment #1
quicksketchSounds interesting but not really something that should be in Flag core, IMO. I don't think Flag should really be getting into caching pages or entities, though using local storage as a complement to cookies to keep track of flagged content could be interesting and more secure than sending cookies back and forth all the time.
Comment #2
coltraneFlag wouldn't be caching the whole page, just some properties of certain entities. This could be rendered a couple ways on a page, depending on how content is shown.
On a listing of content JS could read flagged entity ids from localstorage and mark the corresponding content so.
If it's a specialized list of already flagged content then more details would need to be stored in localstorage to render that list. For example a page of flagged content could only show that content from localstorage if its all stored there, id's title, url etc.
Comment #3
quicksketchThis sounds like what we're doing already with cookies and anonymous user flagging. Already we're rending all flags in the "unflagged" state, then iterating over all flagged content stored in cookies and toggling all the links to their flagged state.
I'm still pretty skeptical of this feature request, it sounds interesting but so far it's a lot of hand-waving and not a lot of concrete suggestion.
Comment #4
coltrane"a lot of hand-waving and not a lot of concrete suggestion"
Haha, fair enough. I certainly wasn't requesting that you work on this for me, but "testing the waters" so-to-speak.
Comment #5
joachim commentedUpping the version.
Comment #6
ivnishDrupal 7 is EOL. No more new features will be added.