[YoutubePostsTabsBridge] Rename Community→Posts to fix broken bridge

[shaunlebron]

Fixes #4604. The community tab was renamed to “posts”, causing the bridge to fail.

Context on rename: https://support.google.com/youtube/thread/321825573?hl=en

The Community tab is becoming the Posts tab: To make things clear, we’re giving the “Community” tab a new name: “Posts.” The tab will work just as it does today, just with a new name. Creators can still share updates and announcements via posts and viewers can engage by commenting on those posts like they always have!

I fixed the tab lookup, and renamed the functions, file, and references to match the new “Posts” name.

Tested locally with:

php -S 127.0.0.1:9001

Verified with:
http://localhost:9001/?action=display&bridge=YouTubePostsTabBridge&context=By+channel+ID&channel=UCLYut6IxIvx5PxwUWMXJz8g&format=html

[github-actions]

Pull request artifacts

Bridge	Context	Status
YouTubeCommunityTab	1 By channel ID (current)	❌ Bridge returned error 0! (20283) ❌ Type: ErrorException ❌ Message: Undefined property: stdClass::$header
YouTubeCommunityTab	2 By username (current)	❌ Bridge returned error 0! (20283) ❌ Type: ErrorException ❌ Message: Undefined property: stdClass::$header
YouTubePostsTab	1 By channel ID (pr)	✔️
YouTubePostsTab	2 By username (pr)	✔️

last change: Monday 2025-07-14 01:49:13

[shaunlebron]

Not sure how to fix the errors in the above comment, but they seem to work locally for me:

1. By channel ID: http://localhost:9001/?action=display&bridge=YouTubePostsTabBridge&context=By%20channel%20ID&channel=UCULkRHBdLC5ZcEQBaL0oYHQ&format=Html
2. By username: http://localhost:9001/?action=display&bridge=YouTubePostsTabBridge&context=By%20username&username=YouTubeUK&format=Html

[Mar-Koeh]

Not sure how to fix the errors in the above comment, but they seem to work locally for me:

That's from this line:

rss-bridge/bridges/YouTubeCommunityTabBridge.php

Line 75 in 354cea0

$this->feedName = $json->header->c4TabbedHeaderRenderer->title;

There, the result of extractJson is used. This function just does a preg_match for a certain piece of JSON and parses it. If the JSON-parsing fails, then there should be a different error. So it looks like JSON is successfully parsed. I had a look at it in curl. Looks good. However, there c4TabbedHeaderRenderer doesn't occur in the JSON at all. Hence, this line fails. When I looked at it, there were multiple places containing the title:

• $json->header->pageHeaderRenderer->pageTitle
• $json->metadata->channelMetadataRenderer->title
• $json->microformat->microformatDataRenderer->title

The question is why the said line didn't fail when you tried it. I have two theories:

• YouTube doesn't always output the same JSON. Might be A/B-testing. Might be the guessed device type. Might be based on your location.
• Your PHP version or config doesn't throw an error but just a warning while using NULL.

You could test this by checking whether your feed has a feedTitle.

Maybe the following line could fix it. It uses the null coalescing operator, which doesn't emit a warning but just attempts the next expression if the previous one would have been NULL.

$this->feedName = $json->header->c4TabbedHeaderRenderer->title ?? $json->header->pageHeaderRenderer->pageTitle ?? $json->metadata->channelMetadataRenderer->title ?? $json->microformat->microformatDataRenderer->title ?? '';

With this line, all currently known locations of the title would be checked and the empty string would be the fallback if none worked.

[shaunlebron]

Thanks @Mar-Koeh that seemed to work. The remaining errors are from a file that no longer exists after this PR renamed it.