On Wed, Jan 13, 2010 at 2:02 AM, John Cremona <john.crem...@gmail.com> wrote:
>>
>> This is frustrating. I built 4.3.1.alpha1 from scratch, ran it and
>> started up the notebook using port=8001 since 8000 was in use with the
>> already running 4.3 server (which had the problem). I also had to use
>> a non-default directory, again because of the clash with the other
>> server running. Of course I used secure=True, but then when firfox
>> went through its "untristed connection" dialog I was stuck since the
>> "Add exception" button failed to work. I am running firefox 3.5.6 (as
>> provided by my university on its standard linux desktop). If I start
>> the server with secure=False then I can log in ok and the problem with
>> %magma cells *does not happen*.
>>
>> Being optimistic, I am hoping that whatever was causing the problem
>> was somehow fixed between 4.3 and 4.3.1.alpha1. But it is frustrating
>> not being able to test it properly because of the firefox problem!
>>
>
> Apologies for all the postings. I connected to the new (4.3.1.alpha1)
> serversecurely from a different machine which had an older firefox
> (3.0.13) where I could add the exception with no problem.
>
> The issue with %magma cells did not happen. So I'll go with the
> optimistic verdict above.
>
I do remember fixing something very similar with the notebook, so I'm
optimistic.
However, I wouldn't deploy the notebook from alpha1, since it does
contain a couple of serious bugs ("little things" like maybe publish
doesn't work?).
There will be an alpha2 soon (if there isn't one already), and then
4.3.1 will come out within a few days.
William
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
