After publishing, composer forgets page's local file name



14 years ago
7 years ago


(Reporter: nelson, Unassigned)


Firefox Tracking Flags

(Not tracked)


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927

After composing a page, I save it, and then publish it.  Then, I often
choose to make additional edits to the page, and then save it again,
and then publish it again.

The problem is that after I have published the page, composer forgets 
the local file name of the page I am composing.  So, after publishing
the page, and then editing it some more, when I click Save to save it,
Composer asks me to choose the name of the file, using a Save-As like
dialog.  Given that I have not closed the composer window, and am still
composing the same page as before, composer should not forget this info.

Then, if I choose the same file name as previously used, it asks me if 
I want to replace the file.  This is all a waste of time.

Reproducible: Always
Steps to Reproduce:
1. Compose page,
2, save it.
3. publish it
4. edit it some more in the same composer window as step 1 above,
5. press Save again

Actual Results:  
A file Save-As type dialog appears, asking me to choose a file name.
If I choose the same name as used before (in step 2), it says the file
exists and asks if I want to replace it.

Expected Results:  
It should just save the file again silently with the same name as used
before, without asking me to name it again.
1.8 is trunk, right?  
Version: 1.4 Branch → Trunk
Product: Browser → Seamonkey

After publishing, Composer "edits" the site on the publised URL, so it want to
"save as", because it is no more editing the local-file.
Assignee: composer → nobody
QA Contact: composer

Comment 3

7 years ago
Still actual
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1
Build identifier: 20120712003002
OS: Windows XP → All
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.