485263 - Default Groovy Blue persona doesn't render in browser chrome when installed from the bundle

Status: VERIFIED FIXED

(Mozilla Labs Graveyard :: Personas Plus, defect)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

Steps to Reproduce:

1. Download the bundle from http://www.getpersonas.com (http://releases.mozilla.com/personas/win32/en-US/Firefox%20Setup%203.0.7.exe) -- I used Opera 9.64 to download the bundle.
2. Install Firefox 3.0.7
3. When it does its first-run promo, look at the browser chrome and click on the fox mask to "get started"

Expected Results:

Groovy Blue persona is selected and applied by default

Actual Results:

Although it appears to be selected by default, it doesn't apply

(See screencast: http://screencast.com/t/nmrItYEzkfL)

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

Myk says to note: http://www.getpersonas.com/store/3/3/33/index_1.json is its JSON, but that:

"when you first select a persona, the extension gets its JSON record from the HTML of the gallery page or, for personas selected from the menu in the extension, from the data feed (http://www.getpersonas.com/store/index_1.json)"

Comment 2

[Myk Melez [:myk] [@mykmelez]]

Confirmed.  This is happening because the locations of the Groovy Blue header and footer images have changed since we shipped 1.0rc1 with Groovy Blue as the default persona.  1.0rc1 refers to those files in the following locations:

  header: 3/3/33/tbox-groovy_blue.jpg
  footer: 3/3/33/stbar-groovy_blue.jpg

But they're now located at:

  header: 3/3/33/groovy_blue_header.jpg
  footer: 3/3/33/groovyblue_footer100.jpg

We could respin, but I suspect that a server-side fix would be easier.  cc:ing Toby for his thoughts on what that fix would be (reupload the images with their original names?).

Comment 3

[Suneel]

if another option is to assign another default -- one whose files remained in the same spot before and after 1.0rc1 was spun -- we can find another design that meets our needs.

Comment 4

[Toby Elliott [:telliott]]

just rename the two image files to the originals, edit the persona to upload them, approve the edit, and it should fix itself.

Comment 5

[Myk Melez [:myk] [@mykmelez]]

(In reply to comment #3)
> if another option is to assign another default -- one whose files remained in
> the same spot before and after 1.0rc1 was spun -- we can find another design
> that meets our needs.

That wouldn't work, as we'd have to respin the extension to use that persona instead.

Comment 6

[Carsten Book [:Tomcat]]

(In reply to comment #5)
> We could respin, but I suspect that a server-side fix would be easier.  cc:ing
> Toby for his thoughts on what that fix would be (reupload the images with their
> original names?).

I have some problems to understand the respin idea here. I did a test with the bundle and its fine when the hostfile points with personas etc to stage, but it fails on the live sites. So i think that a we should fix the websites then, because its working on stage ?

Comment 7

[Toby Elliott [:telliott]]

The revised-named files were never uploaded to staging. Thus, they still have the old names (and old problems).

Comment 8

[Suneel]

uploaded under the original names. files are awaiting approval.

Comment 9

[Suneel]

files approved.

Comment 10

[Myk Melez [:myk] [@mykmelez]]

Suneel's renamed files have made it out to the servers, and Groovy Blue now shows up correctly by default when you first start the bundle.

Comment 11

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #10)
> Suneel's renamed files have made it out to the servers, and Groovy Blue now
> shows up correctly by default when you first start the bundle.

Verified FIXED; thanks for the quick turnaround!