Other Editing. OU Campus v10. OmniUpdate, Inc Flynn Road, Suite 100 Camarillo, CA 93012

Transcription

1 Other Editing v10 OmniUpdate, Inc Flynn Road, Suite 100 Camarillo, CA 93012

2 OmniUpdate, Inc Flynn Road, Suite 100 Camarillo, CA (fax) Copyright 2014 OmniUpdate, Inc. All rights reserved. Document Number: b-003 Publish Date: 8/26/2015 OmniUpdate and are trademarks or registered trademarks of OmniUpdate, Inc. Any other company and product names, and trademarks mentioned within are property of their respective owners. Content is subject to change without notice. About OmniUpdate, Inc. OmniUpdate is the leading web content management system (CMS) provider for higher education. The company focuses on providing an exceptional product and customer experience to its CMS users who manage more than 700 web and mobile sites in the U.S. and around the world. is secure and scalable, server and platform independent, and seamlessly integrates with other enterprise campus systems. It provides college and university web developers, administrators, and marketers with the userfriendly tools and deployment flexibility they need to achieve excellence. For more information, visit. About This Guide The Other Editing booklet includes Source Editor, Properties, Image Editor, and Reminders. Support The Support site is available to everyone and users are encouraged to visit and browse the site for information. An institution's administrators are also available if the answer cannot be found on the Support site or further explanation and clarification is needed. Administrators may contact the OmniUpdate Support Team. Ways to access the support documentation include: Support site: The help link in the main interface of The WYSIWYG Help link Help links embedded in the system Text instructions are provide onscreen for specific fields and functionality OmniUpdate Community Network (OCN): Conventions Shorthand for navigation through the CMS is indicated with a greater-than sign and bolded: > For example, Setup > Sites. Code snippets use Courier New and a shaded background. Page 2 of 37

3 Contents Edit...4 Overview...4 Editable Regions...4 Editing Methods in...5 WYSIWYG Editor...5 MultiEdit...5 Source Editor... 5 Page Properties... 5 Image Editor... 5 Source Editor... 6 Accessing the Source Editor... 7 Using the Source Editor... 8 Using Gadgets in the Source Editor Syntax Highlighting Dependency Tags in the Source Editor Properties...12 Overview...12 Parameters...12 RSS Items...12 Access...13 Reminders...13 Log Overview...13 Accessing Page Parameters Title and Meta Tags...14 Custom Settings Binary Files...15 Overview...15 Basic Steps Editing MultiEdit Content Overview...18 Access Group Approver...21 Enforce Approver Bypass Approval Toolbar RSS Feed URL Type...21 Exclude Search...21 Exclude From Sitemap.xml...21 Modifying Access Settings Binary Files...22 Image Editor Overview...24 Accessing the Image Editor Image Editor Tools Resize Crop Rotate...28 Zoom Undo/Redo Final Notes Reminders...31 Overview...31 Creating a Scheduled Reminder Creating a Stale Reminder...35 Editing a Reminder...37 Binary Files...37 Page 3 of 37

4 Edit Overview Whether accessing a page through DirectEdit or when navigating the folder structure through the Pages list view, there are a variety of ways in which content can be edited in. Editable Regions Web page content is typically accessed through the editable regions on a page. When an editable region is clicked, the WYSIWYG Editor will appear. After clicking through to edit a page, the Edit view shows the editable regions of a page. The availability of an editable region is indicated by an Edit button, the design of which can be customized. The editable region buttons are shown on a page, either by clicking Edit from the Page Actions toolbar or Edit > Page from within the Pages list view. For more information, visit the Editable Regions page. Edit Page 4 of 37

5 Editing Methods in Pages (typically PCF or HTML files) and includes (typically INC or HTML files) are edited through the WYSIWYG or Source Editor; depending on the implementation, includes may only be able to be edited via the Source Editor. Page parameterscan also be edited Assets are edited through a plain text editor, mini-wysiwyg editor, or Source Editor depending on the type of asset. Images are edited using the Image Editor built into. The following editors/editing methods are available: WYSIWYG Editor What-You-See-Is-What-You-Get, or WYSIWYG for short, is the most common way users edit pages in OU Campus. The WYSIWYG editor allows for editing of pages similarly to the way a page is edited in a word processor. For more information, visit the WYSIWYG Editor page. For information about JustEdit, the new WYSIWYG interface released with version 10.2, visit the JustEdit page. MultiEdit MultiEdit allows form-controlled editing for XML and other structured content. Administrators can create form-based templates that present users with an easy-to-follow guide for adding content to a structured layout. Templates can include both style-free form fields and WYSIWYG content editing areas. For more information, visit the MultiEdit page. Source Editor The source code editor allows users to view and edit the actual source code of a given page. For more information, see the Source Editor page. Page Properties Page Properties allow a user to modify the meta data of a page, including the page's title, description, and keywords; custom template settings that have been configured for the page; and the access settings for the page. For more information, visit the Page Properties page. Image Editor The Image Editor allows images to be resized, cropped, and rotated directly in. Additionally, users can upload and edit an image in one operation. This helps ensure large images are properly resized before they ever reach the server. For more information, visit the Image Editor page. Edit Page 5 of 37

6 Source Editor Overview By default, level 9 or level 10 administrators have the ability to edit the source code of a file via the Source Editor. Source Editor privileges can be granted or restricted for users as follows: A level 9 administrator can be restricted access to the Source Editor. User levels 1 through level 8 can be allowed access to the Source Editor. Both of these settings can be configured by a level 10 administrator in the Restrictions panel of User Settings, found in Setup > Users. For more information on user permissions, visit the Users page. The Source Editor is different than the HTML Source Editor available through the WYSIWYG Editor; the HTML Source Editor only allows a user to edit the source code of the region which is currently being edited. The Source Editor will, by default, highlight the code based upon the syntax for the type of file detected. The Syntax drop-down menu in the Source Editor toolbar allows users to change the highlighting. When HTML or XML is selected in the Syntax drop-down menu, the Source Editor automatically completes the closing Source Editor Page 6 of 37

7 tag of an HTML or XML element. Selecting None from the Syntax drop-down disables this feature as well as removes any highlighting. Users can perform a regex find and replace from the Source Editor to edit source code. The regex behavior within the Source Editor is slightly different than the regex behavior in the Find and Replace tool, in that the Source Editor will perform a line-by-line search while Find and Replace searches the whole page. Find and Replace matches white space throughout the document. Source Editor will also provide auto-complete suggestions as you are typing, for ease and efficiency. The suggestions provided will vary depending on the option selected in the Syntax drop-down menu. The following syntax options will trigger auto-complete functionality: Javascript files: JS-related methods/syntax HTML files: HTML nodes/attributes XML files (PCF, TCF, TMPL and XSL): Proprietary OU nodes/attributes such as <ouc:div> and <ouc:editor>, HTML nodes/attributes, and common XSL nodes/attributes. CSS files: CSS properties/pseudo classes Accessing the Source Editor The Source Editor can be accessed through any of the following ways: From the Content > Pages view, check out the desired page. Select the Edit menu and choose Source. Open the page from the Pages list view and click the Source button in the Page Actions toolbar. Source Editor Page 7 of 37

8 Check out the page or click the Edit button, and then click the blue Edit Source button at the bottom of the page. Using the Source Editor The Source Editor contains a modified toolbar, which has different functions than those within the WYSIWYG Editor. The functions for the Source Editor toolbar are as follows: Save: This saves all changes made to source and exits the user from the Source Editor. The user will be taken back to the Preview view of the page. To save in place without exiting the Source Editor, use keyboard shortcuts (Ctrl+S on PC, Cmd+S on Mac). Save As: This allows the user to change the name, path, and extension of the file in order to save a copy. This is an alternative way to create a new file in the system. Undo/Redo: This allows a user to undo a change that has been made in the source code, or to redo a step that has been undone. Source Editor Page 8 of 37

9 Find and Replace: This allows the user to search for (and, if they desire, replace) text or code within the source. Searches can use a regular expression (regex) or simple text string. For more information about regex, see: Regular Expressions (RegEx) Go To Line: This will open up a box beneath the toolbar where a line number can be inputted. Inputting a line number will automatically direct the Source Editor cursor to the start of that line. Line Wrap: This button enables or disables wrap-around text. When enabled, text will be bound to the width of the Source Editor window. Lines of code longer than this width will continue on the next line (though a new line number will not be assigned). When disabled, lines of code longer the width of the window will be accessible via a horizontal scroll bar. Line wrap does not alter the code in any way, only how the user views it. Insert File Path: A user may insert a dependency tag for a file directly into the source code, if Dependency Manager is enabled. This button will open a modal that allows the user to select a file from any configured servers (e.g., staging, production, auxiliary sites, and alternative publish targets). The dependency tag will be inserted at the cursor's location in the Source Editor, so be sure to set the cursor at the desired location. Note that this function only inserts the dependency tag or link, and no other pieces of code. Insert Asset: A user may also insert an asset directly into the source code. This button will open a modal that allows a user to browse for a specific asset. The dependency tag will be inserted at the cursor's location in the Source Editor, so be sure to set the cursor at the desired location. Syntax: This drop-down allows the user to select the code syntax based on code type. A few of the available options at HTML, XML (default), CSS, and JavaScript. Theme: A user may choose between a large variety of themes, which will change the colors of the text and background. Increase/Decrease Font Size: Clicking each icon increases or decreases the font size of the Source Editor. Users can also use a variety of keyboard shortcuts in the Source Editor. The available keyboard shortcuts include: Ctrl (Windows)/Cmd (Mac) + S: Save-in-Place. Saves the content onto the staging server, but allows users to remain in the editor and make further changes. Ctrl/Cmd + A: Select All. Selects all content in the Source Editor. Ctrl/Cmd + D: Deletes the entire line of code on which the cursor is currently placed. Ctrl/Cmd + Z: Undo the last change. Ctrl/Cmd + Y: Redo the last undone change. Ctrl/Cmd + F: Brings up the Find and Replace tool for the Source Editor. Ctrl/Cmd + /: Comments out the currently-selected line(s) of code. This function is syntax-specific; the format of the comment will depend on the language selected in the Syntax drop-down menu. Shift + Tab: Auto-indent. Takes all selected text and indents it according to the nesting of elements. Ctrl/Cmd + [: Indents all selected code by one tab less. Ctrl/Cmd + ]: Indents all selected code by one tab more. Ctrl + Q: Folds the element on the current line, hiding child elements and other content, making the code easier to read. Source Editor Page 9 of 37

10 Before Folding After Folding Using Gadgets in the Source Editor Users are able to drag and drop images and videos from the Images Gadget and YouTube Gadget, respectively, into the Source Editor just as they would in the WYSIWYG Editor. When an image or video is added to the Source Editor from a gadget, the Insert/Edit Image or Insert/Edit Video modal will not appear; instead, a simple <img> or <iframe> tag will be added into the source with only the essential information included. A user must add other information (e.g., image description, dimensions, alignment) manually after the image or video has been inserted. Syntax Highlighting The Source Editor in automatically determines the correct type of document based upon the file extension. However, the need may arise to override the automatic behavior and display a document in a different style. When a user selects a different code syntax, the displayed highlighting is specific for that code base. The list of code syntax types available in the drop-down menu are as follows: 1. None (.txt): The first option, when selected, displays the the code without syntax highlight and without code complete. 2. HTML (.html,.tmpl,.jsp) 3. XML (.xml,.pcf,.tcf,.xsl,.rss,.xslt,.xsd,.dtd) 4. CSS (.css) 5. JavaScript (.js) 6. PHP (.php,.php3) 7. Python (.py) 8. VBScript (.vbs) 9. Perl (.pl,.cgi) 10.MySQL (.sql) 11.C# (.cs) Source Editor Page 10 of 37

11 Dependency Tags in the Source Editor Dependency tags are inserted into the Source Editor via the Insert File Path tool (for files, folders, or servers) or the Insert Asset tool (for assets). Once inserted, the Dependency tag appears as a tag surrounded by two curly braces, such as below: Dependency Manager also includes tracking and reporting broken links within the Source Editor. If a dependency tag is identified as broken,it is highlighted in red in-context so it can be easily identified and fixed. Source Editor Page 11 of 37

12 Properties Overview Properties refers to several ancillary items related to a file. The availability of functionality under Properties is determined by the specifics of the implementation, access settings, authority level, and file type. The file must be checked out to the current user for Properties to be visible in either the List View or the Actions Toolbar. The five possible items under Properties are: Parameters RSS Access Reminders Log Binary files have all properties available except for RSS. Parameters The Parameters screen allows users to edit basic metadata information and template-specific parameters for the checked-out file. While the available fields are dependent upon the template design and implementation for an institution, the metadata fields frequently include title, description, keywords, and tags. Typical configuration options in this panel control page layout and structure, as well as giving users the ability to enable optional editable regions or choose an image for the banner or image slider. For more information, visit the Parameters page. RSS Items If an RSS feed is assigned to a page or at the directory level, then an RSS item can be associated with the page. For more information, visit the RSS Feed Items page. Properties Page 12 of 37

13 Access User levels 8, 9, and 10 have the ability to configure access settings for a file. Level 8 users can only set access settings for content to which they have access. For more information, visit the Access page. Reminders Both a scheduled reminder and a stale reminder can set for a file. For more information, visit the Reminders page. Log Provides a list view of all actions previously performed on the file. For more information, visit the Log page. Overview Parameters can be used to control preconfigured aspects of a page, such as supplying meta tag content and keywords, as well as any custom settings that have been configured for the template. Page parameters are accessed from the Page Properties view. In order to access Page Properties, the page must be checked out to the current user. User levels 5 through 10 have the ability to edit the parameters of a page to which they have access. The available metadata and parameters in the Parameters panel depend upon template design. Some of the fields available during page creation also include parameters. The Page Parameters panel includes the Title and Meta Tags area and the Custom Settings area. Accessing Page Parameters In order to edit the metadata and configuration parameters for a page, Properties must be accessed. 1. Navigate to the Pages list view and check out the page. 2. Access the page parameters by one of two ways: Hover over Edit in the page row and choose Properties. Click on the linked path for the page, and then click the Properties button on the Page Actions toolbar. The included fields in the Parameters panel vary greatly from implementation to implementation, but will always fall under the Title and Meta Tags or Custom Settings headings. Properties Page 13 of 37

14 Title and Meta Tags The first area of Page Parameters contains the Title and Meta Tags heading, which frequently contains the following: Title: Allows users to create a user-friendly name for the page that is used to identify the content in the CMS, and is used for the title of the page that appears in a browser. Description: Allows users to provide a brief description of the page. Tags: Tags are used within to categorize pages and files so that it is easier to search for and filter them. If allowed, users may create new tags directly on pages. For more information about tags, visit the Tags Access and Tags in Setup pages. Note: because Tags are defined through the properties of each individual page, users are unable to apply tags to multiple pages at a time, save through the Tags Access settings of the directory. Author: Defines the user who created the content. Keywords: User-defined keywords that are used in searches to help find content and for SEO purposes. Custom Settings The Custom Settings heading contains any custom settings that have been configured with the template used to create the page. The options under this heading will vary depending on the template used. The available fields may include: Page Type: The ability for the page to be displayed as a one-, two-, or three-column layout Keywords: Choose from a set of predefined keywords to add into the page metadata using checkboxes. Properties Page 14 of 37

15 Additional Editable Regions: Optional editable regions that can be enabled or disabled for the page, such as Student Quotes, a Quick Links section, or a secondary content region. Image Slider Region: An editable region that, when clicked, will allow users to add an image gallery asset to the page in the form of an image slider (requires LDP to be activated for the site). Article Image Article Description Article Author Left and Right Column Options Once edited, changes can be saved by clicking the blue Save button at the bottom of the page. If the page is navigated away from before changes are saved, they will not take effect. Binary Files For binary files, the only field available under parameters is Tags. Tags function as they do throughout OU Campus, and are used to mark the files to make them easier to search for. Overview A MultiEdit region is a type of editable region on a page similar to an editable region that uses the WYSIWYG Editor. It is a way to quickly enter information for several fields without having to worry about layout or formatting, which is handled by the MultiEdit template. Accessing MultiEdit content is accomplished in a manner similar to accessing any editable region, except instead of clicking an Edit button, the orange MultiEdit button, found at the top of the page, is used. When viewing a MultiEdit-capable page in Edit mode, other Edit buttons might also be viewable, such as for an INC file for a navigation bar. MultiEdit is most frequently used for faculty pages and the faculty directory. The traditional implementation for faculty pages includes the index page for the directory which is auto-populated and is not usually edited. The individual faculty pages are used to build the index. Each faculty or staff member has his or her own page, which they can log in to and update. A user can also navigate the file structure to locate and edit the content. Note: If a web page has MultiEdit tags, JustEdit is disabled automatically for that page. Basic Steps Editing MultiEdit Content 1. Log in to via the DirectEdit link on a published page. 2. Navigate through the file structure in Content > Pages if necessary to find the desired page. 3. Check out the page. Click the orange MultiEdit button below the Page Actions toolbar. Properties Page 15 of 37

16 4. The MultiEdit Content panel is shown. 5. Edit the details as necessary. Certain fields may be text-only; others may include a filechooser to upload images, while others may include a mini-wysiwyg Editor for a faculty biography, for example. 6. Save and publish the page. Properties Page 16 of 37

17 Creating a New Faculty Profile When MultiEdit has been used to implement faculty pages, a Faculty Profile template is provided in order to create new faculty pages. This step creates the page that will be used in editing. After the page has been created, it can be edited to add additional information using MultiEdit. 1. Navigate to the Faculty directory. 2. Click New and choose the Faculty Profile template. Alternatively, use the drop-down indicator to select the Faculty Profile template from the menu. 3. For the Faculty Name field enter both the family and given name. For some templates, the Faculty Name is joined with the Designation to create the title on the actual page. 4. For the Designation filed, enter the title for the faculty member. 5. Edit other fields as necessary, including the file name (without adding an extension). Properties Page 17 of 37

18 6. Click Create. The next step is to edit the page to add the rest of the details. Each implementation is different, so the actual fields and field labels may vary. Overview Authority Level: Level 9 and 10 administrators can edit the access setting for any content. Level 8 users can change the access settings for content they can access to groups of which they are members. Properties Page 18 of 37

19 Access settings can be specified for an editable region, page, directory, and site. In particular, this topic covers page access settings. Note that access settings for a page can also be set by a TCF at the time of new content creation, if the template is so configured. If not explicitly set, access settings have default inherit settings as noted below. At the page level, the following access settings are available: Access Group Approver Enforce Approver Bypass Approval Toolbar RSS Feed URL Type Exclude Search Exclude from Sitemap.xml Properties Page 19 of 37

20 Access Group Determines the group with rights to edit the page. The default setting is Everyone. If the Access Group is set to Administrators Only, then only Level 9 or Level 10 administrators are able to access the page. Properties Page 20 of 37

21 The default value is inherited from the parent directory, but the TCF can be configured to assign an Access Group or allow for the choice of an Access Group at the time of page creation. Approver Assigns an approver for the page; the default value is inherited from the parent directory. Setting the approver for a page is optional. Setting an approver revokes publishing rights from all users who are not in the Bypass Approval group or a Level 10 administrator. Setting the approver for a page overrides a user #s default approver. Assigning an approver at the page level still allows users to choose the approver for the page; use Enforce Approver to disable the drop-down that would otherwise allow the user to choose an alternative approver. The TCF can be configured to assign an approver at the time of page creation. Enforce Approver Enforcing an approver is optional even when an approver is set. When enforcing an approver is set, it requires that a page be sent to the designated approver. Select the Enforce Approver checkbox to ensure that a user may not choose an alternate approver from the drop-down. Bypass Approval Selecting this option allows members of the assigned group to override an assigned approver and publish the content directly. If not assigned, the default is level 10 administrators. Toolbar Assigns a previously created custom toolbar to a page. The default is to inherit from the parent directory. A toolbar can be assigned to a page, which overrides any toolbar assigned to a user, directory, or site. This can be helpful for unique content areas, such as a navigation file. It is important to note that if a custom toolbar is selected in this drop-down, all users, including level 10 administrators, will be forced to use this toolbar. The TCF can be configured to assign a toolbar at the time of page creation. For more information about creating custom toolbars, visit the Setup Toolbars page. RSS Feed Assigns a previously configured RSS feed to a page. Once associated either through access settings or automatically with a TCF, RSS items can be created for the feed. The default is no feed assignment, but the TCF can be configured to assign a specific RSS feed or allow for the choice of one at the time of page creation. URL Type Determines the URL type to use for the page. The default is to inherit the URL type from the site settings (or parent directory if a different option had been configured there). Defines the URL structure for when links are inserted on a page. The options are Inherit from Site Settings, Absolute, Root Relative, or Page Relative. Generally, it is best to leave this value at the default and define the URL type in the site settings. Exclude Search This excludes a page from Quick Search results. When Exclude Search is selected, the page is not indexed. This will not remove any content that has already been indexed from the search results, unless the option to apply recursively is available and selected, and it only excludes that folder or page, but not subfolders. This selection will not affect the results when using the Find and Replace tool. Exclude From Sitemap.xml This excludes the page from the XML sitemap when generating a sitemap.xml. Properties Page 21 of 37

22 Modifying Access Settings Page access settings can be changed using two different methods. To modify page access settings: 1. Navigate to the Pages list view via Content > Pages in the global navigation bar. 2. Hover over the row of the target page and select Access from the Edit menu. The Page Access Settings modal will appear. 3. Another method is to select Properties from the Edit menu or click on the linked file path to enter the Preview view. These views show the Page Actions toolbar. From the Page Actions toolbar, select Properties. Then, from the left navigation panel, select Access. The Access Settings panel will appear, which contains the same information as the modal mentioned above. 4. Change any necessary information and click Save. Binary Files The Access Settings for binary files are slightly reduced. Properties Page 22 of 37

23 Access Settings for binary files are comprised of: Access Group Approver Enforce Approver Bypass Approval Exclude Search Exclude from Sitemap.xml They function in the same way that access settings for pages do. Properties Page 23 of 37

24 Image Editor Overview The Image Editor allows images to be resized, cropped, rotated, and zoomed directly within. Images can be uploaded and edited all in one operation. The ability to edit an image helps ensure large images are properly resized before being published to the production server. Additionally, images can be saved and renamed. Access to the Image Editor is dependent on user level. Those who can upload files can use the Image Editor to upload images and edit existing images, but cannot overwrite any existing image with the same file name. Those with overwrite permissions are able to replace existing images. The Image Editor can be accessed using the following methods: Clicking on a linked image name within the Pages list view Clicking Upload and Edit from the Upload modal when uploading an image in the Pages list view When inserting images into an editable region from the Insert/Edit Image filechooser while in the WYSIWYG Editor When inserting images into a mini-wysiwyg editor from the Insert/Edit Image filechooser while editing or creating a new Web Content Asset When inserting images on a page using the Source Editor For more information about the Upload and Edit process, visit the Upload and Edit page. LDP Image Galleries are another way users can add images to a site in the system. However, this function is not related to the standard Upload and Edit Image feature and requires that Live Delivery Platform (LDP) be enabled. For information about creating LDP Image Galleries, visit the Image Galleries page. Image file types support by the Image Editor is browser dependent. The following file types commonly used for web pages can be edited and saved with the Image Editor with the most commonly used browsers: JPG/JPEG PNG GIF Image Editor Page 24 of 37

25 BMP For a complete reference of browser support for image formats, see: Accessing the Image Editor The Image Editor can be accessed in three main ways: Click the hyperlinked image name in the Pages list view When uploading an image, click Upload and Edit from the Upload modal When adding an image to an editable region, the source of a page, or in a mini-wysiwyg Editor and uploading from the Select Image filechooser Image Editor Page 25 of 37

26 Image Editor Tools From the Edit Image screen inside the Image Editor, the following functionality is available in the Tools menu: Resize Crop Rotate Zoom Undo Redo As the image is edited, an estimated file size is shown underneath the image panel. This size will change as the image is resized and cropped. Resize The Resize tool includes the ability to specify a new width and height for the image. The original ratio for the image dimensions can be kept intact by selecting the Preserve Ratio checkbox. Image Editor Page 26 of 37

27 Crop The Crop tool can be used to crop the image, either by selecting a predefined aspect ratio or by determining a custom crop size. When Custom or any of the predefined ratios are selected, a crop box will appear. Users can then adjust the crop for the image by dragging the crop handles located on the edges of the crop box. Clicking the Swap width & height checkbox will swap the dimensions of the crop box width and height (e.g., a crop box with dimensions of 150x300 pixels would swap to 300x150 pixels). Image Editor Page 27 of 37

28 Rotate The Rotate tool rotates the image 90 degrees in a clockwise direction with each click. Image Editor Page 28 of 37

29 Zoom The Zoom tool can be used to manually enter a percentage of the original image size to be displayed in the Edit Image panel for editing. The plus and minus magnifying glass buttons may also be used to increase or decrease the viewing size. Zoom does not alter the size of the image on the staging server; it is only to aid users in the Image Editor. The Original button reverts the image to the original size. The Zoom to Fit button resizes the image to fit into the panel for viewing. Image Editor Page 29 of 37

30 Undo/Redo The Undo and Redo functionality is available after performing another editing function. Undo reverts the last function performed (one level back). The Redo function reapplies the last function removed by the Undo tool (one level forward). Final Notes The edited image must be republished in order to appear correctly on the rendered webpage. This may be initiated with a page publish by selecting the checkbox to publish unpublished dependencies. Or it may be necessary to manually publish the image. If the image does not appear correctly, refresh the browser and/ or clear the browser cache as the previous iteration of the image may have been saved by the browser. This action can be found in various places in browsers' settings and for some browsers/platforms, this can be accomplished by pressing CTRL+F5 (Chrome), CTRL+R (Firefox and IE), or CMD+Option+E (Safari). Otherwise the edited image may not appear as expected. When an image is edited through The Image Editor in, it will be recompressed once it is saved. When using lossy file formats such as JPG, this can cause a visible degradation in image quality, especially when an image is edited multiple times in. As a best practice, crop or resize images to the exact size needed on the page before importing them into. Furthermore, using images saved in a lossless file format (such as PNG) in the Image Editor will avoid losses of quality due to recompression. The image size is dependent on two factors: the browser and the amount of memory allocated to the browser by the parent machine. In testing a fairly large image, x 3955 pixel (27 MB), was used and rendered in 198 ms. Performance of image rendering is dependent upon each individual user's machine and Internet connection. In short, every time a user tries to load an image, large or small, jpeg or any other extension, the image editor relies on the browser to provide the pixel information. If working with an image that cannot be edited, log out of, quit and relaunch the browser. This will free up browser-allocated RAM and may resolve the issue. Image Editor Page 30 of 37

31 Reminders Overview Two types of reminders are available in : scheduled and stale. Reminders can be set on pages and binary files. Reminder notifications can be sent to a user or a group, and can be sent periodically or on a one-time basis. All user levels can set reminders for content to which they have access, and they have the ability to send the reminder notification to themselves or a group to which they belong (except for the Everyone group). Level 9 and 10 administrators can send a reminder to themselves or to any group. A scheduled reminder is used when there is a specific date and time when the reminder message must be sent. An example of a page type that might use a scheduled reminder is a tuition page. If the tuition is updated on a yearly schedule, a reminder may be set for a week prior to the tuition change and set to repeat on a yearly basis, if necessary. A stale reminder is used to make sure that content on a page is being updated periodically. It is important that users understand how the timer is reset for stale reminders. When a version of a page is created or published, regardless of the type of publish (e.g., page publish, directory publish, site publish, asset update publish, Dependency Manager publish, or revert) the last published date and time is reset and the timer on the stale reminder starts over. In other words, a stale reminder notification is sent based on the date/time stamp of the last publish or version creation, rather than based on a specific calendar date. Scheduled and stale reminders can be set from the Pages list view or the Page Actions toolbar (via Properties > Reminders). Both reminder types can be associated with the same page at one time. A reminder can be set even if the content is checked out to another user. Once a reminder has been set, the Reminder icon is shown in blue on the Edit menu under Options in the Pages list view. Set reminders are also shown on the Scheduled Actions report. Creating a Scheduled Reminder The following example makes use of a PCF, but a reminder for a binary file can be set in a similar fashion. To create a scheduled reminder for a file: 1. Navigate to the Pages list view. 2. In the file row, hover over Edit and choose Reminders from the drop-down menu. This shows the Reminders modal where both a scheduled or stale reminder can be set. Reminders Page 31 of 37

32 3. Select the checkbox next to Set Scheduled Reminder. Reminders Page 32 of 37

33 4. Select the Date for the reminder to begin. Click inside the date field or on the calendar icon for a date picker from which the date may be selected. The date may also be entered manually. 5. Select the Time for the reminder. Clicking inside the field or on the clock icon will bring up the time chooser. Click the arrows to choose hour, minute, and AM or PM as necessary, or enter the time in the field manually. Reminders Page 33 of 37

34 6. Use the Repeat Every field to create repeating reminders. Add a number in the field and then select the frequency from the drop-down menu. 7. In the Notification section of the modal, select a group to which the reminder will be sent (alternatively, choose (Myself) to send the message to yourself only), enter in the Subject and Message of the reminder, and select whether a copy of the reminder should be sent to each user's external in addition to their Inbox in. Reminders Page 34 of 37

35 8. Click Save. Creating a Stale Reminder A stale reminder is triggered when a page has not been updated for a set amount of time. Simply select the time period, add a message and recipient, and choose whether recipients will also receive an to their external accounts when a page becomes stale. To schedule a stale reminder: 1. Navigate to the Pages list view. 2. In the file row, hover over Edit and choose Reminders from the drop-down menu. This shows the Reminders modal where both a scheduled or stale reminder can be set. Reminders Page 35 of 37

36 3. Click the Stale Reminder tab and select the Set Stale Reminder checkbox. Reminders Page 36 of 37

37 4. The Last Published date and time is displayed. 5. In the Stale After field, enter a number and select the period of time to define the stale interval from the drop-down menu. 6. In the Notification section of the modal, select a group to which the reminder will be sent (alternatively, choose (Myself) to send the message to yourself only), enter in the Subject and Message of the reminder, and select whether a copy of the reminder should be sent to each user's external in addition to their Inbox in. 7. Click Save. NOTE: The stale page reminder checks from the last published date and time, not the date and time at which the stale reminder was set. After a stale reminder has been sent, the reminder will continue to send until the page has been published again. The length of time between the first reminder and subsequent ones depends on the length of the stale reminder itself: for example, if the page is set to be stale after one week, will send a stale reminder every week after the initial reminder until the page is published. If the page is set to be stale every two months, will send a reminder every two months after the initial reminder. Editing a Reminder Once a reminder has been created, the details can be modified at any time by clicking on Reminders in the Edit menu of the item. Reminders can also be deactivated at any time. To deactivate a reminder: 1. Navigate to the Pages list view. 2. Hover over the item row in the list view, and from the Edit menu, select Reminders. 3. Clear the checkbox for Set Scheduled Reminder or Set Stale Reminder to remove that reminder from the page. 4. Click Save Changes. Binary Files Reminders on binary files function the same way that reminders on pages do, and are accessed the same way. Reminders Page 37 of 37