Closed
Bug 145265
Opened 22 years ago
Closed 14 years ago
Need ability to select files to upload during publish (N4.x parity)
Categories
(SeaMonkey :: Composer, enhancement)
SeaMonkey
Composer
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: kinmoz, Unassigned)
References
Details
(Keywords: helpwanted, Whiteboard: publish)
Filing this bug I received through email on behalf of phookie@xmission.com. ---- The Composer in the 4.x versions allowed you to select the files from the list shown to upload. This new Composer appears to simply upload all (checked) or none (unchecked ) we have an image directory two levels up that contain all the site wide images (banner, etc.) at the level of the page I am editing we have an image directory that is common to all, e.g., Wetlands. I need the ability to upload images to the image directory at the same level as the page I am editing (../images) without uploading the images associated with the site-wide images directory (/images). it was great to allow the user to pick the directory to load images to, 4.x version didn't offer this. However, I find myself doing what i did with the 4.x version of Composer and that is, creating a dummy html file, editing that in the directory where the images are, and uploading the dummy html file and all images to the images directory. needless to say, my users would never use this very bad workaround that i use. many moons ago, Beth E. said something about using the side bar to drag and drop files between the local computer and the web server. is that ever going to happen?? Anyway, having a list of files to pick from for upload is really a neccessity in my case. Thanks... jerry
Comment 1•22 years ago
|
||
future, helpwanted, etc.
Severity: normal → enhancement
Keywords: 4xp,
helpwanted
Whiteboard: publish
Target Milestone: --- → Future
*** Bug 169750 has been marked as a duplicate of this bug. ***
*** Bug 149416 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: cmanske → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
Comment 5•15 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 6•14 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•