Skip to content

Conversation

iMattPro
Copy link
Member

@iMattPro iMattPro commented Sep 30, 2025

@DavidIQ and @marc1706 This PR would be in addition to phpbb/phpbb#6873

This PR updates the composer repo build for phpBB4’s extension catalog so that only extensions marked as supporting the phpBB 4 branch get included. Basically, it cuts down the risk of presenting extensions that aren’t submitted & validated for phpBB4 and could break boards.

@DavidIQ
Copy link
Member

DavidIQ commented Sep 30, 2025

I thought these changes weren't going to be needed. Not sure this will be ok. Like I said there is at least one extension that makes use of this data so not sure we want to break their stuff.

@iMattPro
Copy link
Member Author

Until some user submits an extension that is for phpBB3, and not compatible with phpBB4, yet they updated their composer installers to 2.0 for some reason. Then their extension could appear in phpBB4 forums as installable.

@DavidIQ
Copy link
Member

DavidIQ commented Oct 1, 2025

This is the extension I'm referring to that is referencing the composer repo in Titania: https://github.com/BoardTools/upload/blob/develop-3.2.0/includes/sources/extensions_list.php#L18

These changes would essentially break this extension. Whether or not it is still active is another story.

@iMattPro iMattPro marked this pull request as draft October 1, 2025 13:44
@iMattPro
Copy link
Member Author

iMattPro commented Oct 1, 2025

This is the extension I'm referring to that is referencing the composer repo in Titania: https://github.com/BoardTools/upload/blob/develop-3.2.0/includes/sources/extensions_list.php#L18

These changes would essentially break this extension. Whether or not it is still active is another story.

Ah I forgot about that extension.

OK, here's an alternative approach then. Let's generate a second list that is for phpBB4 branch submissions only, in addition to the standard all extensions list.

This way, the extension(s) currently using our repository list can continue unaffected, and in phpBB4's extension catalog we instead have it download its repository packages from the phpbb4 only branch, aka: /db/composer/packages-40.json

@iMattPro
Copy link
Member Author

iMattPro commented Oct 1, 2025

I added a new URL path so phpBB would need to update it's composer repository config setting to point to:
https://www.phpbb.com/customise/db/composer/40/ to only load extensions submitted to CDB that are supprt the 4.0.x branch, ie:

Screenshot 2025-09-30 at 4 47 57 PM

What gets generated when the repo-rebuilder runs, looks somewhat like this (regular packages.json files for all extensions, and 40/ sub-dir with json files just for phpBB4 extensions:

Screenshot 2025-10-02 at 12 46 27 PM

@iMattPro iMattPro force-pushed the prep-phpbb4-branch-releases branch from 0f6c80f to ae52a12 Compare October 2, 2025 19:45
@iMattPro iMattPro marked this pull request as ready for review October 2, 2025 21:46
@iMattPro iMattPro changed the title Composer repository should only show phpbb4 branch releases Composer repository generate a phpbb4 branch releases Oct 3, 2025
@iMattPro iMattPro changed the title Composer repository generate a phpbb4 branch releases Composer repository builder should also make a phpBB4 only packages.json Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants