Blog Updated Notification On Wrong Page #30

Closed
opened 2024-01-14 14:33:55 -06:00 by jimmyb · 3 comments
Owner

Originally submitted by HyperDebtRay

The success notification is displayed on a game entry page after you confirm a blog entry update and then click on a game within the gamer feed.

Possible Reproduction:

Possible Reproduction:

  1. Go to a blog entry you created
  2. Edit the entry and hit Save/Update
  3. Click on any game in the gamer feed
    3b. Alternatively try quickly clicking the game link in gamer feed within a second or two after update
  4. Observe the blog updated notification in the game entry page
**Originally submitted by HyperDebtRay** The success notification is displayed on a game entry page after you confirm a blog entry update and then click on a game within the gamer feed. Possible Reproduction: Possible Reproduction: 1. Go to a blog entry you created 2. Edit the entry and hit Save/Update 3. Click on any game in the gamer feed 3b. Alternatively try quickly clicking the game link in gamer feed within a second or two after update 4. Observe the blog updated notification in the game entry page
Author
Owner

This will pretty much happen on any page which checks for these types of cookies.

This will pretty much happen on any page which checks for these types of cookies.
Member

Checked against the current Laravel codebase and I can't reproduce this as a live issue anymore.

The old report/comment point at the previous cookie-based notification behavior, but the current blog flow flashes a scoped Laravel session key instead:

  • Blog create/update/delete actions use in .
  • Only the blog index/show views render .
  • The game page renders and does not read .
  • Repo search did not find a current cookie-based global notification path for this blog success message.

Verification:
.

Tests: 1 passed (5 assertions)
Duration: 1.62s passes. The full run had one unrelated existing profile stats HTML assertion failure at line 533, outside this notification path.

Closing this as stale / no longer reproducible in the current site.

Checked against the current Laravel codebase and I can't reproduce this as a live issue anymore. The old report/comment point at the previous cookie-based notification behavior, but the current blog flow flashes a scoped Laravel session key instead: - Blog create/update/delete actions use in . - Only the blog index/show views render . - The game page renders and does not read . - Repo search did not find a current cookie-based global notification path for this blog success message. Verification: . Tests: 1 passed (5 assertions) Duration: 1.62s passes. The full run had one unrelated existing profile stats HTML assertion failure at line 533, outside this notification path. Closing this as stale / no longer reproducible in the current site.
Codex closed this issue 2026-06-03 17:57:53 -05:00
Member

Clean verification note for the closeout: checked against the current Laravel codebase and this no longer appears reproducible. The old report described cookie-based notification leakage. Current blog create, update, and delete actions flash the scoped Laravel session key named blog_status from BlogEntryController. Only the blog index and blog show views render that key. The game page renders game_comment_status and does not read blog_status. Repo search did not find a current cookie-based global notification path for this blog success message. Targeted verification passed with php artisan test --compact tests/Feature/BlogTest.php --filter="draft publishing records one public blog activity update". A full BlogTest run had one unrelated existing profile stats HTML assertion failure at tests/Feature/BlogTest.php line 533, outside this notification path. Closing remains stale / no longer reproducible.

Clean verification note for the closeout: checked against the current Laravel codebase and this no longer appears reproducible. The old report described cookie-based notification leakage. Current blog create, update, and delete actions flash the scoped Laravel session key named blog_status from BlogEntryController. Only the blog index and blog show views render that key. The game page renders game_comment_status and does not read blog_status. Repo search did not find a current cookie-based global notification path for this blog success message. Targeted verification passed with php artisan test --compact tests/Feature/BlogTest.php --filter="draft publishing records one public blog activity update". A full BlogTest run had one unrelated existing profile stats HTML assertion failure at tests/Feature/BlogTest.php line 533, outside this notification path. Closing remains stale / no longer reproducible.
jimmyb self-assigned this 2026-06-03 17:58:57 -05:00
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
MyVideoGameList/myvideogamelist.com#30
No description provided.