[Seaside-dev] Re: Loading 3.2 in Pharo 4:

[phil at highoctane.be]

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, phil at highoctane.be <phil at highoctane.be>
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
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20160214/eae23faa/attachment.htm