Opened 12 years ago

Closed 12 years ago

#69 closed defect (wontfix)

Nightly MS4W Demo Not Working - 4/11/12

Reported by: andersd Owned by: theduckylittle
Priority: critical Milestone: 2.6
Component: Demo Version: 2.6
Keywords: Cc:

Description

Just loaded the nightly MS4W demo. Unzipped on a new version of MS4W 3.0.4. It is not working.

  1. Starts OK
  2. Parcels come up pink
  3. Zoomto missing
  4. Print icon is the binocs icon
  5. Words next to icons (ie. sketch) do not appear.

Please re-run cron job.

Change History (7)

comment:2 by EliL, 12 years ago

Actually, it looks like that has always been that way.

comment:3 by theduckylittle, 12 years ago

Owner: set to theduckylittle
Status: newaccepted

Deleting lines 30-31 should make it work on MS4W by default.

The paths are always a problem. I made a fix to support a "local_settings.ini" that is ignored by SVN.

r729

comment:4 by theduckylittle, 12 years ago

Okay, now we need some documentation.

Essentially, I've just completely changed the way mapserver and the default mapfile path are configured.

  1. There is now a "local_settings.ini" file that must exist to change settings. SVN will *ignore* this file.
  2. getmapbook.php will now dynamically add <param>'s to <configuration>. This puts the mapserver-url and mapfile-root into the configuration without the user needing to edit the mapbook.
  3. We can add some default local_settings.ini files. Right now I have a ms4w_local_settings.ini file in there. It'd be nice if someone can test it.

comment:5 by bfischer, 12 years ago

I just updated to the latest SVN on gmtrunk.houstoneng.net and it seems to work great. This will be new to users so we need to make it clear to them that this is how it works now.

comment:6 by EliL, 12 years ago

updated docs, r738

comment:7 by theduckylittle, 12 years ago

Resolution: wontfix
Status: acceptedclosed

If this is still a problem later, open a new ticket, the new workflow has been implemented and it won't allow too many useful transitions from assigned.

Note: See TracTickets for help on using tickets.