Visitar URL original
[3.3.x][ticket/17756] Include report IDs in new post-report notifications by bonelifer · Pull Request #7105 · phpbb/phpbb · GitHub
Skip to content

[3.3.x][ticket/17756] Include report IDs in new post-report notifications - #7105

Open
bonelifer wants to merge 2 commits into
phpbb:3.3.xfrom
bonelifer:ticket/17756
Open

bonelifer wants to merge 2 commits into
phpbb:3.3.xfrom
bonelifer:ticket/17756

Conversation

@bonelifer

Copy link
Copy Markdown
Member

New post-report notifications now retain the created report ID and include it alongside the post ID in their URLs and unread redirects. Saved links select the original report after closure or a later report; deleted reports retain the missing-report error. Legacy notification data keeps its existing URLs and inherited redirects.

MCP resolution, permissions, notification identity, and PM production code are unchanged. Master additionally converts HTML query separators for Symfony redirects.

Codex verified notification suites and post/PM HTTP lifecycle tests across seven database/driver combinations on the documented 3.3.x and 4.0 snapshots. Oracle/ODBC runs used separate driver or test-harness prerequisites, excluded here. After rebasing onto current master, Codex reran its notification suite: 43 tests and 218 assertions passed. Codex also checked changed-file coding style and whitespace. External email delivery and the expanded forum-ACL combinations were not tested.

Checklist:

  • Correct target branch for this fix.
  • Relevant tests pass with the documented database prerequisites.
  • Changed files follow phpBB coding guidelines.
  • Commit follows the ticket-based format.

Tracker ticket: https://tracker.phpbb.com/browse/PHPBB-17756


Investigated and written by Codex on behalf of William Jacoby (bonelifer).

Persist the created report ID and include it alongside the post ID in
new report notification URLs and unread redirects. Preserve the existing
URLs and inherited redirects for legacy notification data. Cover exact
report selection through closure, subsequent reports and deletion, plus
legacy URL behavior, persistence and PM report links.

PHPBB-17756
@github-actions

Copy link
Copy Markdown

The attempt to merge branch 3.3.x into master has completed after considering the changes in this PR.

  • Merge result: Conflict ❌

A separate PR will be needed to merge 3.3.x into master.

The history test leaves its second report open on the shared fixture
post. Close it after checking deletion of the original report so the
following report CAPTCHA tests can report the post.

PHPBB-17756
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.

1 participant