Adding and deleting a virtual host monster to a folder which already contains one breaks virtual hosting

[Chris McDonough]

From Kai Vermeer:

Just added a virtual_host_monster and didn't notice I already had one
installed ... so after noticing it I deleted the one I added latest.

Now I can't access the site or the Zope manage area anymore ... all pages
display this error messages::

    Site Error

    An error was encountered while publishing this resource.

    Resource not found
    Sorry, the requested resource does not exist.

    Check the URL and try again.

    Resource: VirtualHostBase GET

(This is a UI bug. We probably shouldn't let users name vhms)

[Josef Meile (jmeile)]

> We probably shouldn't let users name vhms)
Why not, I think this is good if a zope's
admin has to leave his job. For the successor,
who not necessary has to know zope, would be
easier if a descriptive name is given.

[Tres Seaver (tseaver)]

Naming the VHM just leads to problematic scenarios: the default name is more googleable than anything else. If preventing name assignment / rename also removed the possiblitiy of a bug, so much the better.

[Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount)]

The code is now changed to use a class-level default Id. The user can no nonger select it. If an object with the same Id exists in the container, or if there is another VHM instance (an older instance with a different Id, for example), an exception is raised.

Zope 2.12 branch: http://svn.zope.org/?view=rev&rev=112531

Zope trunk: http://svn.zope.org/?view=rev&rev=112531