I'm trying to set up rules to create a content page. But the create content action only gives a field to set the title, but where's the body, and the vocab, so I can tell rules where to put the new content?

Not unexpectedly, the rule itself doesn't work.

Comments

amitaibu’s picture

Component: Rules Core » Rules Engine
Status: Active » Postponed (maintainer needs more info)

For the vocab you should use other actions - Load vocab; Add term to content.
I'm not sure if you can change the body without some PHP, but if it was a CCK field you can use CCK actions provided by rules.

Not unexpectedly, the rule itself doesn't work.

That's not a very helpful comment, is it? ;)

fago’s picture

indeed that's missing - we could add a simple action for that like I just recently did for the title.

Flying Drupalist’s picture

Thanks for your help.

"That's not a very helpful comment, is it? ;)"

I only meant that there was no new content created, which doesn't surprise me as the content had nothing to go on to be created, but it actually sounds like you expect there to be a content despite there being no body and taxonomy, which means that there's a different problem.

I'll try a custom type with cck and the load term action. Thanks, will get back.

mitchell’s picture

Title: Create Content? No body or vocabs? » Include Body field settings for 'Add new content' action
Category: support » feature
StatusFileSize
new97.7 KB

Everything else here seems to have been addressed here.

fago’s picture

Title: Include Body field settings for 'Add new content' action » Add "Set content body" action
Status: Postponed (maintainer needs more info) » Active

I'd prefer to have that in a separate action "Set content body".

Christopher Herberte’s picture

subscribe,
would be useful for creating a forum topic from node title (forum topic requires body)

castawaybcn’s picture

I am not sure if this too old a request, but I would also be very interested in this feature

aantonop’s picture

Status: Active » Needs review
StatusFileSize
new496 bytes
new943 bytes

Ok, here's a patch that adds a new action to set the content body.

Tested and working, on my end.

fago’s picture

Status: Needs review » Needs work

I think it should also contain the usual input format selector and set it, as when you are usually editing a node body. Also please create patches from the module's root directory.

aantonop’s picture

hm not sure how to set input selector, but I agree. Let me do some more studying. Thanks for your patience and suggestions!

I will see if I can improve this and then re-submit from root of modules.

Michsk’s picture

i also would need this

Michsk’s picture

to bad this wasn't in the new release... any idea when we can expect set content body?

Michsk’s picture

how is this going guys?

mitchell’s picture

Title: Add "Set content body" action » Action: Set content body
Version: 6.x-1.x-dev » 7.x-2.x-dev
Status: Needs work » Postponed

@fago: Would this work out of the box in 7.x with #372743: Body and teaser as fields? Is there a standard 'populate a field' action in 7.x-2.x, and would it be extensible for additionally supporting an input filter selection?

fago’s picture

Category: feature » bug
Status: Postponed » Active

Yep, that's basically supported but still 7.x-2.x misses an input form for the "text_formatted" data type.

fago’s picture

Category: bug » task
mitchell’s picture

Title: Action: Set content body » Add input form for the "text_formatted" data type
Cyrandir’s picture

+1 to getting this working. Any kind of timeline?

fago’s picture

Status: Active » Fixed

I've just implemented that. Committed. Note that you have to install the latest entity metadata module for this to work.

Status: Fixed » Closed (fixed)

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

Flying Drupalist’s picture

No chance of getting this in 6.x?

Michsk’s picture

fago just stated this got commited... @19

Flying Drupalist’s picture

Yes but the issue is on 7.x-2.x-dev