I cannot access a custom targeted action (404) after upgrading from -dev to RC1. I'm trying to figure out where it's coming from, from what I can tell so far the controller is not being saved correctly so when the resource is accessed, the resource is empty/malformed.

CommentFileSizeAuthor
#1 targeted_actions_404-1153010-1.patch2.81 KBdabblela

Comments

dabblela’s picture

StatusFileSize
new2.81 KB

Patch attached. #1152122: "Targeted actions" listed as a resource fixed here as well.

dabblela’s picture

Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, targeted_actions_404-1153010-1.patch, failed testing.

spuky’s picture

Status: Needs work » Needs review

The Patch fixed my issues with unrecognised targeted actions after updating from -dev to -rc1

since it changes the API from 'targeted actions' to 'targeted_actions' i suggest review by somone who knows what implicatons go along with that change...

voxpelli’s picture

This patch is kind of included in or related to #1154420: Readd support for rich options for resources - needed by auth mechanism I think.

dabblela’s picture

I think that would fix the 'display' portion that this patch addresses, but would not actually fix targeted actions.

kylebrowning’s picture

Ok, This is ready to go, Ive re-reolled it against head, I'm just waiting to get another commit in before this one, b/c it affects the same code. Bear with me.

didlix’s picture

Do you mean RC1 to Dev? Since RC1 was posted on the 5th May and Dev has been being updated frequently?

didlix’s picture

Also, you may well be on top of this, but please see http://drupal.org/node/1224494 where I am getting the same for actions.

kylebrowning’s picture

Version: 6.x-3.0-rc1 » 7.x-3.x-dev
Status: Needs review » Fixed

This is fixed in both 6.x-3.x-dev and 7.x-3.x-dev

kylebrowning’s picture

Status: Fixed » Closed (fixed)