Forums :: Other extensions

DwZone Forum
Welcome to the DwZone-it Forum

FAQ

Memberlist

Usergroups

Other extensions

DwZone Forum Index -> Other extensions

Moderators: Administrators, Moderators

Mark all topics read

Hint: For improved responsiveness, use Internet Explorer 4 (or above) with Javascript enabled, choose 'Dynamic' from the View dropdown and hit 'Set Options' to save your changes.

	Search for
View Per page Messages Since

Messages 371 to 380 of 483 (Total: 237)

First | Prev | Next | Last

Subject

Author

Date

Re:Two issues with the Google Maps extension v 1.1.6

[email protected]

14:17 11 Aug 2007

Hi Gianluigi,

1- The extension places the image in the dwzGoogleMap folder by default. I did not change that.

Here's the lines of code generated by the extension. They are the only lines I can find that reference the image...

dwzGoogleMap_1.addPoint ".", ".", ".", ".", "", "custom", "International Tours & Cruises<br />dwz_vbcrlf_dwz1507 West Street Road<br />dwz_vbcrlf_dwzWarminster, PA 18974<br />dwz_vbcrlf_dwz215-293-0391<br />dwz_vbcrlf_dwz(In the Towne Center Shopping Center)", "BigDots_RED.png", "20_34", "40.220251", "-75.123136"
dwzGoogleMap_1.InsertImage()

I have these two folders in my server root...
/dwzGoogleMap/
/maps/

The map files I've created are in the /maps/ folder. The paths are the same as those on the IIS 6 production server, and the marker image appears when viewing the map on that server, but it doesn't appear on my local IIS 5.1 server when I hit the F12 key in Dreamweaver. How can the path be wrong if the marker image displays on one server but not the other?

If you can offer a solution it would be appreciated, but Issue #2 is more important to me.

2- Yes, I do have DW set up to use document relative links, and it works fine for my site. However, Dreamweaver allows me to depart from the default for links that require a virtual path relative to the site root.

Given that this is an ASP extension, and that MS states that only ASP files on an IIS 6 server need a virtual path when they are located in a folder under the server root, it seems only reasonable that the extension should allow the user to depart from the defaults as DW does. But not having that option, consider these evils I must choose from when using your extension:

a - put nearly 50 ASP map files in the site root (not acceptable, they should be in their own folder)

b - change DW's defaults for my entire site just so this extension will generate the correct path (not acceptable, the site defaults worked fine before I purchased the extension)

c - ask my hosting service to defeat the "Parent Path" setting in IIS 6 which is disabled by default for security purposes (not acceptable for obvious reasons)

d - manually remove the second line of code that your extension re-generates every time I edit map settings (not acceptable, it's extra work)

None of those steps would be necessary if only your extension allowed the user to depart from DW's defaults.

As it is now, it seems the extension recognizes a path based only on DW's default setting. As well, it generates a path based only on DW's default setting. In my opinion, it would be more fitting to have it recognize any valid path (whether it's a File -or- Virtual path), and refrain from re-generating the second line of unwanted code when a valid path already exists. The presumption being the user changed the previously generated default path to something that better fits his particular situation. Otherwise the extension is great - good work! But it lacks the versatility needed when DW's defaults simply cannot be used for everything. IIS 6 is a very popular and widely used server, surely others have run into this situation or will run into it.

Regards,
Frank