Skip to main content
Drupal Answers

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    Am I right in assuming that you can (also) create a view of ALL (not more, not less) "previous submissions to be deleted? Also, can you improve your question by including an export of the Rules component(s) for which you wrote "The components work". 1 more question: any links to those "few older issues"? Commented Mar 5, 2017 at 20:59
  • Updates added. And yes, I can create a view of ALL. I'll have to go hunting for the links. Will post them here if I can locate them again. Commented Mar 5, 2017 at 21:20
  • For using Rules: Fetch by Property, you would use the author property and current user uid I guess. Or for the VBO view, you need a contextual filter for entityform author that takes default: URL argument: 2 (I think), and in your rule, send the current user uid in the rule action for VBO. I can look at this properly tomorrow. Commented Mar 6, 2017 at 16:56
  • That helps. I'm nearly there - added a compare userID variable to the rule component and placed that instead of the VBO in the Fetch series. It's still looking to match the user against the entity-fetch:0, though, and if there's no match, it doesn't work. I need to figure out how to get it to look only at the first item in the USER set. Commented Mar 7, 2017 at 3:18