Disadvantage for managed page in Webspshere portal server 8.0

• Personalization rules that you create using the Personalization editor are not managed in Web Content Manager and so are not available for versioning or included in syndication. These rules must be published using the pznload command or by publishing with Personalization.
• Personalization rules are not aware of projects and the status of items in a project. Because of this characteristic, rules operate only on published content and do not include draft items.
• Explicitly derived pages that are in the release domain can be managed by Web Content Manager. However, if you modify an explicitly derived page, that change does not generate drafts for all of the derived pages. If you want the change to occur for all of the derived pages, you must edit each derived page separately. For more information, see the documentation about derived pages.
• If you change the configuration settings for a portlet in Configure mode, these changes are global and are not limited to the page. Because the changes are global, the changes cannot be managed in Web Content Manager and so cannot be syndicated to another server. To transfer these changes to another server, use the XML configuration interface (xmlaccess command).
• If you change the configuration settings for a portlet in Edit Shared Settings mode, these changes are part of the page. Because the changes are part of the page, the changes are managed in Web Content Manager and are automatically syndicated to other servers.
• The New Site wizard for creating virtual portals is not supported when managed pages are enabled.