captn3m0 / captn3m0/ifttt-webhook

Revert back to previous settings where "tags" field used for remote webhook url.

Open
#4 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
303
Forks
65
PR merge metrics
No merged PRs in 30d

Description

Few days ago `tags` field in WordPress is used for remote web-hook url where `body` is preserved for sending a more data to web-hook. I don't understand what is the reason for changing this.

Now that `tag` field is ignored & `body` is being used for providing remote url there is one less field to send data with.

I would prefer this as a #payload:

```
{
user: "username specified in ifttt",
password: "password specified in ifttt",
title: "title generated for the recipe in ifttt",
categories:['array','of','categories','passed'],
description:"Body of the blog post as created in ifttt recipe"
}
```

Now all my web-hooks recopies are broken. Plz fix it.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named. Start by tracing where the webhook reads the WordPress tags and body fields, then compare the current payload with the requested payload. Done means tags supplies the remote webhook URL, body remains available as post content, and existing webhook recipes receive the expected fields.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.