Legend widget misbehaves when you set maxscaledenom to a layer that is outside the web min / maxscale

[pdeschamps]

Using fusion 1.1 rev 1581 also reproducible in trunk rev 1675 Using the "/templates/mapserver/standard/" application Using gmap.

Steps to reproduce:

set your WEB section to this:

WEB
  MINSCALE 2000000
  MAXSCALE 50000000
#
# On Windows systems, /tmp and /tmp/ms_tmp/ should be created at the root 
# of the drive where the .MAP file resides.
#
  IMAGEPATH "/home/pdeschamps/fgs/tmp/ms_tmp/"
  IMAGEURL "/home/pdeschamps/fgs/tmp/ms_tmp/"
END

add the maxscaledenom to the rail layer

LAYER
  NAME rail
  MAXSCALEDENOM 1000000
  METADATA
    "DESCRIPTION" "Railroads"
  END
  TYPE LINE
  STATUS ON
  DATA rail
  CLASS
    NAME "Railroads"
    STYLE
       SIZE 1
       SYMBOL "circle"
      COLOR 168 0 184
    END
  END
END # Layer

When you set a layer to have a maxscaledenom of 1,000,000 when your web->maxscale is set to 2,000,000 the legend misbehaves.

Zoom in the the 1:200,000 and notice that the legend has toggled all the layers as inactive.

Understandable issue as the user should not specify a maxscale or minscale that is outside of the web's min / maxscale.

[pdeschamps]

added login in the scale processing to reset the layers min / max scales to be set to the main map's min man scales if they happen to exceede the main map scales. without this you get un expected ui behaviour in the legend.

/fusion/trunk/layers/MapServer/php/LoadMap.php REV # 1776

I added closes comment in the commit however it did not close the bug