Closed
Bug 182377
Opened 22 years ago
Closed 22 years ago
composer incorrectly publishes files into one flat directory
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: dranch, Unassigned)
Details
(Keywords: qawanted)
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021126 When publishing HTML and the associately image files (.jpgs), the publish process uploads the various images from a directory heirarchy (www/vaction, /www/family, etc) into the master directory (flat - no heirarchy). Also, the published HTML file for the index.html file still reflects the heirarchy thus everything is now giving broken links, etc. Reproducible: Always Steps to Reproduce: 1. create a www site with a heirarchy (multiple subdirectories) 2. publish it 3. few the resulting published WWW site - all heirarchy files are flattened into one directory Actual Results: all heirarchy files are flattened into one directory Expected Results: Mozilla should: 1. see if the files should have been copied over instead of blindly doing it 2. create the required subdirectories to put the files in their proper place I tried this with Mozilla 1.1 and was going to post a bug but then saw that 1.2 was out. I hoped this was a known bug. It might be similar to Bugzilla id: 142157 but it's not clear.
Comment 1•22 years ago
|
||
How did you fill out the publish dialog? Did you check the box for "include images and other files"? If so, which radio button did you use? It sounds like you want to specify "Use this site subdirectory" and fill it in with either "vacation" or "family" or similar. Please try again with a newer build (1.3alpha?).
Keywords: qawanted
Summary: composer incorrectly publishes files into one flat directory → composer incorrectly publishes files into one flat directory
Comment 3•22 years ago
|
||
resolving as invalid (lacks enough details to reproduce problem)
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•