Can´t display view_all_bug_page.php after upgrade to 1.1.2

[udohof]

Afer upgrading version 1.0.7 to version 1.1.1 or 1.1.2 Internet Explorer cannot display site view_all_bug_page.php.
All upgrade scripts seems to be running sucessfully and also the test of database results in meassage is "OK".

I can view all pages in Explorer. After I had tried to display page view_all_bug_page.php login is damaged. I have to login again.

If am creating an new Project at upgraded version, creating new Issues, I can display these issue in site view_all_bug_page.php.
When I am moving several items from first projekt to new Projekt the failure is moved also to new Projekt.

Maybe it is an problem of the filter, or there are damaged items

[NirreFirre]

Afer upgrading version 1.0.7 to version 1.1.1 or 1.1.2 Internet Explorer cannot display site view_all_bug_page.php.
All upgrade scripts seems to be running sucessfully and also the test of database results in meassage is "OK".

I can view all pages in Explorer. After I had tried to display page view_all_bug_page.php login is damaged. I have to login again.

If am creating an new Project at upgraded version, creating new Issues, I can display these issue in site view_all_bug_page.php.
When I am moving several items from first projekt to new Projekt the failure is moved also to new Projekt.

Maybe it is an problem of the filter, or there are damaged items

I'm also having a similar issue (Firefox 3.01) but having no success in seeing the full Issue list ("All projects" selected), after three issues the tablerow gets broken...see attached screen dump. Selecting a Project from the dropdownlist (or going via All Projects->Manage->'select-one-project') shows that projects all issues without problem... same url in both cases...
So, is it something with a session cookie variable ..? Cache/browser issue? (being new to Mantis so...).

[udohof]

Afer upgrading version 1.0.7 to version 1.1.1 or 1.1.2 Internet Explorer cannot display site view_all_bug_page.php.
All upgrade scripts seems to be running sucessfully and also the test of database results in meassage is "OK".

I can view all pages in Explorer. After I had tried to display page view_all_bug_page.php login is damaged. I have to login again.

If am creating an new Project at upgraded version, creating new Issues, I can display these issue in site view_all_bug_page.php.
When I am moving several items from first projekt to new Projekt the failure is moved also to new Projekt.

Maybe it is an problem of the filter, or there are damaged items

I'm also having a similar issue (Firefox 3.01) but having no success in seeing the full Issue list ("All projects" selected), after three issues the tablerow gets broken...see attached screen dump. Selecting a Project from the dropdownlist (or going via All Projects->Manage->'select-one-project') shows that projects all issues without problem... same url in both cases...
So, is it something with a session cookie variable ..? Cache/browser issue? (being new to Mantis so...).

Thank you for answering, I have tried to delete all temp. internet files and cookies, but I Have still the same error behaviour.

[NirreFirre]

I scrapped the 1.1.2 upgrade and reverted to 1.0.5. The upgrade scripts seems to have some work left even though the db looked ok..

[udohof]

That is the same I have done. I scrapped the complete installation 1.1.2 and took the old version 1.07 again
But in version 1.1.2 there is the feature roadmap, I want to use.

So it would be glad, if there is a solution for using this feature.

[Mithril_Claws]

I found a setting that were disabled by default and was preventing the display of attached pictures in config_defaults_inc.php

Here's some variables that you should customize to your needs.
$g_preview_attachments_inline_max_size = 5000000; # 5 MB
# Instead of 0 that disable it.

$g_preview_text_extensions = array( 'txt', 'diff', 'patch' );
# Default value

$g_preview_image_extensions = array( 'bmp', 'png', 'gif', 'jpg', 'jpeg' );
# Default value

$g_preview_max_width = 0;
# No limit display size # Default value

$g_preview_max_height = 0;
# No limit display size # Instead of 250 that display only a little thumb.


Thanks to that post, I thought of searching variables and configurations.

I hope that will help.