Known Issues

Pages missing under parent page or blank right pane

Symptom

A user is no longer able to see the child pages below a parent page in the WCM. Clicking on the [+] beside the parent page causes the [+] icon to disappear. Similarly, when clicking on a parent page in the left pane of the WCM, the child pages do not show up in the right pane.

This issue is caused by an expired session cookie which is stored in your browser. This cookie allows you to stay logged in to various SFU applications. When the session expires, you may be able to see a cached version of AEM's WCM, but you are no longer connected to the system. 

What to do

Restart your browser and log in to https://author.sfu.ca again. This will establish a new session cookie.

Users attempting to log in to https://author.sfu.ca get a 404 (Page Not Found) error

With the upgrade to AEM 6, we have implemented the CAS single sign-on service. Users who have multiple SFU accounts — e.g., a personal account as well as a departmental "role" account — will be unable to log in to AEM Author if they are logged in to another SFU service with an account that does not have access to AEM.

What to do

There are a number of work-arounds for this issue:

1. Make sure both your personal and role accounts are added to the authoring mailing list that controls access to AEM. For example, if your personal account is "kipling", but you occassionally use the "basketweaving" role account to send email via Connect, both "kipling" and "basketweaving" should be added to the mailing list. (Your Site Admin can add your accounts to the mailing list.)
2. If adding your accounts to the mailing list is not possible, you can ensure your previous account's session is not active by using "Private" or "Incognito" mode in your browser. In Firefox, in the File menu, choose New > Private Window. In Chrome, in the File menu, choose New Incognito Window. Enter the URL https://author.sfu.ca and sign in using an account that has access to AEM.
3. If your browser does not have "Private" or "Incognito" options, clear your browser's cache by quitting and restarting the browser.
   

"Sign out" button is missing  

As a result of the move to a single sign-on service (CAS), the Sign Out button no longer appears as an option in AEM. The advantage of single sign-on is that users can sign into one SFU system and that session is carried through a number of other applications (SFU Connect, Canvas, etc.). Unfortunately, the "Sign Out" option would not have the power to end sessions in other systems, leaving the user logged in to AEM even if they clicked the "Sign Out" button. For security reasons, this button was disabled.

Symptom

Authors are unable to log out using the "Sign Out" button.

What to do

To sign out, close your browser. If you need to sign in as another user, use Firefox's "New Private Window" option to start a new session.

Sidekick cannot be moved in Chrome or Safari

Symptom

After moving the Sidekick to the top of the Editing Window, it becomes stuck. The Sidekick cannot be moved or resized. This issue only occurs in the Google Chrome and Apple Safari browsers.

The vendor is aware of the issue and will be providing a fix in the future.

What to do

There are two workarounds:

• Sign out and sign back into AEM.
• Use a different browser like Firefox or Internet Explorer 9+. See AEM Web Browser Compatibility for a list of supported browsers.
  

Batch Upload of Digital Assets

Symptom

After selecting and uploading a large batch of files (e.g., 20 files or more), some of the uploaded files are not appearing
in the DAM.

What to do

• Upload in batches of no more than 5 files at a time.
• If you need to upload larger files in batches (e.g., several megabytes each), wait 15-20 seconds before clicking the "upload" button.  Typically, the larger the batch and file size, the longer you may need to wait before clicking "upload".
  

Deleted images, assets, or pages appearing on live site

Symptom

An image, asset or page thought to be deleted may still appear within the the live site. This most commonly applies to images but can affect pages as well.

What to Do

• Always deactivate images and pages before deleting them.
• If an asset appears on the live site, but not in author, add an asset with the same name to the DAM and activate it. Then, deactivate the asset. Once deactivated, delete the asset.

Back to top