Blog Updated Notification On Wrong Page #30
Labels
No labels
automated
code-quality
component: admin dashboard
component: backend
component: billing
component: content management
component: faqs
component: game genres
component: game lists
component: game reviews
component: game search
component: games
component: internal notifications
component: platforms
component: security
component: tests
component: user api
component: user badges
component: user blogs
component: user consoles
component: user favorites
component: user friends
component: user notifications
component: user profiles
component: user site notifications
component: user wishlists
component: web design
dependencies
php
priority
high
priority
low
priority
medium
security-hotspot
source: codex
source: sonarqube
status
awaiting feedback
status
backlog
status
done
status
in progress
status
in queue
status
in review
status
needs codex review
status
needs investigation
status
wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MyVideoGameList/myvideogamelist.com#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
3b. Alternatively try quickly clicking the game link in gamer feed within a second or two after update
This will pretty much happen on any page which checks for these types of cookies.
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:
Verification:
[90;1m.[39;22m
[90mTests:[39m [32;1m1 passed[39;22m[90m (5 assertions)[39m
[90mDuration:[39m [39m1.62s[39m 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.
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.