Document Actions
The setup of Plone and Zope on Windows isn't the same as regular Zope. How is it set up?
Up to Table of ContentsThis FAQ applies to: Any version.
Plone by default binds to port 80 for the Plone root and port 8080 for the Zope Management Interface root. This can be a bit confusing if you're used to plain Zope - and is controlled by the accessRule.py in the Zope root.
For example, if you access Zope via FTP, you will end up inside Plone. If this is not what you want, you can modify accessRule.py or just remove it altogether.
To make Plone run on http://localhost/Plone instead of http://localhost, log in at http://localhost:8080/manage and delete the accessRule.py object.
In addition, if you want to bind it to a different port than port 80, stop Plone via the Plone Controller and put in (for instance) port 81 in the Ports page and start it again. For other platforms, this is usually controlled from the etc/zope.conf file.
The reason the access rule is enabled by default is because we want people to easily be able to serve their Plone pages off (for example) their home DSL connection, should they want that. The people who know enough to use it in a server setting of course know how to set up the surrounding software appropriately, but the Windows installer aims to be as easy to use as possible - hence the default access rule in place.
