Project

General

Profile

Bug #5514

Wt4 segfault on localized strings from server global resource

Added by Bruce Toll about 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
-
Start date:
01/24/2017
Due date:
% Done:

0%

Estimated time:

Description

With preview version of Wt4, github 3.3.6-22-gb3a1dd7b, an attempt to use server-based localized strings (tr) from a global resource results in a segfault.

The issue can be reproduced with the attached patch to the blog example. Visiting the path ".../blog/feed/" should result in a segfault.

Based on a comment in WString.C, it appears that this usage may intentionally be unsupported at this time.

Attached is a temporary patch/workaround that was used to help test an app that was being ported to wt4. The patch has only been minimally tested and assumes that a global resource should use the server's locale for localized strings.


Files

#1

Updated by Roel Standaert almost 5 years ago

  • Status changed from New to InProgress
  • Assignee set to Michiel Derhaeg
#2

Updated by Michiel Derhaeg almost 5 years ago

  • Status changed from InProgress to Closed

The locale is now retrieved from the "Accept-Language" header when there is no session or a default one is chosen when the web client does not provide this header.

#3

Updated by Roel Standaert almost 5 years ago

  • Status changed from Closed to InProgress
#4

Updated by Roel Standaert almost 5 years ago

  • Status changed from InProgress to Implemented @Emweb
#5

Updated by Bruce Toll almost 5 years ago

That sounds like a great enhancement. Thanks!

#6

Updated by Roel Standaert almost 5 years ago

  • Status changed from Implemented @Emweb to Resolved
#7

Updated by Roel Standaert over 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF