Closed (works as designed)
Project:
Mailhandler
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
14 Jul 2005 at 15:31 UTC
Updated:
14 Jul 2005 at 15:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
sethcohn commentedbump.
Just got bit with this...
What's a good fix?
is the wrong thing, so what's the right thing, assuming a textarea exists in the flexinode?
I tried this:
(flexinode_2 is the text area in that flexinode I want to populate.
Didn't work... what will?
Comment #2
sethcohn commentedRefiling this against Mailhandler.... it's not really a flexinode problem, as mailhandler needs to handle the special case of flexinodes better.
Comment #3
moshe weitzman commentednot a mailhandler issue. you solve this by using Commands feature of mailhandler and creating a flexinode_mailhandler() function.
Comment #4
sethcohn commentedfigured out why the above code didn't work:
you must also have set ctype_id (=2 e.g.) as well as node type (flexinode-2 e.g) in the mailhandler configuration.
That likely IS something flexinode should fix, and I'll file a bug against it. This bug is still valid: mailhandler needs to allow pointing 'body' content to a different field if desired. I'll submit a patch to do add a command to do so.
Comment #5
sethcohn commentedPatch enclosed...
Command syntax:
bodyfield: new fieldname to copy body contents into.
example:
This will copy $node->body's content to $node->flexinode_2, allowing population of the desired textarea for example.
This patch does not clear $node->body's content (only copy it to the new field), I can't see any reason to at this time.
Comment #6
moshe weitzman commentedmodules that need to copy body text can do so in the mailhandler hook. please look at that hook and state why the hook isn't sufficient when filing these integration issues.