View Issue Details

IDProjectCategoryView StatusLast Update
0023936mantisbtuipublic2018-02-28 03:46
ReporterDRohwerder Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2.10.0 
Summary0023936: UI issue in Internet Explorer 11
Description

Still havin issue as discribed in 0022141, even without using a custom_strings_inc.php
Checked charset encoding of all files and DB. Everything seems to be correct.
But still having this annoying display error.

Additional Information

MantisBT 2.10.0
Schema 209
PHP 5.6.33
mysql 5.7.12
IE 11.0.9600.18816

TagsNo tags attached.
Attached Files
MantisBT-Issue_IE11.png (233,565 bytes)   
MantisBT-Issue_IE11.png (233,565 bytes)   

Relationships

related to 0022141 closedatrol UI Internet Explorer 11 issue if custom_strings_inc.php is used 

Activities

atrol

atrol

2018-02-06 08:18

developer   ~0058767

Do you get any errors or warnings wehen running admin/check/index.php?

DRohwerder

DRohwerder

2018-02-06 08:35

reporter   ~0058768

I get following warinings ...

  • I should delete "admin" folder
  • register_argc_argv php.ini directive is disabled
  • display_errors php.ini directive is disabled
  • mysqli.allow_local_infile php.ini directive is set to 0
  • core_path configuration option is set to a path outside the web root
  • class_path configuration option is set to a path outside the web root
  • library_path configuration option is set to a path outside the web root
  • config_path configuration option is set to a path outside the web root
  • language_path configuration option is set to a path outside the web root
  • Directory doc does not need to exist within the MantisBT root
  • Directory api should be removed from the MantisBT root if you do not plan on using SOAP

It's a LAN only installation and it's encapsulated within a Docker, so i ignored the security warnings.
But i don't think these warnings are the root cause.

dregad

dregad

2018-02-06 08:55

developer   ~0058769

Not sure if this is the same issue as 0022141, where the header div expands over the main display area, whereas in this issue the header is "pushing down" the rest of the display.

Anyway without being able to reproduce, I'm afraid there is not much I can do to help.

DRohwerder

DRohwerder

2018-02-06 10:23

reporter   ~0058770

Ah, no, the header is not pushin down the main area. The header is expanded and is laying over the rest of the page.
If i scroll down, the main page disapears behind the header.

DRohwerder

DRohwerder

2018-02-06 10:52

reporter   ~0058771

Ok, now i understand what you mean ... in 0022141, the NavBar on the left is disapearing behind header, while it's not the case in my issue ...

With Browser-Debugging enabled, i can see, that "main-container" has a "padding-top" of 340px.
So the main area starts below header.
If i change "Document - Mode" to emulate "IE 9" the issue disappears. And the "padding-top" for the main-container changes to 45px.

DRohwerder

DRohwerder

2018-02-06 11:11

reporter   ~0058772

I fixed that by changing layout_api.php from
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
to
<meta http-equiv="X-UA-Compatible" content="IE=9,chrome=1">

I'm not sure if that's a "good" solution, but it seems to do the job for me.

atrol

atrol

2018-02-06 11:23

developer   ~0058773

I'm not sure if that's a "good" solution

At least it's a workaround, but it hides just another issue.
I assume you don't get the issue when visiting https://www.mantisbt.org/bugs so there is a difference in your installation.

Just a guess,

temporarily change line 37 in file status_config_php
from

@require_once( dirname( dirname( __FILE__ ) ) . '/core.php' );

to

require_once( dirname( dirname( __FILE__ ) ) . '/core.php' );

and check if you get any error in logs.

DRohwerder

DRohwerder

2018-02-06 12:10

reporter   ~0058775

I set log_level to LOG_ALL and log_destination pointing to a file.
And changed status_config.php like you suggested.
There are no errors neither with "@require_one" nor with "require_one".

The application is running behind a reverse-proxy, maybe that's an important information ....
And it's running within a docker container and a second docker container for MySQL (these two are linked to each other).
All other functions are working fine with that setup. It's just the display error for IE 11 (unfortunately IE11 is our company's default browser).

atrol

atrol

2018-02-06 13:32

developer   ~0058777

and check if you get any error in logs.

This was not meant to enable and check Mantis logs, it was meant to check web server and PHP error logs (might be the same depending on your configuration).

atrol

atrol

2018-02-17 18:13

developer   ~0058920

DRohwerder,

You did not provide feedback; I am therefore resolving this issue as "no change required".

Feel free to reopen the issue at a later time and provide the requested information.