[web2py] Re: ImportError: No module named gluon.contrib.comet_messaging

Never mind, I found the solution. Stupid me, restarting the computer solves the problem :) On Friday, March 8, 2013 9:13:08 PM UTC-5, surfnet3 wrote: > > I'm still using an older version (2.0.9) > > On Friday, March 8, 2013 9:00:17 PM UTC-5, Anthony wrote: >> >> Sho

[web2py] Re: ImportError: No module named gluon.contrib.comet_messaging

I'm still using an older version (2.0.9) On Friday, March 8, 2013 9:00:17 PM UTC-5, Anthony wrote: > > Should be websocket_messaging.py now. > > Anthony > > On Friday, March 8, 2013 6:56:30 PM UTC-5, surfnet3 wrote: >> >> Hi, >> >> I tried the

[web2py] Re: ImportError: No module named gluon.contrib.comet_messaging

I've been able to send a message from a terminal to the browser, but when the browser tries to send a message, the error occurs. On Friday, March 8, 2013 6:56:30 PM UTC-5, surfnet3 wrote: > > Hi, > > I tried the websocket (comet_messaging.py) and followed the procedures >

[web2py] ImportError: No module named gluon.contrib.comet_messaging

Hi, I tried the websocket (comet_messaging.py) and followed the procedures inside, but got the following error in ajax_form(): ImportError: No module named gluon.contrib.comet_messaging How can I solve the problem? Thanks. -- --- You received this message because you are subscribed to th

[web2py] Environment variable LD_LIBRARY_PATH

How can I set the environment variable LD_LIBRARY_PATH for web2py?

[web2py] Re: Why SQLTABLE display different things for db. and 'list:reference '?

Thanks. On Mar 1, 2:08 pm, Massimo Di Pierro wrote: > fixed in trunk now. > > On Mar 1, 11:13 am, surfnet3 wrote: > > > > > > > > > The newest. > > > On Mar 1, 9:17 am, Massimo Di Pierro > > wrote: > > > > what web2py version? they

[web2py] Non-ASCII on SQLFORM Autocomplete Widget

Is it true that SQLFORM autocomplete widget doesn't work with non- ascii characters? Or is there any adaptations to the codes shown in web2py book that'll make it work?

[web2py] Re: Unable to Reference Tables with Capitalized Names in Version 1.92.1

and because SQL > is not always case insensitive (depends on settings). > > On Feb 28, 10:23 am, surfnet3 wrote: > > > > > > > > > The following codes are not working in v1.92.1 but worked in some > > previous versions: > >

[web2py] Re: Why SQLTABLE display different things for db. and 'list:reference '?

The newest. On Mar 1, 9:17 am, Massimo Di Pierro wrote: > what web2py version? they should be the same. > > On Mar 1, 1:19 am, surfnet3 wrote: > > > > > > > > > I have the following model: > > > db.define_table( > >     'person&

[web2py] Why SQLTABLE display different things for db. and 'list:reference '?

I have the following model: db.define_table( 'person', Field('name'), format=lambda r: r.name, ) db.define_table( 'product', Field('name'), Field('buyer', db.person), Field('seller', 'list:reference person'), ) I realize, in the following code: SQLTAB

[web2py] Re: Unable to Reference Tables with Capitalized Names in Version 1.92.1

wrote: > There has been quite a few posts/complaints around this. > Why was this changed? (if it was... I have not checked) > > On Feb 28, 11:23 am, surfnet3 wrote: > > > > > > > > > The following codes are not working in v1.92.1 but worked in some

[web2py] Unable to Reference Tables with Capitalized Names in Version 1.92.1

The following codes are not working in v1.92.1 but worked in some previous versions: db.define_table( 'Products', Field('name') ) db.define_table( 'purchases', Field('product_id', db.Products) ) It would work fine if the table name changed to 'products' instead.