-
Notifications
You must be signed in to change notification settings - Fork 80
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
New Posts not visible up on the Fediverse after 4.7.0/4.7.1 #1177
Comments
We had an issue with 4.7.0 because it broke the followers list. Have you re-tried it after the update to 4.7.1? |
I added the follower only after the plugin update, just as a test |
So it seems there is a delay? After a few minutes I was able to see/find my test post (https://madmolelabs.com/2025/testing-ap-plugin/) in certain cases....
I did a second test post (https://madmolelabs.com/2025/testing-ap-plugin-again/) and this is the following.....
I am able to follow with certain accounts, though they were following before and I unfollowed prior. Not sure if there caching involved there or not, but my followers list on my wordpress profile page was updating based on my unfollow and refollow. I'm unable to follow from mas.to and pixelfed.social though I'm not sure if that behavior is related to my prior issues. |
No change after 4.7.2; new posts and followers don't show up - would it be beneficial to downgrade to 4.6.0? |
Your followers now show up properly: https://chfrank.net/wordpress/wp-json/activitypub/1.0/actors/1/followers Or do you miss some? Can you check if a cron is blocking? |
These are only the three pre-4.7.X followers; the new ones are missing.
This is a hosted WordPress instance; how do I check for a blocked cron or
any other relevant log file?
…On Wed, Jan 22, 2025 at 12:28 PM Matthias Pfefferle < ***@***.***> wrote:
Your followers now show up properly:
https://chfrank.net/wordpress/wp-json/activitypub/1.0/actors/1/followers
Or do you miss some?
Can you check if a cron is blocking?
—
Reply to this email directly, view it on GitHub
<#1177 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKFZ3MQNNVIMHYJ2MPGCOCL2L56HHAVCNFSM6AAAAABVLPFZAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBWHE4DSNJXGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
🤔 ... when I unfollow and refollow your profile, my account will be removed and readded to your followers list, like it should. I could even follow you on new instances. to check the crons, you could try: https://de.wordpress.org/plugins/wp-crontrol/ |
With 4.7.3 it's working fine now - thank you!
…On Wed, Jan 22, 2025 at 1:18 PM Matthias Pfefferle ***@***.***> wrote:
🤔 ...
when I unfollow and refollow your profile, my account will be removed and
readded to your followers list, like it should. I could even follow you on
new instances.
to check the crons, you could try:
https://de.wordpress.org/plugins/wp-crontrol/
—
Reply to this email directly, view it on GitHub
<#1177 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKFZ3MTFY442J24NY3RVBRD2L6EC3AVCNFSM6AAAAABVLPFZAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBXGA4TSOBQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Quick summary
After the plugin update to 4.7.0 (or 4.7.1), new blog posts are no longer visible from the Fediverse; old posts remain available.
Steps to reproduce
When submitting a new blog post, in the past, that post became almost immediately available on the fediverse.
However, the latest blog post (https://chfrank.net/wordpress/2025/01/14/riesa/) does not show up; the previous post is the last one visible for @[email protected] (https://chaos.social/@[email protected]).
Also, sending a new follow request to the blog will succeed but won't be reflected on the blog's admin page.
It seems as if the plugin is active but disconnected from WordPress.
Site owner impact
Fewer than 20% of the total website/platform users
Severity
Moderate
What other impact(s) does this issue have?
No response
If a workaround is available, please outline it here.
No response
The text was updated successfully, but these errors were encountered: