Hi Ted,
Thanks for your recommendation. I haven't run into a path problem until I started using this extension. And frankly, I find creating virtual directories with IIS rather simple and uncomplicated, surely nothing I need to avoid. I can't blame IIS or DW as they, and other extensions I run, work fine. It's just that this extension isn't able to stand on its own merit without installing superfluous programs, or making otherwise unnecessary site-wide DW configuration changes, neither of which appeal to me. I'm sure MenuIIS works great, but for me it's not worth installing yet another new program just to get F12 DW functionality for marker images. And as I said earlier, this issue is much less important to me than issue #2, which isn't a path problem per se.
Although issue #2 appears to be a path "type" problem, it really isn't that either. After all, the virtual path I gave it in DW is the only path type that works on my production server. The problem is that the extension is not programmatically smart enough to recognize the perfectly valid virtual path and leave it the heck alone when I click OK. DW leaves the connection string path type alone after I set it to virtual, it STAYS THAT WAY - even after editing the recordset. Why shouldn't I expect the same behavior from the extension after I edit a map? Instead, every time I click OK it inserts this bogus line before the others, which breaks the page if it isn't deleted.....
<!--#include file="../dwzGoogleMap/dwzGoogleMap.asp"--> <---BOGUS LINE=PITA!!! <!--#include virtual="/dwzGoogleMap/dwzGoogleMap.asp" --> <!--#include virtual="/Connections/connETAlodging.asp" -->
I had a similar issue with a Web Assist extension writing a bogus script line in the head. They recognized that the behavior should not occur and fixed the extension's JavaScript code in short order by modifying a simple IF-THEN-ELSE statement. It was no big deal to them. They even did it in front of me, on my computer over a Breeze session. I'm not saying I expect that from Gianluigi, but I hope he will at least recognize that the behavior shouldn't occur and fix it in a future release.
Regards, Frank |
|
|