|The root page.|
|A start page.|
|A published page.|
|A page that links to another page on the same website.|
|A page that fetches and displays content from another page on the same website.|
|A page that links to an external website or a specific address.|
|A page containing a shortcut that is not linked anywhere; it only displays the text and is used to create a heading with no link in the menu.|
|A container page used for storing other pages; not visible on the website.|
|A published page. This icon appears for project items; not in the Pages navigation pane.|
|A draft of a new page that is not yet published.|
|A new page that was scheduled for publishing; not visible on the website yet.|
|A page that has an expiration time that has passed; not visible on the website.|
|A page that is set to Ready to publish.|
|A page that is set to Rejected.|
|A page is currently In review and must be reviewed and approved before it can be published. See Content approvals (Beta).|
|You do not have the rights to publish this item or the specific item version does not exist anymore. This icon appears for project items; not in the Pages navigation pane.|
|A previously published page, not visible on the website.|
|A page that is locked for editing for the logged-in user.|
|A page that is being edited by another user.|
Content can have the following status in the version gadget:
- Draft. Content that is work-in-progress and is not yet subject to any publishing actions.
- Published. The most recently published version and the one publicly displayed. Only one published version can exist.
- Previously Published. One or more versions that were published before the latest published version.
- Ready to Publish. Content awaiting approval and publishing.
- Rejected. A draft that was rejected by someone as part of an approval flow. You can edit and update rejected content and then set to Ready to Publish again.
- Delayed Publish. Content scheduled to be published.
- Expired. Content where a stop publish date and time were set and passed.
- From edit viewA section of the user interface where you edit content items, such as pages and blocks. To access edit view, log in and select CMS > Edit. (See admin view for comparison.), click Tasks in the navigation pane.
- Use the drop-down to select the status of interest.
No, you can safely click this option. No previous edits are lost.
Click Preview to access preview mode. From there, you can click links and verify that they are accurate.
- Select Undo in the page information area to discard changes made since the last autosave.
You can undo changes made only in the current editing session. If you move to another page, close the browser, log out, and so on, the history of actions that can be undone is emptied.
- If content was previously published, select Revert to Published from the Publish? button to return the last published version.
- Log in and access edit viewA section of the user interface where you edit content items, such as pages and blocks. To access edit view, log in and select CMS > Edit. (See admin view for comparison.).
- Find the content that you want to compare.
- From the toolbar, click the Compare button . Select the On-page compare mode, if not already selected.
The current version appears on the left.
- From the Comparing bar, click the Previously published drop-down list. Previous versions appear.
A system administrator configures the number of versions that your site maintains. The default value is 20.
- Select the version that you want to compare with the current one.
- When you are done, click the Compare button again to return to the edit view.
Add the Recent gadget either to your left or right pane. The Recent gadget displays content viewed during your current session. See Managing gadgets for installation information.
Click the Toggle Full Screen Mode button.
Click the same button again when you want to close the full screen.
If you add an image to a page in edit view but it is not displayed when the page is published, it is most likely because the image itself is not published. Media (such as images and files), blocks and forms need to be published just as pages do. Publish the image and it will be displayed on the website.
Avoid this with either of the following solutions:
- An administrator can enable the Auto publish media on upload feature. This automatically publishes images and files when you upload them. However, media is not auto published, even if this option is selected, if the folder you are uploading to has a content approval sequence set.
Caution: Even though the media is not published on your website until it is included in a published page, it is indexed immediately and can be found through a search. This is worth remembering if you are uploading sensitive information that should not be accessible until a set time, such as an annual report.
- Use the projects feature. When you are working in a project and add images, blocks or forms to a page, these are automatically added to the project. From the project overview you can set all items (including media, blocks and forms) to Ready to publish and publish them at the same time. If the projects feature is enabled, media is not auto-published, even if the Auto publish media on upload setting is enabled.
Add the Versions gadget either to your left or right pane. From this gadget, you can view and republish older versions. See also Managing gadgets.
The projects feature automatically associates pages, assets, blocks, catalog items and so on while they are under development. When ready, use the project overview to simultaneously publish all items with a status of Ready to Publish.
An administrator enables the projects feature. If not enabled, you can use the projects gadget instead to multi-publish items.
- From the navigation or assets pane, select Settings > View Trash.
- Select the content to restore.
- Click Restore.
The content is restored to its original place. If it was published, it is republished.
- In the upper right corner, click your user name.
- Select the Display Options tab.
- At the Personal Language drop-down, select the language of your choice, and click Save.
Use the Versions gadget to work with multiple drafts. The gadget also lets you label any draft the primary draft. When opening an item, Episerver CMS displays the either the version that is set as primary, or, if a project is active, the version associated with the active project. See also Versioning when working in projects and Managing gadgets.
Drag-and-drop is available in many instances.
- While editing a page in the rich text editor, create a link by dragging a page from the page tree.
- Drag and drop images into the editor.
- In the assets pane, drag and drop assets between folders.
- In the page tree, drag and drop pages to change the order.
Go to global menuA group of options that appears in the uppermost part of the user interface when logged in. The global menu displays products and systems integrated with your website. It also displays links to the user guide and user settings, and to a global search. See the User interface topic for further information. > Reports. See Reports for a list of standard Episerver reports.
When creating or editing the page, click All properties . Then, clear the Display in navigation check box.
- From the dashboard, navigation pane or assets pane, select Settings > Rearrange Gadgets.
- Drag and drop a gadget to the desired position.
There are two ways to enable Episerver projects functionality.
- Your administrator enables the projects feature for the entire site. In this case, you see a project bar at the bottom of the CMS window. If you create a project from that project bar and have it selected, content is automatically associated with the project when you create or edit it. The specific content version is associated with the project for all users, so other users must either use that project to update that version or create a draft from it.
- If the project feature is not enabled for the entire site, add the projects gadget to your work area and manually add content to the project. That project is accessible to other users if they use the project gadget. You can also edit content outside of the project.
Use these tips to find content from the CMS edit viewA section of the user interface where you edit content items, such as pages and blocks. To access edit view, log in and select CMS > Edit. (See admin view for comparison.).
|What you know||Action|
|Content location within page, asset or block structure||Navigate the page tree structure or the blocks and media assets pane and select content.|
|Content location on the website||Using the preview option, navigate to the content on the website.|
|Content is associated with a project||Use the projects gadget or, if you are using the projects feature, the project overview or the project items navigation pane.|
|Text within content title or body||
Use either the global search in the global menu or the search fields at the top of the navigation and assets panes.
See Search for search tips.
|A page's status (for example, draft)||Use the Tasks tab to find all content in that status.
|Content was edited recently||Use the Recently changed status in the Tasks tab or the Recent gadget. See Managing gadgets for information on how to add this gadget.|
Prerequisite: The desired language is activated and enabled in edit viewA section of the user interface where you edit content items, such as pages and blocks. To access edit view, log in and select CMS > Edit. (See admin view for comparison.). See Managing website languages.
When translating an existing content item or block, click Compare. See Comparing language versions when translating content
When translating a website, the Episerver Languages add-on is helpful.
- Activate the project in the project bar, if not already done.
- Select the content that you want to preview.
- Click Preview. You can now navigate your site and see what it would look like if items in the project were published. That is, previewing when a project is active shows you the draft associated with the project or, if there is no draft associated with the project, the published version.
A landing page is an important tool for generating leads and converting visitors. The following tips can help you make the most of it:
- Landing page visitors who are redirected from an ad or a search should see content that matches their expectations. For example, if an ad promotes a 10% discount, the landing page should give the same message.
- Keep it simple and do not forget to use white space. A cluttered landing page scares people off.
- Create engaging copy. Who are your visitors or customers? Adjust your language and tone to your target group.
- If you want visitors to perform an action (sign up for a newsletter, enter a competition, buy an item), make sure that a form, block, or teaser is the focus.
- Keep forms short. For the Submit button, use a phrase that is more engaging than Submit such as Buy now! or Visit our travel site!.
- A/B test your conversion blocks.
- Test your landing page. Make sure it functions as well on a mobile device as on a larger screen.
- Include links to your company's social media pages.
For tips on using search in this user guide, see Search tips.
CMS Administrator FAQs
Prerequisite: Assumes that the users already exist, and belong to the WebEditors group and a group that gives them access rights to content being created/edited.
- Go to admin viewWhere administrators manage access rights, website languages, scheduled jobs, export and import of data between websites, and configure new websites in a multi-site solution. (See edit view for comparison.) > Admin tab > Access Rights > Administer Groups > Add.
- Create a new group called German editors.
- Under Access Rights, click Search User/Group.
- Select a user.
- On the Edit User screen, assign the users to the German editors group.
- Repeat steps 3-5 for all German editors.
- From the Admin tab, go to Config > Manage Website Languages.
- Select German (Deutsch).
- Click Add Users/Groups. The Add Users/Groups dialog appears.
- At the Type drop-down, select Groups and click Search.
- Select the German editors group. Then, click the right arrow to move it to the Add area.
All users belonging to the German editors group now have access to German content.
The user needs membership in a structure-based group that has Change access rights.
Each group can have different access levels, for example create and change, or create, change, and publish, and so on. Make sure the user belongs to a group that has Create and Change access rights for the page.
Episerver comes with a content approval feature that gives you exactly this functionality. As an administrator, you can define which content must go through the review and approval procedure, and also define who should review and approve each content item. Read more on how to set up this procedure in Managing content approval sequences (Beta).
To enable the creation of content in multiple languages, you need to complete two steps. If you see this error, you completed step 1 but not step 2 for a page in the following procedure.
Episerver's personalization features let you optimize each visitor's experience by customizing web pages for different users and groups. Customization is based on factors such as geographic location, language, previous visits, day or time of visit.
Episerver is installed via a number of NuGet packages and if you have access to the website's code base, you can check the version number of the NuGet packages. You also can see the version numbers of the installed components in the admin view > Config > Tool Settings > Plug-in Manager.
- A product packageCommerce: a unit that contains multiple products or variants, with a single unique pricing for the entire package; comparable to an individual SKU because the package item must be purchased as a whole (such as a computer system). contains multiple products or variantCommerce: a variant or SKU corresponds to a specific product with specific characteristics. For example, a product line of shirts has individual variations/SKUs that include size, color, and collar size.s, and has one price.
- A product bundleCommerce: a collection of variations and SKUs that let customers purchase two or more items at once. is a collection of variants with individual pricing. Customers can purchase two or more items at once.
- Create a user profile here: https://world.episerver.com/System/Users-and-profiles/Register1/.
- Go to http://world.episerver.com/forum/developer-forum/Episerver-Commerce/ and click New Topic.
CatalogsCommerce: a top-level container for catalog entries such as categories, products, and variants (SKUs)., marketsOne or more countries, regions or customer groups, to which you want to apply languages, catalogs, currencies or promotions. The market features support targeted merchandising and personalization., and payment Commerce: the verification of a money transaction in a website shopping situation. The e-commerce system most often needs a verification for a payment to create the actual purchase order and complete the shopping workflow.and shippingCommerce: A set of information and rules that determine the shipping cost. Displayed on the front-end public site while a customer checks out an item from the shopping cart. The shipping fee is added to the total price of the purchase. A shipping method is mapped to a shipping provider visible to a back-end administrator in Commerce Manager. For example, when a customer picks "Ground Shipping," UPS (or another provider) may fulfill the shipment. methods.
Both promotions should apply as long as these conditions are met:
- The promotions are not excluded by each other or by other promotions.
- The conditions for the second promotionCommerce: A way to apply a discount to products, order totals, or shipping; a marketing tool used to increase sales of certain products or product lines. A promotion is associated with a campaign. (lower priority) are satisfied after the first promotion is applied. For example, the first promotion discounts the cart $50, making the cart subtotal $480. If the second promotion requires the cart subtotal to be at least $500, it is no longer satisfied.