New Message: Re: Manila Tools vs. Website Fragment Path

[webmaster at userland.com]

A new message was posted:

Address: http://manila.userland.com/discuss/msgReader$1181

By: Scott Greiff (scottag at greiff.org)

Pardon the broken logic of a 3AM post to the news groups. :)

| It seems that Manila thinks my www.example.com site is somehow the server admin site when it's not.
|
|Can you explain what you mean by this? Do you get a password challenge? If you enter valid login information, what page loads at that URL?

I don't get a password challenge.

The tool works great if the site is hosted off of www.myserver.com/site. The url to the site's tool would be, in this case, www.myserver.com/site/mytool/. everything was hunky-dory. Then I moved the /site site to its own domain www.site.com. So, in this case, the too's path would have been www.site.com/mytool/. However, when you try to go to that URL, instead of getting the site's Website Fragment installed when the tool was "enabled", you get the server tool page (or the tool's mytoolWebsite default page). The tool's default page comes up just fin under www.myserver.com/mytool/, but the top-level domain site is hosed.

To fix this, I just removed the tool's Website. The site at the top-level works just fine with the tool's Website removed.

Do you have some pointers on the "Tools framework" and how Manila could handle this for me? Again, I have some Website fragments I'd like installed on the client, but also have some server-side control of system-wide parameters.

I'd love to work with you to determine what the problem might be.

- ScottAG
http://scott.greiff.org

This is a Manila site.. http://manila.userland.com/.