Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.2
-
Fix Version/s: EE-3.2.0.GA, 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Portlets, ACE comps.
-
Assignee Priority:P1
-
Affects:Compatibility/Configuration
Description
In doing work for ICE-8710, I noticed that the strategy of caching resource URLs during the initial creation of the RichTextEntryResourceHandler can lead to problems when running in portlets. Specifically, when the RichTextEntryResourceHandler is first created, it will try to determine and use the URL of the first portal page that loads with an ace:richTextEntry component. For example, a Liferay URL might look like:
http://localhost:8080/web/guest/page1....
It will then try to create mappings for all the resources used by the CKEditor using that URL. If you add another ace:richTextEntry instance to another page:
http://localhost:8080/web/guest/page2....
it will attempt to load the resources from the original page. This may work or it may fail depending on the current state of the application. However, we should not be relying on this strategy anyway for portlets as it can either use the incorrect URL or it may fail completely in environments (e.g. WebSphere) were the URLs might be more opaque.
http://localhost:8080/web/guest/page1....
It will then try to create mappings for all the resources used by the CKEditor using that URL. If you add another ace:richTextEntry instance to another page:
http://localhost:8080/web/guest/page2....
it will attempt to load the resources from the original page. This may work or it may fail depending on the current state of the application. However, we should not be relying on this strategy anyway for portlets as it can either use the incorrect URL or it may fail completely in environments (e.g. WebSphere) were the URLs might be more opaque.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 3.3 [ 10370 ] |
| Assignee | Arturo Zambrano [ artzambrano ] |
| Summary | Placeholder issue | Cached resources for ace:richTextEntry can lead to problems with portlets |
| Fix Version/s | EE-3.2.0.GA [ 10332 ] | |
| Reporter | Migration [ remote ] | Deryk Sinotte [ deryk.sinotte ] |
| Affects Version/s | 3.2 [ 10338 ] | |
| Environment | Test | Portlets, ACE comps. |
| Description | Placeholder issue |
In doing work for ICE-8710, I noticed that the strategy of caching resource URLs during the initial creation of the RichTextEntryResourceHandler can lead to problems when running in portlets. Specifically, when the RichTextEntryResourceHandler is first created, it will try to determine and use the URL of the first portal page that loads with an ace:richTextEntry component. For example, a Liferay URL might look like:
http://localhost:8080/web/guest/page1.... It will then try to create mappings for all the resources used by the CKEditor using that URL. If you add another ace:richTextEntry instance to another page: http://localhost:8080/web/guest/page2.... it will attempt to load the resources from the original page. This may work or it may fail depending on the current state of the application. However, we should not be relying on this strategy anyway for portlets as it can either use the incorrect URL or it may fail completely in environments (e.g. WebSphere) were the URLs might be more opaque. |
| Component/s | ACE-Components [ 10050 ] |
| Assignee Priority | P2 [ 10011 ] |
| Affects | Compatibility/Configuration [ 10002 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Assignee Priority | P2 [ 10011 ] | P1 [ 10010 ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Security | Private [ 10001 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |