What's the Latest in OrchestraCMS?

What’s New in OrchestraCMS?

February 2023

Fixes

• Fixed an issue where a $ (dollar sign) in a rich text content made with the Content Template Creator would result in an error message when the content was rendered in Preview or on the Live Site
• Fixed an issue where a change in the Bridgeline server URL would cause customers accessing OrchestraCMS to encounter a licensing error preventing access to the application.  You will need to add a new Remote Site Setting in Salesforce Setup for the URL https://lmapro.bridgeline.com.  This is the new license verification URL.
• Fixed an issue where a change in the customer's Salesforce URL would prevent certain content from being edited properly in OrchestraCMS
• Fixed an issue where quotes in the name of a content item would prevent the item from showing up in the page editor view
• Fixed an issue where more than 1000 custom objects in Salesforce would prevent the editing of a form in OrchestraCMS
• Fixed an issue where the menu editing UI was unusable at certain screen resolutions.

October 2021

NEW FEATURES!

• Added bulk sharing of of pages and content.  You can now select multiple pages or content and use the Share option in the Actions panel to share all the selected items at one time
• Simplified error messages returned by Salesforce validation rules when creating pages/content

August 2021

Fixes

• Fixed an issue where content types configured with a link selector to an external page/file display the text 'undefined' in front of the link URL
• Fixed an issue where deployment of guest sharing rules from OrchestraCMS was no longer working

March 2021

Fixes

• Fixed an issue with content_template_selector jQuery widget which prevented it loading.
• Fixed an issue with menus where they could not be edited after they were created.
• Fixed an issue preventing Google ReCaptcha on OrchestraCMS forms from loading.  Requires customer signup with Google for their own ReCaptcha keys at https://www.google.com/recaptcha/admin.  You must then contact Bridgeline Support and provide those keys so they can be included in some backend custom settings.
• Fixed an issue where custom settings related to OrchestraCMS user settings were not getting removed when users were removed from all OrchestraCMS site profiles.
• Fixed an issue where clicking the detail link in a Lightning article when viewing in Draft mode took the user to the latest published version of the article instead of the draft version.  It now goes to the latest draft version.
• Page listings in OrchestraCMS were incorrectly displaying the Last Modified By field.  This has now been resovled so that cache refreshes no longer impact this data.
• Send for Approval is now prevented if the minimum required content is not met for a panel on the page.

February 2021

NEW FEATURES!

• Functionality that will list invalid links within content.
  • Page status will display on links in Link Selectors
    • A red exclamation point for expired pages
    • A yellow ellipsis for unpublished pages
    • Note: Published pages, media, or external links will have no icon
  • Generating a report within content tab will now contain an additional column in the CSV when selecting “Has Expired Page Links”
    • TRUE: If the content has links to expired pages
    • FALSE: If the content has no links to expired pages
• Added the ability to allow public tags to be a mandatory field on pages in OrchestraCMS
  • Must be enabled in OrchestraCMS Setup > Tags by selecting “Require Public Tags to publish pages”
  • Includes new profile permission “Ignore required page settings when publishing" allowing users to bypass mandatory tags when publishing
• Added an attribute that will allow admins to apply a minimum number of content items that must exist in a page panel.
  • The “panelMinimum” attribute makes pages require a minimum amount of content to exist in a panel before the page can be published. (eg. PanelMinimum=”1”). These must be added to the cms:Panel markup in the Visualforce page templates to be in effect.
  • Note: Users with a profile where the “Ignore required page settings when publishing” permission is selected can bypass the minimum content requirement to publish pages.
• OrchestraCMS jQuery version updated to 3.5.1
  • In OrchestraCMS Setup > Details there is now the option to set the version of jQuery used by OrchestraCMS. After making changes you must perform a site wide page cache refresh to use the updated setting. The options are:
    • 1.12.4 - The version of jQuery currently embedded in OrchestraCMS
    • 3.5.1 - Most current version of jQuery
    • 3.5.1 + migrate - jQuery migrate plugin for when you're unable to currently switch from all the methods the new jQuery deprecates
    • custom - Allows you to enter a URL for any jQuery you want

Fixes

• Fixed an issue with taxonomy categories not displaying when checking applied taxonomies on content.
• Fixed an issue with failing RSS URL with parameters.
• Show in Preview in the Actions panel was incorrectly labelled.  This has now been changed to Hide in Preview to properly reflect the intended function.
• Fixed an issue where could not create or open content in IE11.
• Fixed an issue where previewing content would sometimes result in a Content is NULL message.
• Fixed an issue where removing languages from a page would result in the page not being added to the search index.
• Added processing improvements for parsing large taxonomies
• Fixed an issue where clicking Clear button while editing a menu item would reload the page
• Fixed an issue with authentication redirects when enabling Salesforce critical update to remove instance names from URLs
• Added new permission set for site guest users ocms_SiteGuest to address Salesforce change preventing guest users from being assigned permission sets with Edit permissions to Objects included.
• Fixed an issue where the Salesforce critical update “Disable Access to Non-global Controller Methods in Managed Packages” would break OrchestraCMS lightning component inline editing.

October 2020

NEW FEATURES!

• Enhanced Celebros Search Configuration for Visual Force Communities
  • New fields added to Content Types setup allowing you to specify a search and detail template per type. This can be setup via RenderingAPI by adding 'templateTypes' to listParameters. The two possible values are 'Detail', and 'Search'. You can request both at the same time.
  • Allow pre-filtering of Celebros Search Results. Visual Force search is now frontend driven (javascript instead of apex). Pagination uses the code from Lightning so rendering should look similar. Search edit will let you choose refinements from Celebros to automatically filter user's searches.
  • Added an option to use GET requests for Basic Form content template to work both server-side and client-side.
  • Added filters to Visual Force search
  • AutoComplete now uses detail template. Content View page properties now have a fallback option. When checked, if no other template is specified, it will try to load the detail template. If there is no detail template, it tries the default. If no default, returns empty.
• Updates to support a Salesforce Critical Update
• Updated to allow selection of jQuery version.
• Additional updates made for a future Saleforce Update for Guest permissions.

Fixes

• Fixed an issue in Lightning where Fallback to English failed and renders blank content when viewing other languages.
• Updated issues with Search Indexing
• Fixed an issue with getSocialIDData when set to private throwing the query over the limit due to a recursive loop
• Fixed an issue with Forms attaching Attachment to OrchestraCMS content record

July 2020

Features

• CKEditor Image Widget no longer inlines image sizes by default.

Fixes

• Celebros Search Integration Support
  • Celebros Search is an intelligent site search offering that provides Natural Language Processing and machine learning to present the most relevant results to your endusers. The search solution accurately interprets and matches longtail keyword searches using over 250 semantic algorithms to increase discoverability and drive conversion.
    
  • Support for Celebros Search Analytics in both Visualforce and Lightning sites.
  • Added a detail page selector to the Celebros Search Results template to enable content templates that do not use the page selector widget.
  • Added a Celebros auto-complete option to the basic search form for Visualforce sites.
  • NOTE: Celebros Search requires additional license fees. Please contact our Customer Success team for more information: success@bridgeline.com
• SearchAPI now supports multilingual values for all properties that are stored as multilingual.
• Admins can now refresh the search index without resorting to anonymous apex. There is now a button within Search Index setup page to do this automatically.

May 2020

Fixes

• Fixed an issue within the Lightning core components that caused issues with the cache not being cleared when a user changed their information within Orchestra.

Features

• Ability to upload Word documents
  • Added a File Upload button within the WYSIWYG editor to give authors the ability to push word documents for document content. This allows users to upload a Word document (.docx) directly in OrchestraCMS, rather than using the external authoring plugins or copying & pasting a document into CKEditor. The same basic styling supported by external authoring plugins is supported – paragraphs, bold/italic/underline, headings, lists, links, tables, and images. Images should be uploaded to the media library.
• Improve VisualForce search results
  • Currently, the implementation of search refinement only covers the scope of content type selection for search result rendering. A Content Type selector field will be visible in the CelebrosSearchResults content editor. All available, listable content types will be visible and selectable. Once the content is published, any page with that search results content will display the results respective to the selected content type(s).
• Added the ability to pass custom attributes through core Lightning components.

March 2020

Important Notes

• Salesforce.com is rolling out a security update on April 1st, 2020 that will disable guest user access to records in Salesforce by default. The Salesforce setting "Secure guest user record access", found in Salesforce Setup under Sharing Settings, prevents unauthenticated users from accessing records in Salesforce. Sites powered by OrchestraCMS use underlying Salesforce records within the OrchestraCMS data model to provide content management features through the application. In order for public (unauthenticated visitors) to access pages and content on sites powered by OrchestraCMS, site guest user sharing rules must be generated to share records within the OrchestraCMS custom objects with site guest users. This process is now automated through OrchestraCMS.
  • Please open a case with Bridgeline Technical Support for any questions or concerns.

Fixes

• Secure Guest Record Critical Updates
  • A new profile permission has been added: Secure Guest Access. Administrator profiles are granted this by default. The permission allows access to the Secure Guest Access setup page, where OrchestraCMS will identify any potential issues between the guest sharing rules that exist in the org versus what OrchestraCMS expects for default functionality.
    • All sites will be checked against, including intranets
    • Missing rules, duplicate rules, and modified criteria are checked for. Mismatched criteria are not necessarily a problem and may be part of your implementation.
    • Rule criteria will differ depending on whether private sharing is enabled
  • This page will generate the proper sharing rule metadata for all your sites. You can choose to download this metadata and deploy it via your own process, or allow OrchestraCMS to use the MetadataAPI to deploy or delete the sharing rules. OrchestraCMS will only deploy or delete sharing rules following a specific naming scheme to avoid collisions or unintended deletes.
  • For orgs with private sharing enabled, sharing with guests is now handled differently behind the scenes, but will function in a familiar way for content authors/editors
    • Upon upgrade of OrchestraCMS, an administrator should visit the package Configure page and run several conversion features
      • Records owned by the application user are not properly shared with guests. The configure page provides a way of changing the ownership of these records.
      • Existing share records for guests will prevent content from being versioned or edited. These share records need to be converted via the configure page.

Features

• Celebros Lightening Search Results Integration
  • View Celebros Search Integration Guide
  • The Search Results lightning component has been upgraded to allow for more search providers. Search providers are interchangeable components that can be created during an implementation, or provided by us in the OrchestraCMS package.
• Enhanced Targeting to support TargetDataSources
• View Enhanced Targeting Guide
• Made Targeting content for a request less restrictive (instead of just mapping fields on the User object)

December 2019

Important Notes

• Salesforce now sets "Default External Access" for OrchestraCMS objects to Private by default within Sharing Settings. This appears to only affect new installations. What this means is that after a new installation, or before going live with a new installation, a System Administrator will need to set all the OrchestraCMS objects in Sharing Settings to match the "Default Internal Access" for the same object. This is found in Setup > Security Controls > Sharing Settings.

Fixes

• Fixed an issue related to the inability to pin Recent Pages within the Overture Tab.
• Fixed an issue that caused the preview language within Pages to be hardcoded to English.
• Fixed an issue related to adding new content to a page - after completed, the page is not updated and appears like no content is added until the page is refreshed. Now the content will display without refresh.
• Fixed an issue that related to subscription pending jobs not being created immediately after a job is processed.
• Fixed an issue that caused CSV report download issues within Internet Explorer 11.
• Fixed an issue that relates to using "existing" as a Rendering API Origin sort type yielding incorrect results.
• Fixed an issue related to unpublished expired pages displaying different statuses. Now it will display “Published Expired” or “Unpublished Expired” status on all manager UIs.

Features

• Celebros Site Search Integration
• Enhanced Life Cycle Management Events
  • Ability to trigger events on content saved for future publish. Events should fire for the following actions:
    • Content being published which has a published start date in the future. E.g. when Publish is clicked through the UI. The event fires immediately, and CONTENT_PUBLISHED will fire when the content actually goes live.
    • Page being published which has a published start date in the future. (See above)
    • Page published or going live.
  • Ability to trigger events on approval. This includes events fired when actions take place:
    • Page or Content is sent for approval
    • Page or Content is approved
    • Page or Content is rejected
  • Ability to trigger another event on publish. This includes when content or pages are:
    • Saved
    • Newly versioned
    • New revision
    • Cloned
    • Created
• Added a notification confirmation that existing content was added to a page.
•  

October 2019

Fixes

• Fixed an issue related to incorrectly resolved links which replaces the relativeURL value at the time that it is rendered.
• Fixed an issue that caused expired pages to still show up on live sites. The behavior should now work as expected – When the page is expired, the page will no longer be served up on the live site.
• Fixed an issue related to the button not updating from ‘Cancel’ to ‘Ok” after deleting pages, content, or media.
• Fixed an issue related to the overture tab being unresponsive in the IE11 browser.

Features

• Updated OrchestraCMS button and menu colors to match as closely to Bridgeline style guide while meeting accessibility guidelines. Also includes the newly branded OrchestraCMS logo.
• Added support to upgrade systems with more than 50 sites
  • Note: On upgrade, only 50 sites will be upgraded.
  • The "Configure" link in installed packages will list if any other sites need upgrading. These can be upgraded by running the ApplicationUpgrader manually

September 2019

Fixes

• Fixed an issue related to accessing sites with incorrectly-cased site names.
• Fixed an issue where the “Performed by” field was being overwritten by revisions. New fields added to content and page objects to store the date and user who performed the new version, revision, clone, or publish action. Please note that operations performed prior to this update will say “Data Unavailable”.
• >Removed Pages within the description within Add Target dialog. Now it only says “Content”.
• Within a published class-styled menu, the pop-up menu for individual menu items will no longer allow the ability to type in any dialog boxes while editing a node. In addition, it no longer allows the user to choose to delete menu items.
• Updated the text within More Actions of a Page Editor from “Add a Page Template” to “Page Template”.
• Dialogue text has been updated to provide the user with more clarification on the confirmation for “Clone Profile” – “Are you sure you wish to overwrite ‘All Other Profiles’ with this one?”

Features

• Added Celebros Site Search integration as a better alternative to salesforce.com site search with setup UI for easy configuration
• Subscription API allows subscriptions to be listed, created, deleted, and modified. It also allows email schedules to be listed.
• Updated the embedded version of jQueryUI to version 1.12.

July 2019

Fixes

• Fixed an issue where Menu Breadcrumb displays incorrectly when Menu has linked submenus.
• When changing the target name, we now ensure that the new name for the Predefined target is also updated in the target's corresponding Filter__c record.
• The JSON Data Template no longer shows in add content for help and advice.

Features

• When subscribing to more than one taxonomy category with the same schedule (i.e. Weekly), users should only get one notification email containing a list of unique content for that schedule.
• Content Types and Content Templates that are required for lists are now preloaded.
• When using the Lightning Editor as a user with a Publisher license, you are now permitted to publish content.

May 2019

Fixes

• When the Salesforce Critical Update "Add a Namespace Prefix to Query Parameters and pageReference.state Properties" is enabled in Salesforce Setup > Critical Updates, URL parameters are no longer removed from internal URLs.
• Fixed an issue where a "cms:Too many SOQL queries: 101" error would be displayed in the content editor when a large number of targets were added to content.
• When using Lightning Components, URLs to Amazon S3 media library in the content editor were being constructed incorrectly. This has been fixed.
  • The changes below are now required and will need to be updated in all custom components. All changes should be tested in a sandbox prior to deploying to production.
    • Image urls no longer need the siteUrl prepended.
      All custom components will need to be adjusted.
    • Example - This: <img alt="" src=" {!v.hostSiteBundle.siteUrl + v.contentAttrs.ImageId}" />
      Becomes: <img src="{!v.contentAttrs.ImageId}" alt="" />
• If you are using AmazonS3 Media Library, in Community Builder, Content Security Policy (CSP) Settings must be set to "Allow Inline Scripts and Script Access to Any Third-party Host".
• Fixed an issue where a "Apex heap size too large" could occur while previewing Search Form content.
• Custom detail page URLs are now constructed correctly in Lightning Experience.
• When hovering over some OrchestraCMS menu items, the chevron was too light. This has been darkened.
• When applying a filter to a Media Library, clicking the folder name value in the search results now takes you to the folder where the media resides.

Features

• In Lightning, when using the Approval Process in the Inline Editor, editors now have the ability to add a comment and specify a priority when sending for approval.
  
• Interacting with content within an OrchestraCMS Page has been simplified:
  • Only one status icon per content (no more Pending Approval and Unpublished)
  • Draggable area on content item includes the title now
  • Panel Add Content menu no longer appears when clicking on content item
  • Panel header hover menu no longer hides itself when you select an action
  • Edit and Trash icons had been added and now have a hover state.
    
• SVG image files are now supported in the Media Library preview window.
• An indicator has been added to display when logged into a Sandbox Organization.

April 2019

Fixes

• We fixed an issue where an error "System.LimitException: cms:Too many queueable jobs added to the queue: 2" could be encountered when upgrading from an older version.
• When providing a custom override body to a lightning component, the override body is now correctly used when no data is returned. (Previously nothing would be displayed.)

Features

• A new field labeled "Search Placeholder Text" has been added to the Basic Search Form template. Any text added to this field's textbox will be used as the placeholder text for the search box when it is rendered.
• We added the ability to deep link to content loaded by a dynamic content loader, as well as a specific article when using an Inline Detail view.
  • Deep linking can be activated within the Taxonomy Loader Properties Panel for the Taxonomy Menu Properties Panel by enabling the "Enable Deep Linking" checkbox.

• There are new performance improvements in Lightning Components. Live site visitors can cache page content locally for faster subsequent load times. There is an option on the Dynamic Content Loader/ Dynamic Content Viewer / Static Content Loader / Taxonomy Menu component configurations to select Enable Session Cache. The caches expire when the user's session ends (closing the tab or window).
  

March 2019

Fixes

• Content that uses a future expiry date now correctly updates the status field in the Search Index record.
• The Dynamic Content Viewer Lightning component now loads content based on URL when inside a Lightning App page. (Previously this only worked in Lightning community pages.)
• When using the RenderingAPI, content is now retrieved if one of the ad hoc targets applied to the content is a value that is passed within the adHocTargets list parameter.

Features

• A new flag 'orBetweenTargetFilters' has been added to the RenderingAPIRequest. If true, it performs an OR operation between the collection of predefinedTargets and the collection of adHocTargets. If false, it performs an AND operation between the collection of predefinedTargets and the collection of adHocTargets. (This is only applicable if you have predefinedTargets and adHocTargets parameters specified.)
• The target bundle within a content bundle has been updated to include a map of filters.

February 2019

Fixes

• Fixed an issue that could occur when a menu on a master page has a target applied to it. In this case, the active, firstActive and lastActive classes were not being applied when the Smart Active Items of the menu is selected and page caching is enabled for the page template.
• Search index records for pages now respect the setting for enabling unique URLs.
• Fixed an issue where a "Too many SOQL queries: 101" error could occur when attempting to add a user to a profile.
• The Email Link property of a page is now correctly used for links in a publication email.
• While working in a sandbox, published or expired content could not be deleted if the sandbox was refreshed from a production org. This has been corrected.
• A new sort order has been added to taxonomy loaders. "Publish Date" can now be used to ensure that loaded items are displayed by the most recently published items first.
• Fixed an issue where inline authoring was skipping the approval process when new content was being created.

January 2019

Fixes

• The behaviour of the ocmsStart parameter has been corrected.
• Mail-out schedules are now only shown in the OrchestraCMS Site where they were created.
• Index records for all pages, content, and media are written to the Search Index object when published, regardless of whether the user has access to the page where the media or content resides.
• We fixed an issue where images and media links were not correctly resolved when using a site-prefixed community.
• We fixed an issue where the Lightning Inline Editor could become unresponsive when editing content that uses a template created with Content Template Creator and containing an attribute that is a Single Picklist in the content editor.
• Emails sent by OrchestraCMS to internal pages should now resolve to the correct page.
• We resolved an issue where expired content would always remain hidden if users had activated the "Hide Expired Content" in Manage Content, as this functionality was moved from a setting to the filter menu for pages and content.
• We made enhancements to Edit Pages so the "Click to add" text no longer overlaps the content that was added.
• We resolved an issue in Firefox where, within OrchestraCMS, items within a dropdown menu in the search bar could not be selected.
• In regard to the Lightning inline editor, images within the rich text editor's "Summary or Body" area are no longer distorted.
• Elements within the rich text editor that have a properties dialog now display this dialog upon right-clicking the element.
• When creating content in OrchestraCMS by authoring in lightning, translated taxonomies appeared duplicated when using the "APPLY CATEGORIES TO YOUR CONTENT" step. We resolved this.
•  

Features

• Previously, a record would be written to the Search Index object when files uploaded to a media library had associated metadata. This has been changed to ensure that a Search Index record is always written when a file is uploaded.
• The Translate Categories dialog has been updated to be consistent with the rest of the UI.
• Added the ability to determine all the pages that content resides on. When calling the Search Index API methods for getItem or getItems, you can pass an includePagesForContent parameter with a value of true. The response will have a return value of pages that returns a list of pageBundles, one for each page the content is on.
• We changed the Search Index behavior to ensure that a record is written for each page where content resides. Past behavior was to write only one record regardless of the number of pages the content was on.
• The type return value for getItemList method of the Search Index API now returns the file extension (.png, .jpg, .pdf, etc) of the media library files.
• A "Rename Category" action has been added to the node pop-out menu within the Taxonomy Menu editor.

December 2018

Fixes

• Fixed an issue in IE11 which prevented Content Loaders from loading content.
• If a thumbnail was saved for a page template in an older version of OrchestraCMS (no longer possible), a "List index out of bounds" error could occur when changing the page template. This has been resolved.
• Resolved an issue where an "Error updating available user(s)": message might be displayed when attempting to add or view users from within an OrchestraCMS profile.

November 2018

Fixes

• When using the Rendering API, whitespace contained at the end of a content cache could prevent the cache from being used to render the content. This would result in poor performance when rendering the page. One additional action that is required is to regenerate content caches.
  • In Setup, under the Cache section, select Content. Refresh Level 1 and Level 2 caches.
• When previewing a page with a menu, under certain conditions users could be presented with a "Maximum stack depth reached: 1001" error. This has been fixed.
• We corrected an issue where taxonomy menu nodes were being incorrectly displayed as the open and active node. (This could occur when two different parent nodes had child nodes with the exact same name.)
• When adding new content to a List Fixed content item, an empty row is no longer added.
• The searchContent method of the FilteringAPI now allows multiple sort orders. For additional information, please visit https://developer.stantive.com/Filtering-API .
• The originIds List Parameter now accepts either a 15- or 18-digit ID.

Feature

The Taxonomy Editor has been enhanced and updated.

Drag and drop capabilities

If you hover over a single category, then click and hold, this displays the "grab handle" on the right side of the node. If the desired location in the tree is already expanded, you can move this node anywhere within the entire taxonomy tree.

Taxonomy Node Menu

The node menu has been updated.

It shows these options:

October, 2018

Fixes

• While using the Read More feature of a dynamic taxonomy loader, the screen position prior to clicking Read More is now remembered.

• Commas (%2C) contained within taxonomy leaf names are no longer being replaced with a forward slash (%2F) when generating URLs.

• Translated taxonomy categories, when double-clicked, will now show the translated taxonomy category. Previously, the default language translation would be displayed.

• Translatable labels are now associated with:
  • The preview tab title of a page
  • Media library sharing options
  • Add and Delete buttons within the Edit Options of a schedule

• When creating a new site in OrchestraCMS, the site properties page has been redesigned.
  • Labels have been repositioned and included for all input fields
  • Default Language Description text area has been expanded by default
  • Naming Requirements have been added for the Site Name field

• In Content Template Creator, the text in Select boxes is now vertically centered.

• When using the RenderingAPI, unpublished content that is targeted will now be returned.

• While editing content and selecting a predefined target from the Properties sidebar or View All Properties dialog, selected targets will now display without having to reopen the content.

• Within visualforce page templates, panel names that contain spaces are now displayed in the page editor.

• The jQuery widget names for Content Type Selector and Content Template Selector were incorrectly changed. Content Type Selector and Content Template Selector have been renamed back to content_type_selector and content_template_selector.

• OrchestraCMS Developer Guide documentation has been updated to correctly reflect the name of the Content Selector widget as content_selector.

• UI improvements have been made to the View All Properties dialog within the page editor.

September, 2018

Fixes

• We fixed an issue where the description's meta tag was incorrectly being set to an empty string value when more than one additional URL was added.

• We fixed an issue where private sharing was not being enforced while using the ContentAPI.

• We fixed an issue where Taxonomy categories were not displaying while using View Content connections.

August, 2018

Fixes

• Custom Content Templates are now showing up in OrchestraCMS Setup (where they hadn't been earlier).

• You can now leave as blank the default values and width for any objects within a form.

• If multiple pages are selected for approval, you can delete those pages from Manage Pages.

• In Taxonomy Properties, the Save and Cancel buttons no longer disappear after selecting "All" or "Leaf" under Notification type.

• Content in created folders now updates properly after an unpublished version is deleted.

• You can now open the Taxonomy menu after entering a long description.

• "Edit page-specific properties" no longer appears on a content item that belongs to a master page.

• We addressed an error in changing language in Site Map.

• Documentation about Language Selector usage is now also included in the information about Multilingual Sites.

• ocmsAjaxFormLoadFinished and ocmsPageLoadFinished now works properly for all forms.

• The Create New Content button now shows the correct tool tip when you hover over it.

• An error message no longer occurs after you have added 29 pieces of unpublished content to a page.

• We made it possible to move (re-order) pages in the Site Map.

New

The Page Editor has a whole new look and function:  

The Droppable Area Summary is easier to read.

When you place a piece of content on a page, you will see new icons, including a drop-down function that allows you to Edit Content, Edit Page-Specific Properties, or Remove Content. It also shows you relevant information you might want to know about that piece of content.

In an earlier version of OrchestraCMS, there was a problem loading several pieces of content on a page. This has been fixed. Now you can choose several content items and place them on the page simultaneously.

Winter, 2018

The OrchestraCMS interface has been updated and unified for easier navigation within the Manage Site tab.

Stronger Font Weight

We found that the lighter font in the OrchestraCMS interface would sometimes get washed out on specific screens, and it was hard to read on some computers. So we changed it from Lato-Light to Lato.

Pagination improvement

To make it easier to navigate pages, we put pagination and the top and the bottom of lists. Now you can also enter a page number.

Collapsible sidebar and folders

Users working with smaller screens can collapse what they don’t currently need so they have more room to work.

Improved date filters

You can filter between two dates now, so you can see what was published in a single month or year.

Sections under Manage Site tab

Overture, Pages, Content, Media, Tasks, and Approvals are now sections (rather than tabs).

Manage Site sidebar

The new Manage Site sidebar, previously available for pages and media, is now available across all sections and also includes the new Site Folder Organization system.

Site Folder Organization system

There is a new section within the Manage Site Sidebar for folders. You can create and manage a hierarchical site folder structure for Content, Pages, Media, Tasks and Approvals, where you can share folders, manage the sitemap, manage media library folders, and preview certain kinds of media.

The sidebar uses the same styling and functionality as all other folder tree structures in OrchestraCMS.

You can Create, Rename, or Delete a folder; you can also add any Content, Pages, and Media into your site folders by simply dragging them from the Manage Site list.

Folder management options are enabled by default on the System Administrator profile only, along with Create, Edit, and Delete. The System Administrator can enable these options for other profiles.

Site Map Mode

In the Manage Site sidebar, you can toggle the option to view and edit your Site Map.

New Floating “Media” window

When you want to take a quick look at a piece of media content, a preview window now floats in the bottom right hand corner when an image is selected. It can be dragged to a place you choose on the Interface.

When you select multiple images you can scroll through them in the preview window.

When you click on a previewed thumbnail, it pops up to be the full size (or max size of window).

Navigational icons

The first section you see when you open OrchestraCMS, within the Manage Site tab, is Overture. At the top of the Overture section, there are icons, or symbols. When you hover over an icon, it becomes green and displays a description of the section. When you click on one of the icons, it displays your list of items in that section.

Information and resources

You can now click on the question mark icon in the OrchestraCMS task bar to open information about resources on the Stantive.com website.

The taskbar also shows the site and user name, and a chevron indicates a drop-down menu.

Rich Text Editor

When you are creating text, the text editor is now much larger and therefore easier to use.  

Tasks and Approvals updates

Tasks and Approvals used to be included in one “tab”. Now they are in separate sections, because they have very different actions. This allows for future bulk actions to be added.

You can also filter items in both Tasks and Approvals so you can look for specific things.

Generate Reports

If you would like to review and analyze data with people who don’t have full access to OrchestraCMS, you can create a report within OrchestraCMS that lists the specific data you want to show.

You can do this using Generate Report in the Actions panel for Content, Media, or Pages.

You can generate a report based on all Content or Pages in a list; or, using the Filters panel, you can first filter your list to include only certain Content or Pages — for example, published or expired items.

In the Generate Report dialog, you can choose what aspects of the list you want to reveal.

When you click Generate, OrchestraCMS creates a CSV document. Depending on the way your browser is configured to handle CSV files, the report will automatically download to your hard drive or open in a new tab.

Open Content or Pages for Edit by URL

URL parameters mean that users can now click on a main OrchestraCMS URL that opens directly to specific pages and content by ID.

New option for text fields on forms

An OrchestraCMS content editor can now add a drop-down pick list to a form, showing a list of categories from which to choose.

Content for guest users

OrchestraCMS site administrators can choose to target content to a guest user only.

Lifecycle actions – expire

Lifecycle Actions allow you to develop code so you can take action on content once it has been published. This could be, for example, pushing it to a social feed; sending an email to the author after it has gone out; or pushing out notifications to subscribers that something new was added.

Sandbox refresh improvement

We added a new apex class to reset the OrchestraCMS custom settings and clear out auto-generated permission sets. This will allow developer sandboxes to work without a lot of overhead.

Foldering API

This manages folders and items in folders – allowing developers to put content into specific folders if needed.