Hi, I found the solution before receiving an answer. I found that using the wicket:container markup tags in development mode will actually work with setVisible toggling, but not in deployment mode. I don't know if this is due to me using the wicket:container tag incorrectly or not. For my solution I just switched the tags over to <div> tags. I realized after the fact I probably could have used panels as opposed to containers for the solution, but it's a bit too late for that now.
On Thursday, November 7, 2013 9:12 AM, Ben S <[email protected]> wrote: Here's the code and markup, I'll begin looking for any errors I have made, thanks! http://pastebin.com/eVQfYCpx On Thursday, November 7, 2013 5:20 AM, Nick Pratt <[email protected]> wrote: This functionality does work - can you put your code up on pastebin/gist/whatever so we can take a look? (Markup and Source please) On Wed, Nov 6, 2013 at 8:14 PM, Ben S <[email protected]> wrote: > Hello, > > I've been trying to work on this issue for hours and have had no luck. > > Basically, my code works just fine in development mode as intended, > however when in Deployment mode I can't seem to get WebMarkupContainers > toggle between visibility. > > If they're visible, they won't go invisible, however if they are invisible > they will toggle visible. > > However, the markup containers seems to work as expected when the form is > passed to the AjaxRequestTarget, however this will clear all the data > that's on the form page, even though the form is set up for a compound > property model.. > > Is there any way to set the webmarkupcontainers visible to false using > ajax in Deployment mode?
