A site manager can configure webmentions to be sent when content is published (not only on form save)

Created on 21 March 2022, over 2 years ago

Updated 1 March 2023, over 1 year ago

Problem/Motivation

We have a setup where content is placed in a "Ready" but unpublished state, and then automatically published on a schedule.

Presently, webmentions are only

Steps to reproduce

Configure webmentions for a content type.
Create an unpublished piece of content.
Publish on cron.

Example code in a function running on cron:

  $node = Node::load($nid);
  if (meets_publish_criteria($node)) {
    // If node is already published we can skip it.
    if ($node->get('status')->value) {
      continue;
    }
    $node->moderation_state->value = 'published';
    $node->save();

The result will be no webmentions are sent.

Proposed resolution

I see two broad options:

One, use real fields rather than pseudo fields and a form alter for the webmention setting and (hidden) display. This would be the most robust and could even simplify the work of the site builder (only have to move one field to be displayed, though that would imply configuration options per instance of this field). The main change is that a content editor could save the content unpublished having checkmarked webmention target A and not target B and on programmatic publish it would only be send A, not B.

or:

Two, add another option "on publish" next to "cron" and this won't display the form fields for webmentions at all but will send to all available targets on publish.

Remaining tasks

Pick approach, if any.

User interface changes

API changes

Data model changes

✨ Feature request

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States mlncn Minneapolis, MN, USA

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇺🇸United States mlncn Minneapolis, MN, USA
We owe updates here but the approach we have intermittently been working on is https://www.drupal.org/project/social_post_controller →

This could work with https://www.drupal.org/project/activitypub → also; both modules could implement a hook to use this "real field" instead of the pseudofield approach (or conditionally do the pseudofield only if Social Post Controller is not enabled, maybe)

Again we need to write more about the approach and why but wanted to belatedly share this update.
Comment over 1 year ago →
🇧🇪Belgium swentel
fwiw, I've added scheduler integration in ActivityPub #3322886: Integrate with scheduler → - with tests

we can probably introduce that here as well - although it's been a while since I've looked that this code.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024