[keycloak-user] Breaking Change to Themes in 2.0/2.1?

[Stian Thorgersen]

Most likely it'll be fixed in 2.2.0.CR1, 2.3.0.CR1 at the latest.

On 29 August 2016 at 17:16, Chris Hairfield <chairfield at gmail.com> wrote:

> Gladly! https://issues.jboss.org/browse/KEYCLOAK-3494
>
> How might you prioritize this one?
>
> On Mon, Aug 29, 2016 at 4:42 AM Stian Thorgersen <sthorger at redhat.com>
> wrote:
>
>> Just tried this out with the address theme and there's indeed a bug. I
>> can also see the following in the log:
>>
>> 12:41:26,385 WARN  [org.keycloak.forms.account.freemarker.model.AccountBean]
>> (default task-14) There are more values for attribute 'region' of user
>> 'admin' . Will display just first value
>>
>> So something is definitively broken. Can you create a JIRA please?
>>
>> On 26 August 2016 at 20:03, Chris Hairfield <chairfield at gmail.com> wrote:
>>
>>> Hello Keycloak Users,
>>>
>>> We recently upgraded from 1.9.8 to 2.1.0 and love it (fixes a good
>>> number of issues we've been having), but it seems to have broken an
>>> important one: our themes!
>>>
>>> For all HTML input elements we've added (those backed by user
>>> properties), when we modify their value and save/POST, Keycloak returns an
>>> HTML document populated with the old values rather than the new. A refresh
>>> of the page is required for the new value to be returned/displayed, even
>>> though the first save is sufficient to save the new value on the user.
>>>
>>> One may reproduce this easily in 2.1.0 by adding the following code to
>>> the base theme's account.ftl file:
>>>
>>> <div class="form-group">
>>>     <div class="col-sm-2 col-md-2">
>>>         <label for="user.attributes.example"
>>> class="control-label">Example:</label>
>>>     </div>
>>>     <div class="col-sm-10 col-md-10">
>>>         <input type="text" class="form-control" id="user.attributes.example"
>>> name="user.attributes.example" value="${(account.attributes.
>>> example!'')?html}"/>
>>>     </div>
>>> </div>
>>>
>>> In an Incognito window, impersonate a user, update the Example input,
>>> and click save. Your new value is stored as an attribute on the user, but
>>> the value of the input is set to whatever it was before. Refresh your
>>> browser for the updated value to appear.
>>>
>>> Any thoughts as to why? Do we need to update our theme code somehow?
>>>
>>> Thanks,
>>> Chris
>>>
>>> _______________________________________________
>>> keycloak-user mailing list
>>> keycloak-user at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-user/attachments/20160830/756d2697/attachment.html