Skip to content

[Components] wordpress_com #15127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pipedream-component-development opened this issue Jan 2, 2025 · 15 comments · Fixed by #16461 or #16500
Closed

[Components] wordpress_com #15127

pipedream-component-development opened this issue Jan 2, 2025 · 15 comments · Fixed by #16461 or #16500
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@pipedream-component-development
Copy link
Collaborator

pipedream-component-development commented Jan 2, 2025

wordpress_com

URLs

Polling Sources

new-post

Description

Emit new event when a new post is published on the site. Required props: site ID or URL. Optional props: post type (e.g., blog post, page).

new-comment

Description

Emit new event when a new comment is added to any post. Required props: site ID or URL. Optional props: post ID to filter comments for a specific post.

new-follower

Description

Emit new event when a new follower subscribes to the site's blog. Required props: site ID or URL. No optional props.

Actions

create-post

Description

Create a new post on the site. Required props: site ID or URL, post title, content. Optional props: post status (draft, published), post categories, tags.

upload-media

Description

Upload a media file to the site's library. Required props: site ID or URL, media file (binary or URL). Optional props: media title, description.

delete-post

Description

Delete an existing post from the site. Required props: site ID or URL, post ID. No optional props.

@vunguyenhung vunguyenhung added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Jan 6, 2025
@michelle0927 michelle0927 moved this from To Do to Ready for PR Review in Component (Source and Action) Backlog Apr 28, 2025
@michelle0927 michelle0927 moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Apr 28, 2025
@michelle0927 michelle0927 moved this from In Review to Ready for QA in Component (Source and Action) Backlog Apr 28, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to Ready for Release in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from Ready for Release to In QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog Apr 29, 2025
@github-project-automation github-project-automation bot moved this from Ready for Release to Done in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung reopened this Apr 29, 2025
@vunguyenhung
Copy link
Collaborator

Hi @michelle0927 @SokolovskyiK, the ticket was moved to ready for release due to an automation bug on my side. It is actually changes required. Could you check the test report below and create a new PR to fix them?

https://vunguyenhung.notion.site/Components-wordpress_com-1e3bf548bb5e815dba87d480e611b16d?pvs=4

@vunguyenhung vunguyenhung moved this from Done to Changes Required in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung
Copy link
Collaborator

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/Components-wordpress_com-1e3bf548bb5e815dba87d480e611b16d

@SokolovskyiK
Copy link
Contributor

@vunguyenhung
Hi. No problem.

@SokolovskyiK
Copy link
Contributor

SokolovskyiK commented Apr 29, 2025

Hi @michelle0927 @michelle0927

I tested the sources locally and then via pd dev, but the problem is that I only have 10 tries per day, so it's difficult to test everything thoroughly. Is there some kind of dev mode or something where I can increase the number of tries? =)

@dannyroosevelt
Copy link
Collaborator

@SokolovskyiK definitely yes — we really appreciate all your contributions! DM me on Slack and we'll get you set up:
https://join.slack.com/t/pipedream-users/shared_invite/zt-2mkow7144-~gqAxbfCe6L4hzhY54pNSw

@michelle0927
Copy link
Collaborator

Hi @SokolovskyiK, sorry for merging that first PR too soon. When this one is ready for a code review, would you mind moving it from "Changes Required" to "Ready for PR Review" (top right-hand side of this page)?

@SokolovskyiK
Copy link
Contributor

Hi @michelle0927. No problem!
As for moving it to "Ready for PR Review", I don’t mind doing that, but I don’t have permission. =)

Image
Or will I be able to do it once it's marked as "Ready for a code review"?

@michelle0927 michelle0927 moved this from Changes Required to Ready for PR Review in Component (Source and Action) Backlog May 3, 2025
@michelle0927
Copy link
Collaborator

@SokolovskyiK Sorry, didn't realize you didn't have permission! Moved it to Ready for PR Review!

@michelle0927 michelle0927 moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog May 3, 2025
@SokolovskyiK
Copy link
Contributor

@michelle0927 Great. Thanks

@michelle0927 michelle0927 moved this from In Review to Ready for QA in Component (Source and Action) Backlog May 3, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog May 5, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for QA in Component (Source and Action) Backlog May 5, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog May 5, 2025
@vunguyenhung vunguyenhung moved this from In QA to Changes Required in Component (Source and Action) Backlog May 5, 2025
@vunguyenhung
Copy link
Collaborator

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/Components-wordpress_com-1e3bf548bb5e815dba87d480e611b16d

@SokolovskyiK
Copy link
Contributor

Hi @vunguyenhung
The link to the test report contains problems that I already fixed (at least I think so).
The report was edited on May 5, 2025, at 7:09 AM.
So, as I understand, I need to fix only the issues you wrote here: #16500?
Please correct me if I'm wrong. Thanks.

@vunguyenhung
Copy link
Collaborator

Hey @SokolovskyiK, yeah the test report is not updated. You can fix only the comments I made. Please ignore the test report for now.

Thank you

@michelle0927 michelle0927 moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog May 6, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog May 7, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for QA in Component (Source and Action) Backlog May 7, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog May 7, 2025
@vunguyenhung vunguyenhung moved this from In QA to Changes Required in Component (Source and Action) Backlog May 7, 2025
@vunguyenhung
Copy link
Collaborator

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/Components-wordpress_com-1e3bf548bb5e815dba87d480e611b16d

@SokolovskyiK
Copy link
Contributor

Hi @vunguyenhung

I fixed the subscriber issue.
Please note:
I tested everything and it worked fine for me, so I was confused why the test failed on your side.
Then I looked closer at your screenshot and saw the "Add Subscriber" button.

That’s when I realized that during my tests, I created a new WP account and clicked the Subscribe button on the website.
Turns out WordPress treats those who click Subscribe and those added manually in the dashboard as two different types — they even get totally different IDs (like 908324936 for manual and 265762416 for Subscribe button).

And the API only fetches one type at a time (email or wpcom).
So I added a prop that lets the user choose which type of subscriber to track. By default, it tracks wpcom (those who clicked Subscribe).

@michelle0927 michelle0927 moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog May 7, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog May 8, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog May 8, 2025
@vunguyenhung
Copy link
Collaborator

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Components-wordpress_com-1e3bf548bb5e815dba87d480e611b16d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee
5 participants