Showing posts with label components. Show all posts
Showing posts with label components. Show all posts

Friday, December 28, 2012

Outlook 2013 deprecated features and components

AppId is over the quota
AppId is over the quota

As much as we love adding new features to Outlook, for the maintainability of our product we sometimes need to remove those that are out of date and aren't utilized by a large number of users.  This allows us to focus on improving the Outlook features that most of you, our customers, rely on.

The following are some features that we've removed from Outlook 2013, and we want to make sure you are aware so there aren't any surprises when you go to use or deploy the new version. 

In Outlook 2013, we will no longer support "Classic Offline" Mode for Microsoft Exchange accounts.  Users in this configuration will be upgraded to Cached Mode when they install Outlook 2013.  For the vast majority of users this will mean no change to your Outlook experience.  Details of Cached Mode in Outlook can be found here:  http://technet.microsoft.com/en-us/library/jj683103.aspx

Exchange accounts will no longer be able to have their delivery location be a PST file (rather an .OST).  Users in this configuration will be upgraded to Cached Mode (with an .OST file) when they install 2013. See the previous article for details about cached mode. 

Users will no longer be able to publish calendars publicly to Office.com using Outlook 2013, and the Office.com calendar sharing service will be shutting down for older versions of Outlook as well.  We will publish a follow-up blog post detailing the timeline for the service changes, as well as ways to get the same feature set using Exchange or Outlook.com.

VPN and dialup preferences are no longer independently configurable in Outlook.  These options were previously located on the Send/Receive tab in Outlook 2010.  As a workaround, affected users are encouraged to set these options system wide in the Windows Control Panel. 

Outlook 2013 will no longer surface search results for mail and calendar items in Windows Explorer (or via the start menu).  Users can still utilize all of Outlook's search functionality from within the app itself. 

The Journal as a top-level module no longer exists in Outlook 2013.  Journal entries can still be accessed via the Journal folder in the Folder List module.   Also, the ability to 'auto-journal' your Outlook actions is gone in 2013. 

Outlook has traditionally supported importing and exporting data to and from many different file formats.  Many of the formats Outlook has supported are outdated and are no longer in mainstream use.  Outlook will continue to support comma-separated-value (.csv) files as well as .PST files, but other file formats are no longer supported.

 This list includes:

-          ACT! Contact manager files

-          Word 97-2003 (.doc)

-          Excel 97-2003 (.xls)

-          Outlook Express archives

The Contact Activities Tab is removed from Outlook 2013.  This previously provided a way to "link" contacts with other Outlook items, and have them all roll-up in the Activities Tab.  The Outlook Social Connector (introduced in Outlook 2010) replaces much of this functionality in a faster, more user friendly fashion. 

--Justin Mahood, Outlook Program Manager


View the original article here

Friday, April 27, 2012

A Short Simple Video Explaining the Shadow DOM and Web Components

A Short Simple Video Explaining the Shadow DOM and Web Components « Christian Cantrell function clearSearch() {document.search_form.s.value = "";} adobe.com      Christian Cantrell / A Short Simple Video Explaining the Shadow DOM and Web Componentsby Christian Cantrell  

View the original article here

Saturday, January 14, 2012

Permissions Denied issue when deploying components on a Cluster with a NFS GDS even though app.server starting user has been given read and write permissions to GDS.

When deploying LC components through LCM on JBoss Cluster running on RH Linux with a NFS GDS permissions denied error is thrown and deployment fails. This is seen even though the user starting the app.server has been granted read and write permissions to the GDS.
The following error is seen in LCM logs -
[2009-09-02 12:27:58,159], SEVERE, Thread-7, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask, Task failed com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component
….
…
Caused by: com.adobe.idp.DocumentError: java.io.IOException: Server returned HTTP response code: 500 for URL: http://10.8.224.110:9080/DocumentManager

In Server log the following error is seen -
com.adobe.idp.DocumentError: java.io.IOException: Permission denied
Cause – the issue happens if the netapp level permissions for this share are set to “NTFS” or “UNIX”.
Resolution – The permissions at the netapp level for the GDS share should be set to “mixed” instead of “NTFS” or “UNIX”.


View the original article here