It seems I can't get the Manage fields page to open...

I tried setting up a node flag, set it to Confirmation form but still when clicking on Manage fields Drupal takes me to the standard flag edit page...

Comments

joachim’s picture

Title: Manage fields redirects to flag edit page » After creating first flag, 'Manage fields' link goes to flag edit page
Version: 7.x-3.0-alpha4 » 7.x-3.x-dev

Clearing cache fixes it, though not sure why the menu path isn't registering in the first place. Will look into it.

joachim’s picture

Status: Active » Needs review
StatusFileSize
new2.08 KB

Ah, 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.

joachim’s picture

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.

Anonymous’s picture

> 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.

joachim’s picture

I 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.

joachim’s picture

Status: Needs review » Needs work
joachim’s picture

Tagging.

joachim’s picture

Status: Needs work » Needs review
StatusFileSize
new2.44 KB

Here's a reworked patch.

Could someone try this out on a site with no flags? Thanks!

joachim’s picture

Status: Needs review » Fixed

Committed.

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.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

podarok’s picture

untag