throws a full-stop php error when it is invoked by the features module.

Comments

zzolo’s picture

zzolo commented

Just an FYI, the features implementation has been commented out (not by me)

phayes’s picture

phayes commented

That was me. It was breaking the entire site with a php error - so I just commented it out until someone could actually deal with it.

phayes’s picture

phayes commented
Version: 6.x-1.0-beta1 » 6.x-1.x-dev
zzolo’s picture

zzolo commented

Do we want to support this for 1.0? I think it would be great, but not sure how feasible it is. I believe it was put in there by tmcw in the first place, probably before their fork, so I am not sure if that incentive is still there. If I get a chance, I will try to look at in more detail. Thoughts?

tmcw’s picture

tmcw commented
Assigned: Unassigned » tmcw

This could be caused by an API change on the features side. I'll review the code over the weekend.

tmcw’s picture

tmcw commented
Status: Active » Closed (won't fix)

Sorry, marking as will not fix. It's taken a little bit to track the problem down, and since features support for 1.x is entirely different than 2.x, this isn't really a backporting task.