Closed Bug 373748 Opened 17 years ago Closed 17 years ago

Missing Some of My Addons

Categories

(addons.mozilla.org Graveyard :: Administration, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: twistermc, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: 

The preview site lists three of my addons: iPox, MidnightFox and Tinseltown.
https://preview.addons.mozilla.org/en-US/firefox/user/9138

The live site lists all six of my addons: iPox, MidnightFox, Tinseltown, HalloFF, PinkHope and yExplore.
https://addons.mozilla.org/firefox/9138/author/

The new developer control panel lists all six though.  So I'm unsure where the disconnect is.

Reproducible: Always

Steps to Reproduce:
1. Go to TwisterMc's author page in the preview release.
https://preview.addons.mozilla.org/en-US/firefox/user/9138
Actual Results:  
Only three of my addons are listed.

Expected Results:  
Should see all six.
These three are the public themes, the other three show if you select 'sandbox';
However one might expect all 6 to appear in the sandboxed view!
I don't understand how to get to the sandbox view.
Log in then click your email address at the top-right then tick the "Show sandbox" checkbox then save then you should see a link at the left of the search bar.
Thanks.
As stated above, 3 of your add-ons are in the sandbox.

https://preview.addons.mozilla.org/en-US/firefox/users/info/9138/status:1
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
To help clear this up, why are three int he sandbox? They were all live on the current addon site. I'm just confused on how the new site works.:)
Also, my iPox them isn't the same version as the main site.  Is that a bug?
Please join #addons on irc.mozilla.org for support.
Component: Add-ons → Administration
QA Contact: add-ons → administration
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.