1). History ‘back’ will now go all the way to the login form even if the user is logged in and has not logged out (enhanced security disabled)
2). Valuelists in webclient that are based on a global relation do not work
3). Can’t add a foundset filter to a related foundset anymore (is this new?) I get an exception thrown
4). Focusing on an HTML area field in smart client activates RTF toolbar
Also the debug code from wicket about “using a non-standard component name: servoy” is still littered throughout the log. I thought this was removed.
jcompagner:
1> you mean the login form was not added to the history list in 5.1 and it is in 5.2?
2> make a case
3> was never meant to work, but i guess you called one that did by pass this, so this is a fix.
4> need to check
About the log, i dont know, i dont see that at all. in my logs
1 - In 5.1 (or before as I recall) you could not go back past the solution’s first form if you were logged in. The [custom] login form was not in the history.
2 - OK. See 328821.
3 - Note that this has worked in the past and the documentation does not reference this limitation of fsFilter.
4 - This one is pretty easy to spot. It’s all html areas in smart client whenever they grab focus.
Regarding the log, I am still getting those messages. See attached.
about 4: yes thats true, but why shouldnt it work for a html area? if that wasnt the case in 5.1 that thats a bug…
It works fine for html also like making stuff bold or italic.
So that is not a bug that got introduced in 5.2
about the logging, somehow you have configured log4/slf4j settings to also log wicket stuff and then also the info level.
Because you do see:
if (!ComponentTag.DEFAULT_WICKET_NAMESPACE.equals(wicketNamespace))
{
log.info("You are using a non-standard component name: " + wicketNamespace);
}
which you really shouldnt see in our default log settings.
jcompagner:
about 4: yes thats true, but why shouldnt it work for a html area? if that wasnt the case in 5.1 that thats a bug…
It works fine for html also like making stuff bold or italic.
So that is not a bug that got introduced in 5.2
You’re right, and I had no idea the toolbar was component aware. Meaning I didn’t know that if you are focused on an HTML area and use the formatting toolbar it will write HTML markup whereas if you are focused on an RTF area and use the formatting toolbar it will write rtf markup. I don’t recall ever seeing the formatting toolbar enable when I focused on html areas before, but I guess it must have.
Thanks
PS: the formatting toolbar seems to enable even if the html area is editable = false. Is that the expected behavior?
jcompagner:
about the logging, somehow you have configured log4/slf4j settings to also log wicket stuff and then also the info level.
Because you do see:
if (!ComponentTag.DEFAULT_WICKET_NAMESPACE.equals(wicketNamespace))
{
log.info("You are using a non-standard component name: " + wicketNamespace);
}
which you really shouldnt see in our default log settings.
We seem to have:
log4j.logger.org.apache.wicket=INFO
But no one recalls setting it. Sounds like it should not be INFO though.
