In that topic, the topic says ‘Topic was published via ActivityPub on Invalid date’.
See this screenshot:
Thanks for the report, appreciate it. I see the same, we will look into it.
3개의 좋아요
@pmusaraj Could you share any relevant meta logs from Apr 3, 2:42 PM, when that post was posted? It might help determine why the post-publication behaviour, i.e. saving published at, isn’t working in some cases.
1개의 좋아요
We have a similar behavior. We can see the post being POSTed on the activity end-points and accepted but they are not shown in the different subscriber. The only issue we see (after a recent update of the plugin - we run 3.6.0.beta1-dev) Invalid date for ActivityPub post on topic.
What would be the best option for debugging this behavior? In previous version, we didn’t see that error and the posts were published on the subscribers properly.
1개의 좋아요
Oh, I added a partial fix for this in DEV: Ensure activity_pub_published_at returns a single date by pmusaraj · Pull Request #243 · discourse/discourse-activity-pub · GitHub, I think. If you rebuild your instance @adulau you should no longer see this issue.
The underlying bug isn’t fixed. In some cases, the plugin creates multiple activity_pub_published_at custom fields for the same object, which results in the serializer returning an array of dates for topic.activity_pub_published_at. Often these are the same date added twice in the array. The frontend code (Moment) doesn’t know how to interpret an array of dates and outputs invalid date. The fix above ensures the serializer always outputs a single date (without yet fixing the underlying reason for multiple custom fields).
5개의 좋아요
FYI I reported this as well some time ago in the SocialHub forum. Cross-referencing to https://socialhub.activitypub.rocks/t/topic-was-published-via-activitypub-on-invalid-date/5447
3개의 좋아요
Thanks for the fix. It indeed works now. By the way, the ActivityPub plugin is really awesome.
4개의 좋아요