I tried to load the 3.2:
(ConfigurationOfSeaside3 project version: #'release3.2') load: #('OneClick'). ... and when accessing the control panel, got an error: MNU: WAServerManager contents Version 3.1 loads nicely and control panel works. Just have to add an adapter and start it. Any idea of what is going south here? TIA Phil _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
As I saw the default was an instance of WAServerManager, I removed the contents / contents: and returned default. This got me the control panel back, I was able to add an adapter. When I asked for loading the default page, I got WAError: no secure key generator availble because seeding failedYour request could not be completed. An exception occurred. What's the proper way to load 3.2? Is 3.2 even supported in 4.0? Should I stick to 3.1.x ? TIA Phil On Sun, Feb 14, 2016 at 4:31 PM, [hidden email] <[hidden email]> wrote:
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
I don't know, is Seaside 3.2 even out ? Or is it just development ?
https://ci.inria.fr/pharo-contribution/job/Seaside/ > On 14 Feb 2016, at 16:37, [hidden email] wrote: > > As I saw the default was an instance of WAServerManager, I removed the contents / contents: and returned default. > > This got me the control panel back, I was able to add an adapter. > > When I asked for loading the default page, I got > WAError: no secure key generator availble because seeding failed > > Your request could not be completed. An exception occurred. > > What's the proper way to load 3.2? Is 3.2 even supported in 4.0? Should I stick to 3.1.x ? > > TIA > > Phil > > > On Sun, Feb 14, 2016 at 4:31 PM, [hidden email] <[hidden email]> wrote: > I tried to load the 3.2: > > (ConfigurationOfSeaside3 project version: #'release3.2') load: #('OneClick'). > > ... and when accessing the control panel, got an error: > > MNU: WAServerManager contents > > Version 3.1 loads nicely and control panel works. Just have to add an adapter and start it. > > Any idea of what is going south here? > > TIA > Phil > > > > > _______________________________________________ > seaside-dev mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Hi,
3.2 is a ‘release candidate’. The thing you hit is one of the reasons it’s still a release candidate. The Seaside-Security package does not work on Windows. I don’t know how you got the first error with WAServerManager though. When I load it the same way you do and start an adaptor, it works as intended. Do you have a bit more stack trace to know where that got sent? For the second error (WAError: no secure key generator availble because seeding failed), do not install ‘Seaside-Security’. If you already did, you can ‘uninstall’ : WASecureKeyGenerator uninstall I think we will just remove it from the OneClick build. Unless Philippe has another idea to fix this? cheers Johan > On 14 Feb 2016, at 17:44, Sven Van Caekenberghe <[hidden email]> wrote: > > I don't know, is Seaside 3.2 even out ? Or is it just development ? > > https://ci.inria.fr/pharo-contribution/job/Seaside/ > >> On 14 Feb 2016, at 16:37, [hidden email] wrote: >> >> As I saw the default was an instance of WAServerManager, I removed the contents / contents: and returned default. >> >> This got me the control panel back, I was able to add an adapter. >> >> When I asked for loading the default page, I got >> WAError: no secure key generator availble because seeding failed >> >> Your request could not be completed. An exception occurred. >> >> What's the proper way to load 3.2? Is 3.2 even supported in 4.0? Should I stick to 3.1.x ? >> >> TIA >> >> Phil >> >> >> On Sun, Feb 14, 2016 at 4:31 PM, [hidden email] <[hidden email]> wrote: >> I tried to load the 3.2: >> >> (ConfigurationOfSeaside3 project version: #'release3.2') load: #('OneClick'). >> >> ... and when accessing the control panel, got an error: >> >> MNU: WAServerManager contents >> >> Version 3.1 loads nicely and control panel works. Just have to add an adapter and start it. >> >> Any idea of what is going south here? >> >> TIA >> Phil >> >> >> >> >> _______________________________________________ >> seaside-dev mailing list >> [hidden email] >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > _______________________________________________ > seaside-dev mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Free forum by Nabble | Edit this page |