![]() By default all page types have support for extensions. If the parent page only allows one kind of page type, the wizard will jump to the next step.Īs we need to convert the source document to fit the page type we add another restriction that the page type needs both a configured filter, script and wizard for the current document type (based on the extension). This step has the same behavior as the "Create new page" functionality in EPiServer CMS and will display page types based on the allowed child page types from the parent page type. When the user has selected a location for the page, an EPiServer page type must be selected. The user can now decide if the EPiServer CMS page based on the document should be updated or if a new page should be created. If a user tries to republish a document that has already been published, a warning appears. This applies, for example, on the Document page type by default. Note When a document is published for the first time, a Microsoft Office property will be placed in the document to describe where the document has been published, if the AllowDocumentUpdate property is used on the page type and set to true. A session cookie for an authenticated connection will be stored until the user logs off the computer. If no password or session cookie has been stored earlier, a login prompt will appear. When the user selects a website, the wizard will contact the server using a Web service, receive pages from the site and make it possible for the user to choose a location for the new page. (Information about EPiServer CMS websites that are available for the user is stored in the registry together with an activation key.) First, the wizard lets the user choose the EPiServer CMS site to publish to. The most visible part of the solution is the wizard, which is activated from the Microsoft Office programs Word, Excel and PowerPoint. ![]() Select location, enter metadata and properties in the wizard. The main flow can be divided into the following parts:ġ. The resulting files are then uploaded to the EPiServer CMS page folder of the newly created page and a filter is activated on the server that creates the final HTML output. The next steps in the wizard are, technically, Web pages placed on the Web server, but shown in the wizard.Īfter the user has chosen to save and view, a script is downloaded from the server that creates local HTML documents, images and other files. In the first part of the wizard the user selects a site and location to publish the page to. When you select Publish to EPiServer in one of the supported Microsoft Office applications, a wizard is activated. This is done with the following location directive. The part of the path attribute named is to be replaced with the actual path to the UI folder. If Forms authentication is used on the website, access to the server parts of the office integration must be enabled in web.config before it is possible to use any functionality from within Microsoft Office applications. Enabling Office Integration in web.config Note If you use Integrated Windows Authentication, make sure you enable basic authentication. The client side application is installed from the main global menu by clicking on the user profile link in the upper right corner, selecting My Settings and then selecting the Microsoft Office Add-in option. The server side is built into EPiServer CMS and is activated from Admin mode by setting the appropriate access rights for the function in Permissions for Functions under the Security section of the Config tab in Admin mode. The EPiServer CMS 6 Office Integration package consists of a server-side and a client-side application that communicate with each other using HTTP. Note Basic authentication is not supported. The easiest way to resolve this is to add the EPiServer edit URL to the trusted sites in Internet Explorer. The default security settings in Microsoft Windows Vista prevents Internet Explorer from writing registry settings which causes the site activation to fail. Note The Office Integration client components needs permission to read and write the registry. The user needs to have at least create and edit access rights to the pages that are used to publish information to.The EPiServer CMS Office integration add-in components are backwards compatible with EPiServer CMS 4.62 or later on the server.Only Forms Authentication and Integrated Authentication with automatic logon is supported when publishing from Office applications.The Microsoft Office integration has the following additional requirements on the server setup: See System Requirements for general system requirements » Enabling Office integration in web.config
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |