Closed (fixed)
Project:
Flag
Version:
7.x-3.x-dev
Component:
Flag core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
17 Dec 2012 at 08:17 UTC
Updated:
27 Sep 2018 at 07:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joachim commentedClearing cache fixes it, though not sure why the menu path isn't registering in the first place. Will look into it.
Comment #2
joachim commentedAh, it's because we've been returning no bundles to entity info until that point. Hence the menu paths don't exist.
We need to clear entity info cache when it's the first flag we're saving.
Comment #3
joachim commentedHmm on second thoughts, we should probably clear entity cache whenever a flag is new, as other things may want to know there's a new bundle.
Comment #4
Anonymous (not verified) commented> We need to clear entity info cache when it's the first flag we're saving.
> Hmm on second thoughts, we should probably clear entity cache whenever a flag is new, as other things may want to know there's a new bundle.
Confirmed: the described redirect behaviour is still present when adding a 2nd, 3rd, ... flag without clearing the cache after any new flag.
Comment #5
joachim commentedI don't think that's the case -- once the menu path exists for one flag, it exists for all of them because it uses a wildcard.
I think what you rather mean is that if you don't clear the cache after the first flag, it carries on not working. Which is because you still don't have the menu path registered.
Comment #6
joachim commentedComment #7
joachim commentedTagging.
Comment #8
joachim commentedHere's a reworked patch.
Could someone try this out on a site with no flags? Thanks!
Comment #9
joachim commentedCommitted.
Probably needs a backport, since 'Issue #1699328 by socketwench: Moved the bookmark flag to its own sub-module.' was committed on the 2.x branch before 3.x branched off.Nope, I wasn't reading git log properly.Comment #11
podarokuntag