Ah, is it possible that this is a problem in the last RC that was fixed in
HEAD?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-and-Automatic-Link-Disabling-tp3748072p3749160.html
Sent from the Users forum mailing list archive at Nabble.com.
--
I was recently working for a French company where I had lots of issues
with the French accent ;)
Alf = half
en-jine = engine
inerf = enough
Sure made for some amusing moments for all involved.
I don't think Wicket can fix that though :0
>Hi,
>
>I have created a xxx_fr.properties file to transl
Thanks for the thoughts!
This is a bit strange. Not only is it not working, but when I add that
setAutomaticLinking to my init, it causes further errors... it's apparently
trying to resolve ".style.css" (no class name)...
It's possible it's my fault somehow. I'll debug in the morning, but any
ide
It works. Just tested it.
Maybe you don't have: getMarkupSettings().setAutomaticLinking(true);
in YourApp#init()
On Tue, Aug 16, 2011 at 9:54 PM, Martin Grigorov wrote:
> Yes, it should work.
>
> On Tue, Aug 16, 2011 at 9:42 PM, Jonathan Locke
> wrote:
>> In Wicket 1.5, the new mountPackage() in
Yes, it should work.
On Tue, Aug 16, 2011 at 9:42 PM, Jonathan Locke
wrote:
> In Wicket 1.5, the new mountPackage() in combination with wicket:link doesn't
> seem to create links that automatically disable when you're already on the
> given page. Is auto-link enable/disable still supported?
>
> T
In Wicket 1.5, the new mountPackage() in combination with wicket:link doesn't
seem to create links that automatically disable when you're already on the
given page. Is auto-link enable/disable still supported?
Thanks!
Jon
--
View this message in context:
http://apache-wicket.1842946.n4.nab
