556508 - Provide way to disable 'What's New' tab from opening after minor updates.

Status: RESOLVED DUPLICATE of bug 690316

(Thunderbird :: General, defect)

Description

[Charles]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: 3.0.4

Summary says it all.

This is getting really irritating. Besides being incorrect information as bug 549447 points out, there should also be a way to permanently disable this for those of us who don't want/need it.

Hmmm...

Will setting app.update.silent to true accomplish this?

Reproducible: Always

Comment 1

[Mark Banner (:standard8)]

You can set the hidden pref "mailnews.start_page_override.mstone" to "ignore". Doing so may also mean you don't get presented with migration assistants and other information on future updates.

Comment 2

[Charles]

(In reply to comment #1)
> You can set the hidden pref "mailnews.start_page_override.mstone" to "ignore".

Either  this pref is badly named, or not what I'm looking for.

There is a UI pref for disabling the START page.

I'm talking about the 'What's New' page that opens every time TB updates itself.

You didn't answer about the app.update.silent pref - what is it for?

> Doing so may also mean you don't get presented with migration assistants and
> other information on future updates.

Reopening, because setting a hidden pref that does *not* accomplish the purpose of the bug is not a resolution.

I did, however, modify the bug Title to be more indicative of what I'm asking for.

There should be a way to disable the 'Whats New' page so that it doesn't open every time TB updates from one minor version to another, without totally disabling *major* update notifications, migration assistants, etc.

Comment 3

[Ludovic Hirlimann [:Usul]]

Charles look into bugzilla we have a dup for your issue.

Comment 4

[Charles]

Well, I already searched and didn't find a dupe - if you know of one, please do tell...

And I'd still like an answer to what app.update.silent pref does...

Comment 6

[Charles]

Re-opening, because it isn't a duplicate.

Bug 548619 is about providing more contextually correct update pages, which I agree would be a good thing.

What this bug is asking for is simply a way to *disable* *minor* update pages - ie, going from 3.0.5 to 3.0.6, or 3.1.1 to 3.1.2) - without disabling the update page/migration assistant for major updates - ie, 3.1.x to 3.2...

And *still* no one has answered what app.update.silent does...

Oh... and

(In reply to comment #1)
> You can set the hidden pref "mailnews.start_page_override.mstone" to "ignore".
> Doing so may also mean you don't get presented with migration assistants and
> other information on future updates.

'May'? Either it will or it won't... so, can you confirm which it is? I certainly wouldn't want to disable major update notifications, and especially migration assistants for major updates if they are needed...

Comment 7

[Wayne Mery (:wsmwk)]

If what's new is being improperly presented after an update, the proper way to address it is to fix the issue - not provide a work around.

skipping to version 5 - some people have reported the issue is gone (bug 619772 comment 9)

Question - is the problem gone for you in version 5?

Comment 8

[Wayne Mery (:wsmwk)]

Mark, do we care about this now that minor version updates are mostly gone?

Comment 9

[Mark Banner (:standard8)]

We actually did this in bug 690316.

app.update.silent looks like just a way to hide the prompts prior to the actual update.