Hi, yes, I did restart the server... The install (no upgrade) was obviously as smooth as ever. I did look a little deeper in the folder that was upgraded, and realized that I was upgrading something I grabbed from trunk instead of a the previous official release. In which case, I would not expect anyone or any organization to support this type of upgrade path. Not sure why it id that, but I would say that it is 1) my bad for upgrading an what should be for testing and development 2) my bad, ... well just because. I did look around and can't see any reason why the web2py upgrade would have broken the installed server (i probably had something that would have broken it at the next stop/start of the server anyways).
BTW - does look great! On Nov 13, 1:10 am, mdipierro <[email protected]> wrote: > Did you restart the server? > > On Nov 12, 11:13 pm, mart <[email protected]> wrote: > > > hum... the upgrade broke my running instance of web2py (not a big > > deal, I'll just install (not upgrade) to a different folder). Since, > > this seems to only happen to me, I can assume that it is something I > > have in current web2py folder (or on my system)... wish I knew what > > the "oddity" was so I could report better.... The strange thing, is > > that i get a continuous cycle of tickets. While trying to view the > > ticket, I get a new ticket (different number), and this just keeps on > > going... anyways, thought you may want to know tat this is happening. > > > Tanks > > Mart :) > > > On Nov 12, 11:55 pm, Alex <[email protected]> wrote: > > > > Maybe a bug? > > > > When I create a .LOAD component, the save doesn't seem to work in IE > > > or Firefox. > > > > On Nov 12, 10:44 pm, mdipierro <[email protected]> wrote: > > > > > The fact is after you upgrade you get the new admin which uses a new > > > > API function. Unless you restart the server that API function is not > > > > available. This is a one time event since we never made such a big > > > > change in admin. > > > > > On Nov 12, 7:26 pm, Anthony <[email protected]> wrote: > > > > > > I had the same exact experience on Windows (in IE). Here's the > > > > > traceback I got: > > > > > > Traceback (most recent call last): > > > > > File "C:\web2py\gluon\restricted.py", line 188, in restricted > > > > > exec ccode in environment > > > > > File "C:\web2py\applications\admin/views\default/site.html", line > > > > > 182, in <module> > > > > > AttributeError: 'translator' object has no attribute > > > > > 'get_possible_languages' > > > > > > Referring to: > > > > > > for language in T.get_possible_languages(): > > > > > > Like Andrew, everything was fine after restarting web2py. > > > > > > Anthony > > > > > > On Nov 12, 7:20 pm, Andrew Thompson <[email protected]> wrote: > > > > > > > On 11/12/2010 4:58 PM, mdipierro wrote:> ps. may not work on windows > > > > > > > I doubt this is what you meant, but I seem to have hit a snag with > > > > > > the > > > > > > upgrade. > > > > > > > web2py is running on ubuntu, but I'm managing it from chrome on > > > > > > win7. > > > > > > After upgrading, the redirect back failed. Attempting to reload the > > > > > > admin page gave me more failures. > > > > > > > If anyone wants to glance over the error files: > > > > > > >http://aktzero.com/static/scratch/__ffff_127.0.0.1.2010-11-12.19-03-0...... > > > > > > > Restarting the web2py process cleared it up, and it seems to be ok. > > > > > > I've > > > > > > got the new admin interface, and my small handfull of sites are > > > > > > still > > > > > > running. > > > > > > > -- > > > > > > Andrew Thompsonhttp://aktzero.com/-Hidequotedtext - > > > > > - Show quoted text - > >
