Should not rely on Navigation._publishTraverse() to have objects appended to request.traversed_objects

Bug #423898 reported by Guilherme Salgado
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Guilherme Salgado

Bug Description

Since it's only Navigation._publishTraverse() that adds stuff to request.traversed_objects, instances of any classes for which there's no Navigation defined will not be added to traversed_objects and thus break our breadcrumbs.

Revision history for this message
Guilherme Salgado (salgado) wrote :

I've asked Francis if there's any reason why we do things this way, and here's what he said:
<flacoste> salgado: no particular reason, might be a good idea to put it into the request/publiation traversal hook

Changed in launchpad-foundations:
assignee: Guilherme Salgado (salgado) → nobody
importance: High → Undecided
milestone: 3.0 → none
Changed in launchpad-foundations:
assignee: nobody → Guilherme Salgado (salgado)
milestone: none → 3.0
status: Triaged → In Progress
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in launchpad-foundations:
status: In Progress → Fix Committed
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.