Clearing the cache does not fix this. Tested with multiple browsers.

On 1 November 2015 at 17:15, Dan Haywood <[email protected]>
wrote:

> I'll check this on 1.10.0 RC1 before releasing.
>
> It's possible that the issue is cached CSS; do a ctrl-R or ctrl-F5 (or
> whatever) to force reload of all assets; might fix things?
>
> Dan
>
> On 1 November 2015 at 14:17, Jeroen van der Wal <[email protected]>
> wrote:
>
> > Hi Stephen,
> >
> > I've checked the kitchensink app and [1] and integers are displayed
> > correctly there [2]. I do see a bug with booleans not being displayed
> > though.
> >
> > Perhaps you could checkout the app on your local computer too?
> >
> > Cheers,
> >
> > Jeroen
> >
> >
> > [1] https://github.com/isisaddons/isis-app-kitchensink
> > [2] http://imgur.com/PJa94Nq
> > [3] http://imgur.com/xFE3QXQ
> >
> >
> >
> >
> > On 31 October 2015 at 00:59, Stephen Cameron <[email protected]
> >
> > wrote:
> >
> > > seems its mrore general, also have same problem with Boolean property,
> so
> > > maybe its everthing that is not a String?
> > >
> > > On Sat, Oct 31, 2015 at 10:14 AM, Stephen Cameron <
> > > [email protected]> wrote:
> > >
> > > > Hi,
> > > >
> > > > I just noticed a bug, I have an Integer property that is not being
> > > > displayed in the Wicket UI.
> > > >
> > > > I can see that value is being saved to the data-store (MySQL) but its
> > not
> > > > displayed.
> > > >
> > > > This is in the 1.10.0-SNAPSHOT version.
> > > >
> > > > I cannot access JIRA at the moment to log a bug.
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Reply via email to