Known Issues

Deployments are scheduled to occur biweekly on Tuesdays. Occasionally deployments will take place outside of this schedule. During deployments, the authoring environment is unavailable between 4:00 - 5:30 PM. Upcoming deployment dates  1/31/23, 2/14/23, 2/28/23, 3/14/23, 3/28/23 . Maintenance may be scheduled outside of deployments and will be posted here and announced in the AEM web author Slack Channel. Thank you for your patience.

Events Page Time-picker

• Events created from a time zone different from PST are using the local time of the person creating the event. This also occurs on components with time-pickers.
• Resolved: 1/23

Manage Publications

• Using Manage Publications to publish/unpublish multiple items at once does not function.
• Resolved: 12/22

Open DAM Shortcut for Image Components Missing

• The shortcut in all image-type components is presently missing. The button allows users to open the side-panel while the configuration dialogue is open. 
• Resolved: 6/22
• Workaround: Before configuring the component, be sure to open the Side Panel Asset (DAM) tab.

AEM Forms 404 Pages

• Due to a security risk, AEM forms were disabled on 5/13. If a user attempts to submit a form, they will be directed to a 404 page.
• Resolved 5/24: Ensure your form is properly configured.

Required Form Fields

• Enabling required form fields in the new Form component does not restrict as intended.
• Resolved: 5/24

RTE Nested Bullet Point Format

• The nested bullet points feature does not work correctly.
• Resolved: 5/24

Add Footer Links to Text and Image Component

• In Touch UI, the option to add a footer link is missing. 
• Resolved 5/10

Events Page Template

• Events Lists and associated Event Page Templates created in Classic are not fully editable in Touch (e.g. Description field)
• Resolved 5/10

Banner Builder in Full-Screen Setting

• Banner Builder difficult to edit when "Full Screen" configuration is selected. Authors cannot scroll through page. Please select 'view as published' for increased scrolling functionality.
• Resolved 5/10

Copy / Paste Components in Chrome

• Copying and Pasting components is supported in Touch UI. We are currently experiencing an error in Chrome with copy/paste functionality.
• Resolved 5/4: Clear your profile cache (or use incognito mode, Firefox or Safari)

Help Tips Persist

• Help tips pop-up that appears when editing a page persists after author selects 'do not show this again.'
• Resolved 4/8

AEM Author Environment Access Issues: VPN Required

• If you are having trouble accessing author, please refer to our VPN instructions, and be sure to note the 'full traffic no-split-tunnel' group selection requirement. 
• Resolved 9/21

RTE Lost Functionality

• Resolved 2/18/22

Event Page Template Date Displays Incorrectly

• The date selected in the dialog on an events page template is not what is displayed on the published page. The published page currently displays a date one day ahead of the selected date. 
• Resolved 2/15/22

Activating pages Doesn't Cascade to Sub-Pages

• This is specifically noted for pages where an action should be inherited to it's sub-pages for instance, adding or removing SUNetID protection, using the inherited paragraphs/text under the navigation in Everest sites, or activating/deactivating pages.  Be sure to check sub-pages to ensure what you intend is happening.  You can manually do this for all sub-pages.
  
• Resolved: 10/13/21

Asset Directories With SUNetID Protection May Show Pages as Forbidden

• If you have a SUNetID protected Asset directory (example - https://author.medweb.stanford.edu/damadmin#/content/dam/sm/SITENAME) links to these assets in your pages may come up as forbidden for some authors.
  
• Resolved: 10/13/21

Reference Component Unavailable

• Existing reference components exist but are not editable
• Not possible to create a new reference component. 
• Resolved: 9/14/21

Download Component

• Strange url generated for files in download component.
• This issue is caused when a file was added to the component but is not in the DAM. To resolve the issue, authors should upload the component to the DAM, then add it to the component.
• Tip: File names should NOT have spaces. 
• Resolved: 9/1/2021

Error message upon form submission

• Users seeing an error message upon submitting an AEM form
• Resolved: 9/1/2021

Google Sheets component error message

• Error message on Google Sheets component, data does not load.
• Resolved: August 31, 2021

Newly activated pages not appearing on med.stanford.edu

• When authors activate a page it is not appearing on med.stanford.edu
• Likely cause: dispatcher needs to be flushed
• Expected resolution: May 10th end of day
• Resolved: May 10th, 3:00 pm

Text Editor tools missing

• Authors reporting that the Rich Text Editor (RTE) tool bar in multiple components (text editor, text & image, feature box, etc.) is missing several tools that are normally part of the funtional editing toolset 
• Resolved: May 11th 2:00 pm

Authors reporting inability to successfully upload images to DAM

• Some authors have reported inability to successfully upload images. A 'blank' image appears in place of the thumbnail.
• Resolved: May 11th 1:00 pm Please note the thumbnail may first appear blank but after a short time the correct thumbnail will appear.

Authors reporting 'outdated template' when attempting to publish a page

• Outdated template messagae appears when authors attempt to publish some pages.
• Please submit a help ticket and include the url of the page(s) you encounter this issue
• Resolved: May 13th at 6:00 pm

Some pages directing to a content/sm link OR 404 pages.

• Some pages are directing to a med.stanford.edu/content/sm link.  
• Resolved: May 18th. 

SUNet Pages Inaccessible

• Site visitors unable to access SUNet protected pages. They receive error messages and / or 404s and are sometimes unable to access pubic pages after this occurs. 
• If you encounter this issue please submit a help ticket and include the urls where this occurs. Note that if you are an author and an end user reports this issue it is possible you will not be able to replicate it. Please still report it.
• This issue has been resolved for most sites that have pages protected by SUNet ID. If you encounter it please report it so that we may investigate.

PDF links resulting in error messages

• Reports of error messages for PDF links referencing documents in the DAM. 

Broken images

• Some sites are experiencing broken images on both author and / or on published pages
• Many of these issues have been resolved. If you are experiencing this issue submit a help ticket and include the link(s) to the page(s).

Internet Explorer is not a supported site editing browser

Internet Explorer has known issues in AEM when it comes to trying to make page edits. Therefore, we do not support it as a browser for working with your AEM site. We recommend Chrome for editing.  

Images don't update when changed in AEM author

AEM is browser based and because it is browser based it falls prey to a technique browsers use to make you think pages are loading fast, it's called browser cache.  The cache holds on to page images to give the appearance of loading fast when you return to pages you have already been to.  Because images are usually larger, by storing them locally on your computer it makes a page load faster.  This causes AEM to display the "older" image even though you have updated it.  The system acutally has updated the image and if you activate your page you will see it is correct on your live site.  To get AEM author to dispaly the correct image you will need to dump your browser cache. 

Editing can be slow

AEM is a rich, dynamic application that runs in a browser.  It is not a website so it will be slower than a public website.  AEM uses a lot of memory and processor power.  We recommend not keeping a lot of browser tabs open while editing, disabling browser plugins that take a lot of processes/memory, and using a wired network when available.  You can also close down desktop applications that take a lot of processing power.  The system will be slower for a few minutes every few hours as we update all the CAP profiles on the system.  We are monitoring and improving the performance on a regular basis.

Dragging components into narrow right columns is finicky

Some pages in our environment have a lot of overlapping drop zones created by the editing tool. This can result in zones that are hard to place content. The workaround is right click the drop zone and add the component directly. Another work around is to drag onto the desired zone and move the mouse up until the purple box in placed in the zone you want to use.

Pages that are hidden in navigation do not appear in list components

This is actually a feature that is required for some sites. We have just released an option to include hidden pages in news and event lists.

Adding annotations to hero banner keeps the banner from showing

Annotations are child objects of the component so this component gets confused when it encounters an annotation instead of an image. Avoid adding annotations on hero banners and remove annotations that you've added. If this does not fix the issue the help desk can quickly fix this.

Clicking on "Target" Crashes the Page

Targeting is not currently a supported feature in AEM. Avoid clicking it at all costs. if you click "Target" on components that have it in the edit bar, it most all cases the page will crash and you will need to contact the Help Desk to have the page recovered. On these components only click on "Edit" from the toolbar menu.

Tables do not stay in panels

There are cases in the tablet view where the table bleeds over the edge of the panel. We do not recommend using wide tables in general as this is a problem for mobile users. In most displays, tables work well. We will be fixing this issue.

URLs for subdomain sites

Vanity URLS are great for marketing your unique site to your audience. We used to build these with vhosts that keep your web traffic on the vanity URL, but this is not recommended for new sites and discouraged for ongoing use. Redirects are the recommended way to use a vanity URL. This allow sites to market more simple URLs and serve to solve the majority of issues. We always want to aggregate traffic into a single domain (med) to build page rank at Google and we have seen certain URL patterns that don't always work with subdomains using vhosts.