Closed
Bug 433449
Opened 17 years ago
Closed 17 years ago
Last-updated date reads "Updated December 31, 1969" on /browse/ pages
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
3.4.2
People
(Reporter: stephend, Assigned: wenzel)
References
()
Details
Attachments
(1 file)
|
844 bytes,
patch
|
morgamic
:
review+
|
Details | Diff | Splinter Review |
Steps to Reproduce:
1. Load https://preview.addons.mozilla.org/en-US/firefox/browse/type:1/cat:5
2. Look at the date after the add-on's description
3. Now click through (we'll use FlashGot: https://preview.addons.mozilla.org/en-US/firefox/addon/220) to its details page.
Actual Results:
The /browse/ page (step 2) reads, "Updated December 31, 1969"
Expected Results:
As when you click through to its details page (https://preview.addons.mozilla.org/en-US/firefox/addon/220), reads, "Updated April 4, 2008" (or something similar)
| Reporter | ||
Comment 1•17 years ago
|
||
(This is from bug 425527, btw...)
| Reporter | ||
Updated•17 years ago
|
Target Milestone: --- → 3.4.2
| Assignee | ||
Comment 2•17 years ago
|
||
The problem is that the fix from bug 425527 does not use the correct date field: it uses $version[0]['created'], no matter if that version even exists or what status it has.
In the Addon model, getAddonsByCategory() generates a "datestatuschanged" field that should be used where available.
Comment 3•17 years ago
|
||
I think the problem was that the category landing page is it's own template and that variable wasn't getting passed in. r13094 fixes this for the category landing page, theme landing page and the search engine page.
I think this bug is fixed, but holding off marking it that way till wenzel has a change to comment.
Assignee: nobody → clouserw
| Assignee | ||
Comment 4•17 years ago
|
||
Ah yeah, I think that fixed it; however it does not address my points in comment 2, which arguably aren't this bug. I may file another bug or fix them here, hmmm.
| Assignee | ||
Comment 5•17 years ago
|
||
This patch will fix the "datestatuschanged" issue.
I will fix the "what status does the latest version even have?" problem as part of bug 404664 (this may not sound obvious, but I am quite sure it's the same problem).
Attachment #320771 -
Flags: review?(clouserw)
Comment 6•17 years ago
|
||
Shouldn't we check for that array key in each of the templates then?
| Assignee | ||
Comment 7•17 years ago
|
||
Not sure if any other templates use that array key: it is generated by the Addon model's getAddonsByCategory() only when queried for a list of recently updated add-ons.
Comment 8•17 years ago
|
||
Comment on attachment 320771 [details] [diff] [review]
Using "datestatuschanged" in listitems
wfm - ship it.
Attachment #320771 -
Flags: review?(clouserw) → review+
Comment 9•17 years ago
|
||
(it works to fix this specific bug)
| Assignee | ||
Updated•17 years ago
|
Updated•17 years ago
|
Keywords: push-needed
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•