Closed Bug 483817 Opened 16 years ago Closed 16 years ago

Seagull v2 persona disappears after a day (daily update applies incorrect values in its index_1.json)

Categories

(Mozilla Labs Graveyard :: Personas Plus, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: myk, Assigned: telliott)

References

()

Details

The Seagull v2 persona (in the Nature category) lacks an index_1.json file, so users who select it have it automatically removed by the code that checks daily to see if the persona is still available: http://www.getpersonas.com/store/4/8/487/index_1.json
We have an algorithm mismatch. The persona path is based on the last two digits of the persona. Seagull v2 is at http://www.getpersonas.com/store/8/7/487/index_1.json
Assignee: cbeard → myk
Priority: -- → P1
Hmm, indeed, sorry about that. The algorithm mismatch was actually in my head, as the extension is correctly using the last two digits. The actual issue I was investigating when I reported this issue is that the Seagull v2 is disappearing from its users' browsers after a day. I've just taken a closer look, and it turns out that the problem is with the content of that persona's index_1.json file, not its location. The Seagull v2 record in the gallery looks like this: {"id":"487","name":"Seagull v2","accentcolor":"#5e869f","textcolor":"#000000","header":"8/7/487/seagull2_header.jpg","footer":"8/7/487/seagull2_footer.jpg"} The Seagull v2 record in its index_1.json file, on the other hand, looks like this: {"id":"487","name":"Seagull v2","accentcolor":"5f6877","textcolor":"000000","header":"8/7/487/Seagull2_header.jpg","footer":"8/7/487/Seagull2_footer.jpg"} The difference in capitalization in the names of the header and footer files is presumably why the persona vanishes after the daily update. I've corrected the summary and reassigned it back to Toby, since this again looks like a server issue. Tag, you're it!
Assignee: myk → telliott
Summary: Seagull v2 persona lacks index_1.json file → Seagull v2 persona disappears after a day (daily update applies incorrect values in its index_1.json)
crazy. My belief is that the only way this could happen would be for the user to upload an edit with a differently capitalized username. At the moment, those changes don't get passed into the index_1 local file (which is the core bug). I regenerated all the personas local files, and that should get us through to the new version. Will make sure the new version updates correctly on edits.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.