Computed Field and Auto Node Title
clarkburbidge - February 7, 2009 - 23:41
| Project: | Computed Field |
| Version: | 6.x-1.0-beta2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I'm using computed field to generate a field used in the auto node title. I have to edit the node twice to get the correct title to show up.
1. Is there any way to get the computed field to "compute" a couple of times so the data is there?
2. Is there a way to get the computed field to "compute" before the auto node title?
#1
How do you get the computed field's value into the node title? In my setup, computed field does not expose it's values as token, so there's no replacement pattern I could enter for automatic title generation.
Thanks & greetings,
-asb
#2
All my cck fields are available as tokens. I don't know what I did to get it that way. I thought that was standard.
#3
While this response may be too late for you, I think your problem may be related to this:
#414088: computed_field_field should compute on $op='presave'
while I'll be looking into here...
#4
This is still and issue for me. I'm not sure if 'presave" would fix the issue. Currently I have a views bulk operation that I run occasionally to band aid the issue. I'd love to see it fixed, but I think it is more the way I have it set up with a nested computed CCK fields as one of the tokens for my auto node title. Thanks for info and I'll be following the results!
#5
I'm sure you're right - the computation has to happen before the value is tokenised or the value can't be available.
I'd been thinking it was simply an issue with module weights?
I've been struggling with the same problem. Is it as simple as patching the module to change the operation to presave or are there other considerations?
#6
Subscribing.