When specifying a folder that doesn't exist in the publish settings Mozilla gives an error message instead of just creating the folder specified. Steps to reproduce: 1. Create or edit a page in composer 2. Choose file - publish as 3. Put a folder name in the 'site subdirectory' field that does not exist on the server. 4. Publish. Expected results: A new folder is created, and the file is published. Actual results: '550 no such file or directory'.

--> cmanske

Please supply publishing details: Publish url at a minimum. HTTP publishing *will* create subdirectories, so this is most likely FTP.

Sorry, didn't know you could publish via http. This is FTP as you assumed. Let me know if you need more details or testing.

I'd say this is a duplicate of bug 64214. (If bug 64214 is resolved without addressing this bug then we should reopen this issue.) *** This bug has been marked as a duplicate of 64214 ***

I think it would be better to keep this bug open so we are sure that when mkdir is implemented by fixing bug 64214, that we also do the additional work to automatically create the subdirectory during FTP uploading. It's not clear that that task is part of 64214. Actually, I'd prefer if we would first ask the user if that's what they want first. e.g., "Subdirector foo does not exist at this site. Create it now?" This would be a better UI since not finding a subdirectory may be caused by a typing error by the user, so asking user avoids that kind of misconception.

I like this "Composer bug depends on underlying FTP bug" structure. It will make life easy fro sujay and I. Can someone comment about the status of this feature, as of Mozilla 1.0 (works/not)?

Both bug 64214 and this bug are set to Future. There are no plans to implement these for the 1.0 timeframe (that I am aware of).

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

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