[JBoss JIRA] Created: (GTNPORTAL-1328) Container without porlet still displayed in special case
by Hang Nguyen (JIRA)
Container without porlet still displayed in special case
--------------------------------------------------------
Key: GTNPORTAL-1328
URL: https://jira.jboss.org/browse/GTNPORTAL-1328
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Hang Nguyen
Priority: Minor
Attachments: Stilldisplaycontainerwithoutportlet.png
Steps:
* Edit lay out of portal
* add a container (but do not add any portlet inside)
* Save >> The container without portlet is not displayed. It is ok.
However, in case edit the container above, define width and heigh.
In spite, the container does not contain any portlet, it is displayed when showing portal.
Requirement:
* Do not show the container without any portlet in spite change the container's width & height.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-1407) Language doesn't persist when session timeout
by Benjamin Paillereau (JIRA)
Language doesn't persist when session timeout
---------------------------------------------
Key: GTNPORTAL-1407
URL: https://jira.jboss.org/browse/GTNPORTAL-1407
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Internationalization and Localization
Affects Versions: 3.1.0-GA
Environment: all
Reporter: Benjamin Paillereau
Priority: Critical
There is a critical issue in GateIn about i18n. In public mode, the current portal language user choice is stored in the session. If the user waits the session timeout then we lose the language and go back to the default one.
If you take WCM for example, for performance reasons, we reduce automatically the session MaxInactiveInterval to 60sec.
So, if you change the language in public mode, you lose it after 60 sec if you don't refresh your page.
We can see a workaround and a longterm solution.
Workaround : use a cookie and store the language in a cookie. When we load the page, if the current language is different than the one in the cookie, we will prefer the cookie.
Longterm solution : we must have a unique url for each language/page.
http://mysite.com/portal/public/website/mypage => default language
http://mysite.com/portal/fr/public/website/mypage => fr language
or
http://mysite.com/portal/fr/website/mypage => fr language
URL format is still to be determined but the point is to have a unique url. The best solution should be to be able to choose the url format in the UI when creating a website.
Using unique urls also allows to use a web cache (like varnish), which is not possible now.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-1420) Implement a resource compressor service that allow compressor pluggable
by Trong Tran (JIRA)
Implement a resource compressor service that allow compressor pluggable
-----------------------------------------------------------------------
Key: GTNPORTAL-1420
URL: https://jira.jboss.org/browse/GTNPORTAL-1420
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Trong Tran
Fix For: 3.2.0-GA
Allow to perform compression of client resources such as javascript or stylesheet. The compression is specific to resource types and produce a new representation of the same file that is semantically equivalent. There are a few compressor existing in open source and we could leverage them.
A ResourceCompressorService that is used by javascript and css services to perform resource compression. The service is a facade for plugins. The plugins perform the actual compression, the compressor service is here to factor the common code to plugins and most importantly the client of the service does not have to chose the implementation, it just wants compression to occur. It is possible to have several plugins for the same kind of resource, an integer priority will be used to make the choice possible at runtime.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months