History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-2685
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Scott Farquhar [Atlassian]
Reporter: Michael Phillimore-Brown
Votes: 0
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
JIRA

i18n fails on log out screen

Created: 17/Nov/03 06:03 AM   Updated: 30/Jul/06 07:37 PM
Component/s: Web interface
Affects Version/s: 2.5.1 Enterprise
Fix Version/s: 2.6 Pro

Time Tracking:
Not Specified

Environment: Running on WAS 5 with Sybase db 2.5.1 EAR.
Issue Links:
Duplicate
 

Participants: Ann-Sophie HOCQ, Jeff Turner [Atlassian], Michael Phillimore-Brown, Owen Fellows and Scott Farquhar [Atlassian]
Since last comment: 154 weeks, 5 days ago
Resolution Date: 04/Feb/04 09:29 PM
Labels:


 Description  « Hide
When I log out, I get a screen with the words '{0}Log in again.{1}' at the bottom and no link to click.

On your site, I get 'Didn't mean to logout? Log in again.' where 'Log in again' is hyperlinked and works as expected.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Owen Fellows - 17/Nov/03 05:44 PM
On the Logout page do you get text saying

You are now logged out. Any automatic login has also been stopped.

Didnt mean to logout? {0}Log in again.{1}

or

You are now logged out. Any automatic login has also been stopped.

Didn't mean to logout? {0}Log in again.{1}


There was a problem with single quotes in the text that caused the values to be replaced incorrectly.

If you change
logout.desc.line2 = Didn't mean to logout? {0}Log in again.{1}
in JiraWebActionSupport.properties
to
logout.desc.line2 = Did not mean to logout? {0}Log in again.{1}

It should solve the problem, but this is just a work around.


Owen Fellows - 17/Nov/03 07:44 PM
Hi,

I have found the solution, it is because your appserver (and older version of tomcat) do not pick up the webwork.tld file from the lib directory the use the one in the jar. (I believe this is incorrect).

As we use a custom TextTag for internationalisation this is not picked up and the standard one is used. This is why certain text is not internationised.

If you remove the meta-inf\taglib.tld from the webwork-xxxx.jar and redeploy it should solve the problem. (The jsps need to be recompiled using the new taglib).

I believe this as an App Server bug.

Thanks,
Owen


Jeff Turner [Atlassian] - 08/Dec/03 11:32 PM
Here is the workaround Owen mentioned, in a bit more detail, assuming we're in the JIRA Standalone root:

[ ~]$ cd atlassian-jira/WEB-INF/lib/
[ ~/atlassian-jira/WEB-INF/lib]$ mkdir tmp
[ ~/atlassian-jira/WEB-INF/lib]$ cd tmp
[ ~/atlassian-jira/WEB-INF/lib/tmp]$ jar xvf ../webwork-280803-profiling.jar
...
[ ~/atlassian-jira/WEB-INF/lib/tmp]$ rm -r META-INF/
[ ~/atlassian-jira/WEB-INF/lib/tmp]$ jar cvf ../webwork-280803-profiling.jar *
...
(in = 640585) (out = 337669) (deflated 47%)
[ ~/atlassian-jira/WEB-INF/lib/tmp]$ cd ..
[ ~/atlassian-jira/WEB-INF/lib]$ rm -r tmp


Scott Farquhar [Atlassian] - 04/Feb/04 09:29 PM
I have fixed this in webwork HEAD - waiting on 1.4.1 to be released:

http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-460

I'll create a separate issue to track the folding back of our text tag.


Ann-Sophie HOCQ - 01/Aug/05 11:23 AM
I have the same problem with Enterprise Edition, Version: 2.6.1-#65 and now with Enterprise Edition, Version: 3.2.2-#90.
We run Jira on Websphere 5 (windows) with Oracle 8i.
I tried this solution or the one described here : http://jira.atlassian.com/browse/JRA-3463 but no result (removing or replacing the taglib file).