Closed Bug 274858 Opened 20 years ago Closed 20 years ago

Add new extension breaks after extension upload

Categories

(addons.mozilla.org Graveyard :: Developer Pages, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: wolf)

Details

Attachments

(2 files)

Steps to reproduce:

1.  Log into developers section of UMO (I logged in as paul@ctomer.com).
2.  Click on "Add new extension"
3.  "Browse" to local file: translate-0.6.0.6-fx.xpi  (the file can be
downloaded here http://ctomer.com/extensions/translate/translate-0.6.0.6-fx.xpi)
4.  Click on "Next"

The following erros appear:
Warning:
move_uploaded_file(/opt/update-beta/files/temp/translate-0.6.0.6-fx.xpi): failed
to open stream: No such file or directory in
/opt/update-beta/developers/additem.php on line 55

Warning: move_uploaded_file(): Unable to move '/tmp/phpejONtW' to
'/opt/update-beta/files/temp/translate-0.6.0.6-fx.xpi' in
/opt/update-beta/developers/additem.php on line 55

I've also attached a screenshot.
Attached image Additem errors
Attachment #168850 - Attachment description: Additem erros → Additem errors
Confirming.

Looks like some part of the add chain still uses a hardcoded path. doh.
Severity: normal → blocker
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → 1.0
Fix hardcoded path to $websitepath/files to use $repositorypath variable.
(When testing, never use the old path as your $repositorypath variable. doh)
Patch checked in.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Looks good, works as expected now.
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: