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 support Chrome, Firefox, and Safari as browser editing tools.
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 mode, it most all cases the page will crash and you will need to contact the Help Desk to have the page recovered.
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.