Closed
Bug 402140
Opened 18 years ago
Closed 18 years ago
Add new add-ons image for start page snippets
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: drolnitzky, Assigned: reed)
Details
Attachments
(1 file)
|
2.21 KB,
image/png
|
Details |
New content has committed to:
start-snippets/en/snippet-1.html
Also have attached a new icon to go with this snippet. It should go in the "images" directory.
| Reporter | ||
Comment 1•18 years ago
|
||
Comment 2•18 years ago
|
||
Reassigning to Justin. I think all of this needs to be committed first.
Assignee: server-ops → fligtar
Comment 3•18 years ago
|
||
Re-assigning to morgamic because I know nothing about the start page system.
Assignee: fligtar → morgamic
the full url for the snippet is:
http://www.mozilla.org/start-snippets/en/snippet-1.html
no need to commit above, it's all taken care of.
david needs help uploading the attached icon to:
http://www.mozilla.org/start-snippets/images
Assignee: morgamic → nobody
Component: Server Operations: Web Content Push → www.mozilla.org
QA Contact: justin → www-mozilla-org
| Assignee | ||
Comment 5•18 years ago
|
||
Thank you, pkim, for moving the bug to the proper component where it can be appropriately fixed, as IT has nothing directly to do with the content of the (www.mozilla.com/www.mozilla.org) websites.
Assignee: nobody → reed
OS: Other → All
Summary: Swap out operation firefox start page snippet to add-ons snippet → Add new add-ons image for start page snippets
| Reporter | ||
Comment 6•18 years ago
|
||
Point taken Reed. Will make sure not to file in IT next time.
| Assignee | ||
Comment 7•18 years ago
|
||
RCS file: /www/mozilla-org/html/start-snippets/images/addons-ico.png,v
done
Checking in addons-ico.png;
/www/mozilla-org/html/start-snippets/images/addons-ico.png,v <-- addons-ico.png
initial revision: 1.1
done
Something seems to be broken with the building of www.mozilla.org, so changes aren't showing up as they should. I'll file an IT bug on getting that fixed.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 8•18 years ago
|
||
Also, I noticed that snippet-2.html has the same text as snippet-1.html, but it uses a URL without Urchin tracking, and it uses light.gif instead of the new addons png. Is this correct?
| Reporter | ||
Comment 9•18 years ago
|
||
Google was not rotating snippet 2 because of a 404 error (due to a typo in one of the url's). I've fixed the typo in case we'd like to put it into rotation, but will just swap out for operation firefox for now. I'm going to put in some new content for #2 once we have some supporting landing pages up on our side.
| Assignee | ||
Comment 10•18 years ago
|
||
(In reply to comment #7)
> Something seems to be broken with the building of www.mozilla.org, so changes
> aren't showing up as they should. I'll file an IT bug on getting that fixed.
Filed bug 402174 on this issue.
Updated•18 years ago
|
Group: infra
| Reporter | ||
Comment 11•18 years ago
|
||
I checked the update snippet:
http://www.mozilla.org/start-snippets/en/snippet-1.html
No image appears. Is there a way we can ensure that this shows up before we submit to Google?
| Assignee | ||
Comment 12•18 years ago
|
||
(In reply to comment #11)
> I checked the update snippet:
> http://www.mozilla.org/start-snippets/en/snippet-1.html
>
> No image appears. Is there a way we can ensure that this shows up before we
> submit to Google?
That seems normal. Looking at all the snippets, the images do not show up because the snippets specify the wrong location for the images (my understanding is that this is on purpose?). For example, /en/snippet-1.html uses "images/addons-ico.png" for the image source, but the actual location is "../images/addons-ico.png". You can see the image at its current location at http://www.mozilla.org/start-snippets/images/addons-ico.png.
Updated•17 years ago
|
Product: mozilla.org → Websites
Updated•13 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•