Re: [Seaside-dev] Re: WAResponseGenerator>>expiredKey

Under Julian's guidance we fixed this issue, with both a fix to Seaside WAResponseGenerator>> expiredRegistryKey and some fixes to PRDesignChooserWidget>>renderContentOn: Name: Seaside-Core-Nick.644 Author: Nick Time: 13 June 2010, 5:57:22 pm UUID: 967def9d-0131-4ec8-bd40-b27d13987f57 Ancestors: Seaside-Core-pmm.643 Fix #expiredKey to use the registry URL instead of the session URL when redirecting. Then rename it to #expiredRegistryKey in order to be explicit. ---- Name: Pier-Setup-Nick.84 Author: Nick Time: 13 June 2010, 5:53:32 pm UUID: 450e1618-0911-4061-91e6-ede14bdfcb58 Ancestors: Pier-Setup-lr.83 redirecting back to Pier after a new application is registered didn't work on latest Seaside. New implementation more specific about what we're trying to achieve.  Consider reviewing code in PRDistribution>>register -- _______________________________________________ seaside-dev mailing list seaside-dev(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev