When attempting to use Rules and VBO to create a UI for adding taxonomy terms to a deployment plan, I noticed that fetch-only deployment plans were explicitly removed from the drop-down list in the Rules UI when selecting the plan to add to. I can only assume that this is an error, as this is one of the only viable ways of constructing such a plan to use with UUID entity export via Features.
Patch to follow shortly. If this is the intended behavior, I would still like to submit the same patch as a feature request for the same reasons (feel free to change status).
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | interdiff.txt | 1.21 KB | manuel garcia |
| #7 | 1483896-7.patch | 1.29 KB | manuel garcia |
| #1 | 1483896--deploy-allow-add-fetch-only-rules--1.patch | 364 bytes | alexiswatson |
Comments
Comment #1
alexiswatson commentedPatch attached.
Comment #2
aspilicious commentedIf this is correct we should just replace the calback function in the info hook as the wrapper has no use anymore.
Comment #3
dixon_I can't recall why I did like this when implementing this.
If all tests pass with this patch, it should be ok. But tests have to be run locally, because we still have issues with the d.o test bot here.
I'm going to look into this shortly.
Comment #4
aspilicious commentedDo we have rules tests? I can't find any...
Tests work localy but I don't think they call any rules functions, or do they?
Comment #5
henrijs.seso commentedAdds missing item to actions. Seems trivial and important.
Comment #6
hnln commentedThis patch works for me.
Comment #7
manuel garcia commentedAddressing #2 and deprecating the wrapping function.