I have the same issue.
I tried Mantis 1.0.6, Mantis 1.1.0a1 and Mantis 1.1.0a2.
Without any success.

Same here, I'm surprised this issue hasn't come up yet, since it has been present at least since 1.0.6.
This problem only seems to occur on windows based servers, and not on my linux server.
What actually happens: When selecting a project, mantis is always showing the project with id=1, no matter what (sub)project the user actually selected. If this id is not present in the project table, it defaults to 'all projects'

imho, the severity should be scaled up a bit, as this issue is blocking for firefox users using mantis on a windows server.

What version of Firefox are you using?
2+ works well for me now (sorry for not reporting that)

(sorry too)
2.0.0.11

Hmm, that is strange. I also have 2.0.0.11.
I think, this is a configuration problem, may be you disabled JavaScript or something else important for Mantis.
I have reported this issue, but now I have no problem with Firefox 2.0.0.11 and Mantis 1.0.7

By the way, I have noticed, that if you work with Mantis from two windows of Firefox or Internet Explorer, the changes in filters in one window influence the another. I'm not sure if this a bug or a feature :-) but sometimes this is inconvenient.
Moreover, sometimes (very rare) I observed that filter settings of one user change the display of another, when two users simultaneously posts their changes to the database.

Hi!

I had the same problem...while using any browser with a proxy!

Browsers were caching the page bug_report[advanced].php... and only by hitting refresh the right project ID was selected.

I opted for using the solution from http://uk3.php.net/header

PHP scripts often generate dynamic content that must not be cached by the client browser or any proxy caches between the server and the client browser. Many proxies and clients can be forced to disable caching with:
<?php
header("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
header("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past
?>

Hope it helps!

i can confirm this bug... but since update to mantis 1.1.1 it's quite ok... with the application error message...

I can confirm this bug in Mantis 1.1.1 on Unix server (Ubuntu). It doesn't depend on browser or Web server. It is because of proxy cache.

We encounter this behaviour always after installing a new version of Mantis.
Currently we have FireFox 7.0.x installed on several machines.
Clearing the browser cache did not help.
Our workaround is, we remove the cookies. After that Mantis works as expected.

Unable to reproduce this on 1.2.11