184216 - unable to publish from the composer

Status: VERIFIED FIXED

(SeaMonkey :: Composer, defect)

Description

[jean-max Reymond]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021206
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021206

with a preversion of 1.3a, I try to publish my page.
So, the dialog window is empty; I try to add a new entry and it says to me that
entry already exists

Reproducible: Always

Steps to Reproduce:
1.try to publish a page from Compser
2.The publish window is empty, so you try to add a new entry
3.insert an previously entry (but not displayed)

Actual Results:  
message: entry already exists

Expected Results:  
first, display the entries
If not and you have to insert all the previously entries, does not complain that
entry already exists

Comment 1

[Syd Logan]

--> brade for investigation.

Comment 2

[Kathleen :Brade]

jean-max Reymond--can you clarify the steps you give?
for step 1: "try to publish a page from Compser"
 - are you starting with an empty page or opening a local file or editing on the
server?
 - are you choosing "publish" or "publish as" or "publish settings"?

for step 2a: "The publish window is empty"
 - is this the publish dialog or the publish settings?
 - what tab do you see (what are the prompts/edit fields in the dialog)?

for step 2b: "so you try to add a new entry"
 - how do you do this?  Do you click a button or fill in the fields or ?

for step 3: what is the error message you get (exact text if possible)?

-->cmanske since this sounds like the publish UI and not the publishing core

Comment 3

[jean-max Reymond]

jean-max Reymond--can you clarify the steps you give?
I try !!!

for step 1: "try to publish a page from Compser"
 - are you starting with an empty page or opening a local file or editing on the
server?

I start with an empty page but it issimilar with existing pages

 - are you choosing "publish" or "publish as" or "publish settings"?

I choose "Publish as" But I have the same troubles with publish

for step 2a: "The publish window is empty"
 - is this the publish dialog or the publish settings?

The two tabs are empty . The first one is naturally publish but it is empty so I
swith to the setting tab and it is empty too

 - what tab do you see (what are the prompts/edit fields in the dialog)?

All the fields are empty

for step 2b: "so you try to add a new entry"
 - how do you do this?  Do you click a button or fill in the fields or ?

I fill the fields in the setting tab. When all the fielads are filled, I click
on the tab setting 

for step 3: what is the error message you get (exact text if possible)?

"tomfun" already exists. Pelase enter a different site name.

NB: tomfun is the name of my site

-->cmanske since this sounds like the publish UI and not the publishing core

Comment 4

[Kathleen :Brade]

>>for step 3: what is the error message you get (exact text if possible)?
>
>"tomfun" already exists. Pelase enter a different site name.
>
>NB: tomfun is the name of my site

Have you tried using a different name?  Does tomfun2 work?

Another thing to check is in the Publish tab, is there anything in your site
menu (to the left of the "new site" button)?

You might also want to check your "Publishing Site Settings" (under Edit menu).
 The sites you configure in that dialog should also appear in the site dropdown
list in the Publish tab within the Publish dialog.

Comment 5

[jean-max Reymond]

Have you tried using a different name?  Does tomfun2 work?

with tomfun2, I can switch to the publish tab but all is empty so I switch again
the setting tab, tomfun2 is here, so I swith again to the publish tab and now, i
have again the message "tom2 exists already exists. Please enter a different
site name."

Another thing to check is in the Publish tab, is there anything in your site
menu (to the left of the "new site" button)?

I have the Drop-down button (is it the term ?) bot no site names to display.


You might also want to check your "Publishing Site Settings" (under Edit menu).
 The sites you configure in that dialog should also appear in the site dropdown
list in the Publish tab within the Publish dialog.

Oh, Yes, all my sites are here (hello, good old friends) in the "Publishing Site
Settings" (under Edit menu) but nothing in the publish dialog ;-) 
Does I miss something but I use the publish menu once a day since 6 months. 

Comment 6

[Charles Manske]

This is all fairly confusing! What would really help is to do this:
1. Locate your "prefs.js" file. This is in an directory under your profilename,
The default location is deep under "Documents and Settings" on your C drive.
It's probabaly simpler to locate "prefs.js" by using the Windows Find file feature.
Email this file to me so I can see what your publishing site data contains.

Comment 7

[Kathleen :Brade]

Confirming; I see this problem on my Mac debug build from today.
This is a serious regression!

Bug 118038 appears to have a fix that would fix this problem so making this bug
depend on it.

Comment 8

[Asa Dotzler [:asa]]

What regressed this and how can we fix it without having to take a big
menulist.xml patch so late in the game? 

Comment 9

[Charles Manske]

mostly, no. that menulist patch is very good and fixes many problems.
I could back out some code in Composer, but that seems conter-productive.

Comment 10

[Kathleen :Brade]

cc asa so he can see response to question he posed

Comment 11

[Asa Dotzler [:asa]]

I'm concerned about taking such a large change to menulist.xml so close to the
release. If the choice was between a release note, "publish doesn't work in
1.3a" or backing out some code to fix this regression which one makes the most
sense? What fix regressed this? What would we be re-breaking to back that out?

Comment 12

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

(mid-air colliding with asa.)

The issue is that drivers would like to ship 1.3alpha tomorrow in order to avoid
keeping the trunk closed (and avoid the cost of a branch, which is now the
general rule for alpha/beta releases).  I'm not comfortable taking changes that
would affect the whole product and shipping tomorrow's builds as 1.3alpha, since
they'll be shipping with essentially no testing.  (Especially right after what
just happened with 1.2 being pulled and followed up by a 1.2.1 within days.)

That said, there might be some other issues for which we'd want to hold
1.3alpha, in which case we could probably take the menulist.xml patch if we get
it in before tomorrow morning's builds.

Comment 13

[Charles Manske]

While the fix for bug 118038 was not checked in for 1.3a, I checked in some 
changes to make publishing work.

Comment 14

[sujay]

verified in 12/12 build.

Comment 15

[R.K.Aa.]

*** Bug 186244 has been marked as a duplicate of this bug. ***