Authors using crop and rotate tools within the Assets Console may occasionally discover that their changes appear to work but are ultimately ignored when the image is refreshed. (This is for the crop-rotate-flip tools that are in the Assets Console, and not the tools within the photo component.)
When in Edit mode, clicking to open a link in a new browser tab or window loads the new page without the Flex UI header, removeing 'editor.html/' from the page URL in the location bar. Opening in the same tab works normally.
We have had some reports of secure pages (-pw) loading very slowly relative to the rest of a site. For example, the first secure page may take 20-30 seconds to display while adjacent non-secure pages load instantaneously.
On comparison, an RSS feed displayed on a UBCMS page does not match the master feed. One (or more) items are not the same, perhaps the headline or a link is different. After the synch interval set in the UBCMS has passed, this difference persists.
We have seen cases where a Photo Gallery does not load quickly or seems to never load. In this situation, the problem seems to be unreliability and poor response due to the file size of the images being displayed from the DAM. Extremely large images can be a problem, as well as lots of relatively large images.
Site managers can set their site to only show as https (SSL/secure) in Page Properties of their home page. However, in some cases, sites set as https can be opened as http, or even switch from https to http as visitors click through the site.
Some authors have reported that drag-and-drop of files into the Digital Assets Manager (DAM) fails. Instead the files load into the browser as a preview. This occurs when the DAM is accessed through the Websites Admin Console instead of the preferred Digital Assets Manager console.
When a tag is moved or merged, any pages already carrying that tag retain a 'ghost' of the original tag in their meta-data. This can corrupt tagged lists that are built on a parent of the original tag.
Secure pages are by design only accessible to a user once they have successfully logged in through Shibboleth. In some cases, like the List Component, the UBCMS is smart enough to not even reveal a link to a secure page unless the user should see the link, but this makes it difficult to naturally reveal these pages in lists.
Your site includes content such as a news or events feed from another UBCMS or external source, and what is shown on your site doesn't update when that external feed changes. This has to do with server caching.
A page or piece of shared content sometimes is published under a name that no longer exists on the author system. This can happen if a user without publishing rights renames a published page, or possibly for other reasons.
The Content Finder can be collapsed against the left edge of your browser. This can increase the visible area of your browser window when you are working within components of the UBCMS. However, it is also possible to accidentally hide it, and the Content Finder seems to be removed.