CQ5.4: How to display a confirmation dialog when activating pages

Posted on July 4, 2012 by dmcmahon | Comments (0)

Issue

If you are using CQ5.x you will notice that there is a confirmation dialog for deleting/deactivating pages in the WCM console.  No such confirmation dialog is presented when you activate a page.  In some projects it may be a requirement to present such a confirmation dialog for activation also.

Solution

You will have to overlay:
/libs/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js
to
/apps/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js
Create the same folder structure in apps and then copy the SiteAdmin.Actions.js node from libs to the same folder in apps. This will ensure the jcr:content node under the JS file is also copied.

Then edit the SiteAdmin.Actions.js from apps.  You should replace the CQ.wcm.SiteAdmin.activatePage function with the lines (435-520) from this SiteAdmin.Actions.js file.

Note

Ideally you should not not completely overlay the siteadmin.Actions.js as you might run into problems when a SP brings a new SiteAdmin.Actions.js with it. Instead just overlay the function you want to change.  Use the clientlib approach and create a new JS file, attach it to the same clientlib as the SiteAdmin.Actions.js and redefine the function you want to change in that new JS file.

reference: (35823)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES3: CertificateException: Terminating SSL connection – The server is not trusted

Posted on June 25, 2012 by dmcmahon | Comments (0)

Issue

If you are using LiveCycle ES3 Digital Signatures to apply signatures to PDF documents using a timestamp (TSP) server you may encounter the following exception:

WARN  [com.adobe.livecycle.signatures.pki.client.PKIException] (http-0.0.0.0-8080-7) Exception from transport package   (in the operation : internalSendReceive)

Caused By: java.security.cert.CertificateException: Terminating SSL connection – The server is not trusted(Alerts.java174)

Caused By: Terminating SSL connection – The server is not trusted(PKISocketFactory.java255)

Reason

This exception will occur if the TSP server is configured to use SSL, i.e. with a HTTPS URL, and the relevant certificate from the TSP server is not found in the LiveCycle Trust Store.  In this case the connection to the TSP server is ignored by LiveCycle as it is not configured correctly, and the signature on the PDF will be applied using the local time from the LiveCycle server machine.

Solution

You will need to import the certificate from the TSP server into the LiveCycle Trust Store (AdminUI > Settings > Trust Store Management > Certificates > Import).

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES3: PKIException: ALC-DSS-310-033 Invalid timestamp mime type

Posted on June 25, 2012 by dmcmahon | Comments (0)

Issue

If you are using LiveCycle ES3 Digital Signatures to sign PDF files using a timestamp server (TSP) you may encounter the following exception:

2012-06-22 06:48:31,608 WARN  [com.adobe.livecycle.signatures.pki.client.PKIException] (http-0.0.0.0-8080-7) ALC-DSS-310-033 Invalid timestamp mime type. (in the operation : createTimestamp)

Reason

This exception occurs when the TSP server does not return a response with the expected mime-type.  LiveCycle assumes that the TSP servers conform to the standards defined in RFC-3161 (http://www.ietf.org/rfc/rfc3161.txt).  According to this RFC the mime-types for communicating with TSP servers should be

application/timestamp-query
application/timestamp-reply

Solution

You should use a TSP server that conforms to RFC-3161 when integrating with LiveCycle Digital Signatures.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (3 votes cast)

LiveCycle: JBoss stopped logging in server.log

Posted on June 23, 2012 by dmcmahon | Comments (0)

If you have installed LiveCycle in a JBoss application server the server activity will normally be logged in:

<JBOSS_HOME>\server\<profile>\log\server.log

If the JBoss log is no longer logging activity you should check the following:

1. Log4J

The jboss-log4j.xml file is located in <JBOSS_HOME>\server\lc_turnkey\conf and controls logging in JBoss.  If there is any problem with this file then logging may stop working.  You can download this file (jboss-log4j-working) from a fresh LiveCycle installation on JBoss and replace the original (make a backup first).  Restart JBoss after swapping the log4j file and logging should switch to the server1.log file.

2. User account

If you are starting JBoss using a Windows service ensure that the user account used for the service has administrative privileges.  See the installation documentation for further requirements such as disabling UAC on Windows.

reference: (183305796)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

CQ5.4: Files uploaded to DAM saved with incorrect mime-type

Posted on June 20, 2012 by dmcmahon | Comments (1)

Issue

If you are uploading specific types of files (Word, PPT, SWF….) to CQ5 DAM, you may notice the the files are saved to the repository with a different mime-type, for example as images.

You may also notice warnings and errors in the error.log similar to the following:

*WARN* [JobHandler: /etc/workflow/instances/2012-06-20/model_171459455015372:/content/dam/geometrixx/documents/slides.ppt/jcr:content/renditions/original] com.day.cq.dam.commons.handler.StandardImageHandler extractImageInfo: error while reading metadata from image [/content/dam/geometrixx/documents/slides.ppt]:  org.apache.sanselan.ImageReadException: Can’t parse this format.
    at org.apache.sanselan.Sanselan.getImageParser(Sanselan.java:621)
    at org.apache.sanselan.Sanselan.getImageInfo(Sanselan.java:587)
    at org.apache.sanselan.Sanselan.getImageInfo(Sanselan.java:479)
    at com.day.cq.dam.commons.handler.StandardImageHandler.extractImageInfo(StandardImageHandler.java:207)
    at com.day.cq.dam.commons.handler.StandardImageHandler.extractMetadata(StandardImageHandler.java:244)
    at com.day.cq.dam.commons.handler.StandardImageHandler.extractMetadata(StandardImageHandler.java:145)
    at com.day.cq.dam.core.process.ExtractMetadataProcess.execute(ExtractMetadataProcess.java:65)
…
*ERROR* [JobHandler: /etc/workflow/instances/2012-06-20/model_171459455015372:/content/dam/geometrixx/documents/slides.ppt/jcr:content/renditions/original] com.day.cq.dam.core.impl.cache.CQBufferedImageCache Error while loading image /content/dam/geometrixx/documents/slides.ppt/jcr:content/renditions/original: javax.imageio.IIOException: No decoder available to load the image
*ERROR* [JobHandler: /etc/workflow/instances/2012-06-20/model_171459455015372:/content/dam/geometrixx/documents/slides.ppt/jcr:content/renditions/original] com.day.cq.workflow.impl.job.JobHandler Process execution resulted in an error: java.io.IOException: No decoder available to load the image com.day.cq.workflow.WorkflowException: java.io.IOException: No decoder available to load the image
    at com.day.cq.dam.core.process.CreateThumbnailProcess.execute(CreateThumbnailProcess.java:145)
    at com.day.cq.workflow.impl.job.HandlerBase.executeProcess(HandlerBase.java:172)
    at com.day.cq.workflow.impl.job.JobHandler.process(JobHandler.java:122)
    at org.apache.sling.event.jobs.JobUtil$1.run(JobUtil.java:272)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: No decoder available to load the image
    at com.day.cq.dam.core.process.CreateThumbnailProcess.execute(CreateThumbnailProcess.java:126)
    … 6 more

Reason

This is a product bug in CQ5.4 and earlier versions, as it does not correctly handle the dc:format metadata property in particular files.  When these documents contain images with dc:format=image/jpeg, CQ assumes that this property applies to the whole document. Therefore the file gets uploaded into /content/dam with a node ‘metadata’ which has property dc:format=image/jpeg.

Solution

The issue has been fixed in CQ5.5 as we have re-engineered the component responsible for handling the mime-type detection for files uploaded to DAM.  When you update to CQ5.5 you will have the final solution to this issue.

As a workaround for earlier versions you should follow these steps:
1. create a file reset-mimetype.ecma under etc/workflow/scripts
2. use the script in the attached file: reset-mimetype.ecma
3. save it
4. edit the workflow model (“DAM Update Asset” workflow)
5. add a “Process step” after the “Metadata extraction” step
6. edit the “Process step”
7. select the etc/workflow/scripts/reset-mimetype.ecma script
8. select the “Handler Advance” checkbox
9. save the workflow
Now the file formats should be correctly identified when uploading to DAM.

reference: (35508/CQ5-13504)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 5.0/10 (3 votes cast)

CQ5: NoInitialContextException: Cannot instantiate class: com.day.util.jndi.provider.MemoryInitialContextFactory

Posted on June 19, 2012 by dmcmahon | Comments (0)

Issue

If you have installed the Sharepoint connector for CQ5 you may encounter the following exception in the log:

*ERROR* [FelixStartLevel] com.day.crx.spi.sharepoint.osgi.impl.SharepointRepositoryImpl Failed to bind repository to JNDI: crx2sharepoint.repository javax.naming.NoInitialContextException: Cannot instantiate class: com.day.util.jndi.provider.MemoryInitialContextFactory [Root exception is java.lang.ClassNotFoundException: com.day.util.jndi.provider.MemoryInitialContextFactory]
at com.day.commons.simplejndi.impl.InitialContextProxy.getInitialContext(InitialContextProxy.java:75)
at com.day.commons.simplejndi.impl.InitialContextProxy.getDefaultInitCtx(InitialContextProxy.java:121)
at com.day.commons.simplejndi.impl.InitialContextProxy.getURLOrDefaultInitCtx(InitialContextProxy.java:116)
at com.day.commons.simplejndi.impl.InitialContextProxy.rebind(InitialContextProxy.java:146)
at javax.naming.InitialContext.rebind(InitialContext.java:408)
at com.day.crx.spi.sharepoint.osgi.impl.SharepointRepositoryImpl.registerJNDI(SharepointRepositoryImpl.java:532)
at com.day.crx.spi.sharepoint.osgi.impl.SharepointRepositoryImpl.activate(SharepointRepositoryImpl.java:283)

Reason

This error occurs if you are attempting to configure the Sharepoint connector to connect to Sharepoint 2010.  The Sharepoint connector (currently version 2.0.4) does not support Sharepoint 2010 at the moment.

Ensure you have read the instructions to install and configure the Sharepoint connector from the documentation:

http://dev.day.com/docs/en/crx/connectors/sharepoint/current.html

Solution

Support for Sharepoint 2010 will be added in a later version of the Sharepoint connector.

reference: (35371/CON-737)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (2 votes cast)

CQ 5.5 Update 1: Service unavailable – AuthenticationSupport service missing. Cannot authenticate request.

Posted on June 18, 2012 by dmcmahon | Comments (8)

Issue

CQ 5.5 Update 1 is now available on PackageShare.  If you have installed CQ 5.5 Update 1 you may encounter the following error in the error.log after restarting the CQ instance:

*ERROR* [0:0:0:0:0:0:0:1%0 [1340016598398] GET / HTTP/1.1] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.

Reason

After installing the Update 1 package, an info dialog appears which advises to “restart the instance”.  If you restart the instance immediately after the dialog appears, you will run into this problem.  Even after the dialog appears, the package keeps on installing behind the scenes.  This process is interrupted if the instance is restarted at this point.

You should wait until the installation has completed before restarting CQ5, checking the activity in error.log.  Once the error.log becomes quiet (after approx. 5 mins) it is safe to restart the instance.

Solution

After installing Update 1 check that all OSGi bundles have the status “ACTIVE” in the OSGi console.  Start any bundles that do not have the “ACTIVE” status and this should resolve the issue.

If the issue persists, you may have to reinstall CQ5 from a fresh copy, install the update 1 package, restart (wait until error.log shows no more activity) and finally reinstall your installed packages manually.

reference: (CQ5-18534)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.1/10 (9 votes cast)

LiveCycle ES3: Authentication failed for user (Scheme – Username/Password) Reason: Username or password is incorrect

Posted on June 18, 2012 by dmcmahon | Comments (0)

Issue

If you are accessing any LiveCycle services and have problems getting a response, you may notice the following warning in the server logs:

WARN  [com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] (Thread-21) 
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect. 
Refer to debug level logs for category com.adobe.idp.um.businesslogic.authentication for further details

 

If you enable DEBUG level logging you will see the following DEBUG information in the log:

DEBUG [com.adobe.idp.common.errors.exception.IDPLoggedException] (Thread-21)
UserM:: [Thread Hashcode: 1796127844] com.adobe.idp.common.errors.exception.IDPLoggedException|
[com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] errorCode:12803 errorCodeHEX:0x3203 message:
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect
 =========== Authentication failure detail report ================== 
 Scheme Type : Username/Password 
 UserId : user 
 Current Thread : ajp-0.0.0.0-11148-8 
 Following are the response details from various authProviders.  
 1 - com.adobe.idp.um.provider.authentication.LocalAuthProviderImpl - 
 Authentication Failed : Exception stacktraces are avialable at TRACE level 
 Messages collected for this AuthProvider are provided below
      - No local user found with UserId [user] in Domain [DefaultDom]
      - No local user found with UserId [user] in Domain [EDC_SPECIAL]

These warnings in the log may also be accompanied by an Error 500 if you are attempting to call the LC services through a browser/web application.

Reason

This issue can occur when you are attempting to access the services with a user account that does not exist in the LiveCycle database, especially when you are migrating applications from one LiveCycle environment to another (e.g. ES2 to ES3).  User accounts that were used by applications in the 1st environment will also need to be available in the 2nd environment.

Solution

Try whichever of the following solutions is applicable to your environment:  (contact your LiveCycle administrator if you do not have sufficient privileges)

1. Synchronize your LDAP server with LiveCycle (AdminUI > Settings > User Management > Domain Management > (Select LDAP Domain) > Sync Now)

2. Create the user manually in a local LiveCycle domain (AdminUI > Settings > User Management > Users and Groups > New User)

reference: (183300170)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

CQ5.5: Upgrade recommendations and information

Posted on June 18, 2012 by dmcmahon | Comments (1)

This information will be useful if you are planning to upgrade your CQ environment to CQ5.5. This information is intended as a supplement to the official upgrade documentation:  http://dev.day.com/docs/en/cq/current/deploying/upgrading.html

You should read these recommendations, and then follow the steps in the upgrading documentation, applying the added suggestions here as required.

Trial migration

It’s better to first run a dry-run migration on a clone of UAT (author & publish instances) to ensure that there are no major issues in the upgrade process. Check if there are any changes needed for your code to work on the upgraded version. In this case, change the code and ensure you have a consistent process for applying those changes. Identify any high risk areas in the code and plan for extended testing time on these areas following the upgrade.  Repeat the steps from scratch on the UAT clone so that you’ll be sure to have a consistent end-to-end process for the upgrade. Then proceed to upgrade all the environments: DEV, UAT & PROD.

Preparation

  • Create a clone of the instance to upgrade.  You’ll perform the upgrade on the clone. It will be easier to rollback in case of problems.
  • Perform a full consistency check on the repository early.  Fix any problems before attempting the upgrade/migration.
  • Read the extensive list of “Tips and Troubleshooting” in the upgrade documentation and apply the recommended changes to avoid these common problems.
  • The code-base has to be frozen before the upgrade process and all the existing bugs closed. In case it’s not possible to close all bugs, keep a detailed list of them and double check them on the upgraded version.
  • Only do 1:1 migrations. Only introduce new product features for editors/business later. This will let you focus on the migration itself and any regressions.
  • Try to get dedicated hardware for all environments (PROD + staging), this gives you much more flexibility.
  • Involve Adobe consulting if required.  This will ensure a smooth migration process adhering to best practices.
  • Compile a list of all connected systems and involve those teams in the migration planning.  Ensure they have a short turn-around time in case of issues.
  • Purge workflow history (this speeds up the update process).
  • Make sure all workflow tasks are finished (none are running).
  • Make sure you have at least 1024MB Heap configured during update.
  • Clean all the logs to make it easier to isolate upgrade issues.
    • crx-quickstart/logs/*
    • crx-quickstart/server/logs/*

Post-upgrade

Tests should cover complete authoring workflows and not just the correct rendering of templates.

Check ACLs and permissions (especially when updating from 5.2.1).

Check Workflow models – check if any customizations were overwritten.

Check all forms and form actions (especially when updating from 5.3 or older).

Production upgrade

After performing the upgrade process on a UAT instance, once you are ready to upgrade the production instances, there shouldn’t be any major/unexpected issues. The code-base should already be frozen and in a good state, and you should freeze out content changes also. Only urgent changes should be applied to the content and the author team will need to keep track of all updated pages. These can then be moved later with a package.

1. Follow all the steps documented in the upgrade docs.

2. Sign-off the environments.

3. Migrate the latest content changes (if needed).

4. Switch the instances.

5. Delete all the dispatcher(s) cache.

It’s better to keep the old instances available for a while in case of problems not encountered during all the documented steps.  You should plan enough time for bug fixing following the production upgrade.

reference: (35335)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.3/10 (4 votes cast)

LiveCycle Workbench ES3: AttributeNotFoundException trying to create a new process

Posted on June 6, 2012 by dmcmahon | Comments (0)

Issue

If you have installed ES3 SP1 (10.0.3) to your LiveCycle ES3 server and Workbench ES3 you may encounter a problem creating new processes.  Selecting the menu item to create a new process does not have any effect.  If you look in the Workbench log file (C:\Users\<YOUR_USER_NAME>\Workbench ES2\.metadata\.log) you may notice the following exception:

!ENTRY org.eclipse.ui 4 0 2012-05-31 21:58:28.424
!MESSAGE Unhandled event loop exception
!STACK 0
ALC-DSC-110-000: com.adobe.idp.dsc.registry.endpoint.EndpointStoreException: endpoint registry failure.
Caused by: com.adobe.pof.schema.AttributeNotFoundException: Attribute: parent_oid does not exist on object-type: dsc.sc_category.
 at com.adobe.pof.schema.POFAbstractObjectType.getAttribute(POFAbstractObjectType.java:177)
 at com.adobe.pof.omapi.POFDefaultQuery.addSort(POFDefaultQuery.java:323)
    at com.adobe.pof.omapi.POFDefaultQuery.addSortAsc(POFDefaultQuery.java:372)
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointStoreImpl.getEndpointCategories(EndpointStoreImpl.java:219)
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointRegistryImpl$2.doInTransaction(EndpointRegistryImpl.java:155)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:357)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew(EjbTransactionCMTAdapterBean.java:299)
    at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)

Reason

ES3 SP1 includes some feature enhancements in Process Management.  This involved addition of new columns and tables to the existing ES3 DB schema and hence requires a DB re-initialization when running LCM.

Solution

You should always read the installation steps in the ES3 SP1 readme (link below) before attempting the installation.  In this case, you will need to re-run LCM and select the step to initialize the database.

https://www.adobe.com/products/livecycle/pdfs/lces3_sp1_readme.pdf

You can download ES3 SP1 here:

https://www.adobe.com/cfusion/entitlement/index.cfm?e=lces3_sp1

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

CQ5.5: Members of administrators group not able to unlock pages from other users

Posted on June 6, 2012 by dmcmahon | Comments (0)

Information

Only the user who locked the page, or the “admin” user, can unlock it.  Members of the administrators group, apart from the “admin” user, cannot unlock pages which were locked by other users.

The documentation (http://dev.day.com/docs/en/cq/current/wcm/page_publish.html#Locking%20Pages) states:

You can only unlock locked pages if you locked the page or if you have administrator privileges.

This may be misleading, as it is not sufficient to have administrator privileges (i.e. general members of the administrators group).  Only the “admin” account has the correct privileges.

How to unlock a page

It is possible to unlock a page using the sidekick in WCM, or using Content Explorer.

1. Using the sidekick

Log into CQ as the user who locked the page or the “admin” user.

Open the page that is currently locked in the WCM Websites panel.

In the sidekick, select the Page tab and then “Unlock Page”.

2. Using Content Explorer (http://<server>:<port>/crx/explorer)

Browse the tree to the locked page.

Right-click on the jcr:content node below the locked page.

Select “Unlock” from the context menu.

reference: (35128/CQ5-18339)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 votes cast)

Acrobat: PDF Printer missing after installation on Windows 64-Bit

Posted on June 4, 2012 by dmcmahon | Comments (21)

Issue

If you have installed Adobe Acrobat on a Windows 64-bit OS, you may notice that the Adobe PDF printer has not been installed.  During the installation you may have received an error similar to the following:

Please note that the Adobe PDF Printer functionality to create PDF files  is only available with Adobe Acrobat (paid version), and not with Adobe Reader (free version).

Solution 1

Repair the Acrobat installation using the option in the Help menu.

Solution 2

Uninstall and then re-install Acrobat on your Windows OS.

Solution 3

Manually install the PDF Printer

  • Click Start >  Control Panel > Devices and Printers
  • Select Add a printer
  • Select Add a local printer
  • Check Use an existing port and select Documents\*.pdf (Adobe PDF) from the drop down.  Click Next
  • Click the Have Disk… button
  • Click the Browse… button
  • Navigate to C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Xtras\AdobePDF
  • Select AdobePDF.inf from the list if using Acrobat Pro, or AdobePDFstd.inf if using Acrobat Std, then click the OK button
  • You will see many Adobe PDF Converters in the list, however count six down from the top and click Next (you may need to try this numerous times to find the correct Converter from the list that works with your version of Windows)
  • Name your printer, e.g. Adobe PDF
  • Follow the rest of the prompts and your PDF printer should now be installed correctly

If you are later prompted for the ADPDF9.PPD file, it can be found in the C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Xtras\AdobePDF\<OS version> folders.

Additional Information

http://forums.adobe.com/message/3348729

http://acrobatusers.com/forum/pdf-creation/how-do-i-insatll-adobe-pdf-printer-windows-7-adobe-reader-9/

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.3/10 (64 votes cast)

CQ5.5: ‘uu’ is undefined javascript error in widgets.js

Posted on June 1, 2012 by dmcmahon | Comments (1)

Issue

If you add a datetime or datefield Widget to a component dialog (e.g. /apps/geometrixx/components/title/dialog/items) in CQ5.5, you may encounter a javascript error on the page when you open the dialog, enter a date and submit it.  Your other changes in the dialog will not be displayed (e.g. the updated title will not displayed).

The javascript error says “uu is not defined” .

Reason
This is caused by an error in the JS code in
/libs/cq/ui/widgets/source/undo/UndoHistory.js (line 921).
There is an undefined variable “uu” used here.

Solution

This is a bug in CQ5.5 and will be fixed in a future release.

Workaround

A workaround would be to add a definition for “var uu = CQ.undo.util.UndoUtils;” before that variable is called.

1. create an overlay of /libs/cq/ui/widgets/source/undo/UndoHistory.js to /apps/cq/ui/widgets/source/undo/UndoHistory.js
2. open /apps/cq/ui/widgets/source/undo/UndoHistory.js
3. goto line 921
4. paste the following code into line 921:

var uu =CQ.undo.util.UndoUtils;
5. line 922 should now have:

var dateValue =uu.parseDate(originalValue);
6. save the file

reference: (33913/CQ5-17726)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (8 votes cast)

Acrobat: Hotfix recommendations for Citrix XenApp environments on Windows 2008 Server

Posted on May 21, 2012 by dmcmahon | Comments (1)

Information

If you are using Adobe Acrobat/Reader in a Citrix XenApp environment, you may experience issues related to problems in Citrix or the underlying Windows operating system.  Citrix have issued recommendations for hotfixes in XenApp and Microsoft Windows, which resolve most of the common issues with XenApp 6.0 and later, running on Windows 2008 Server.

If you do experience issues running Acrobat/Reader in a Citrix XenApp environment, ensure you have the recommended hotfixes installed.  You should contact Citrix for support or refer to their technotes such as the one below:

http://support.citrix.com/article/ctx129229

For more information related to Acrobat/Reader deployments on Citrix, please refer to our Enterprise Administration Guide:

helpx.adobe.com/content/dam/kb/en/837/cpsid_83709/attachments/Acrobat_Enterprise_Administration.pdf#page=101

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (2 votes cast)