package problems, which should now be fixed). Original commit message: I thought Weblocks should export a WITH-TRANSACTION macro to go with the other functions in this file. Implementing it, I noticed a bug in DYNAMIC-TRANSACTION: it would commit, rather than rollback, on a nonlocal exit out of the body if that exit wasn't done by signalling an error (i.e. was done by THROW, RETURN, or GO). I fixed this. I guessed that this was the "unique non-local exit unwind behavior" being warned about, and removed the warning.
Conflicts: src/acceptor.lisp src/store/clsql/clsql.lisp src/store/store-api.lisp src/widgets/quickform.lisp
Make URI parameters wok
… phase. The update-widget-parameters is called first thing for each widget, so the update-widget-children can take the URI parameters into account.
Fixing weblocks backtrace on latest hunchentoot (1.2.3 and 1.2.5 at least)
…efault store" This reverts commit d9afd2e. The right way to do what I was trying to do was to say :AUTOSTART NIL in the DEFWEBAPP, and then call START-WEBAPP myself with the additional arguments. (If there were multiple webapps being autostarted, it wouldn't make sense to pass the same additional arguments to all of them.)
button or checkbox presentation.
"back" button returns from the drilldown widget to the datagrid, as the user might expect. Example: you can have a datagrid of frobs selected by a 'navigation' at 'http://foo.com/frobs/';; the :drilldown-link-url-fn can return URLs like 'http://foo.com/frobs/42';. To do this, wrap the datagrid in a custom subclass of 'on-demand-selector', with a :lookup-function that, if given an empty list of tokens, returns the datagrid itself, otherwise returns the drilldown widget named by the first token.
Specifically, when an empty list of children was supplied, and the type alist didn't already have an entry for the type given, all children were discarded.
being loaded using a relative path.