Closed
Bug 191121
Opened 23 years ago
Closed 23 years ago
Netscape Composer 4.xx will publish but NS7 and Mozilla will not.
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mlightfo, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212
I am using the EXACT same publishing location and directory structure.
The first error I get is:
"Alert - 553 Could not determine cwdir: No such file or directory"
When I click OK on that dialog box, the error is
"Publishing Failed"
Reproducible: Always
Steps to Reproduce:
1. I edit the web page
2. I save the page
3. I click Publish on the toolbar.
Actual Results:
I am using the EXACT same publishing location and directory structure.
The first error I get is:
"Alert - 553 Could not determine cwdir: No such file or directory"
When I click OK on that dialog box, the error is
"Publishing Failed"
Expected Results:
Published the files to the web server directory
Comment 1•23 years ago
|
||
which FTP server do you use for uploading ?
Assignee: asa → composer
Component: Browser-General → Editor: Composer
QA Contact: asa → sujay
Comment 2•23 years ago
|
||
I would guess that the url being used for publishing is an ftp url and that it
is missing a '/'
for example: instead of ftp://ftp.foo.com/mydir/
you might try this: ftp://ftp.foo.com//mydir/
There is a difference from Netscape 4.x and Netscape 6/7 for ftp code. Logging
into an ftp server may root you in a different place and not necessarily at the
root so the extra slash may be needed (in some cases) if you are publishing to a
root path rather than one in the login default directory. You can confirm ftp
behavior by using the browser: ftp://me@ftp.foo.com/
Comment 3•23 years ago
|
||
Without more information I am resolving this as invalid.
Please comment here if you have more information which could help explain what
this bug is about (we can reopen the bug if it becomes valid).
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•