Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Currently, when a node revision is saved, even if the node is unpublished, and a twitter field is selected to send a tweet, the tweet is sent immediately. It would be a desired behavior to only send the tweet when the node revision is published.
The current schema for the field_data_field_post_to_twitter and field_revision_field_post_to_twitter (or whatever you call your field) does not include the actual tweet value (before token substitution), which prevents this feature from being possible. I think also adding a column here for "tweeted" or "tweet_sent" would also be required in order to store whether a tweet that was attached as a field to the node was actually processed. I would think that you would only want the tweet to go out once, although it would be possible to add an additional tweet if there was another revision that was added to the node, which could be scheduled to be published later.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | twitter-n2461937-3.patch | 7.3 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaI'll work on this after getting 6.0 out the door.
Comment #2
DamienMcKennaAlso #2557783: The field name and hook_field_schema are out of sync seems to be related - the field doesn't seem to actually store any data.
Comment #3
DamienMcKennaI guess I'm doing this now :)
This improves the form, removes twitter_post_field_attach_form entirely by moving the account selector into twitter_post_field_widget_form, and unchecks the status checkbox if the entity was previously published ($element['#element']->status).
Comment #4
DamienMcKennaCommitted.