[web2py] Re: problem with a date in a form
yes, I'm italian :D I've already check it in my it.py is %d/%m/%Y for the input I use the calendar I have, for exeple 20/06/2013 and the error say me "enter date as 28/08/1963" and the date is in that format! -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[web2py] problem with a date in a form
I have a form that I submit by ajax and I have a problem with a date field.
in my db:
db.define_table('fatture',
Field('codice','string', length=10),
Field('dataf', 'date'))
in my form:
ajax function:
ajax('inseriscifa',['codice','dataf'],':eval')
controller:
def inseriscifa():
form = SQLFORM(db.fatture)
if form.accepts(request.vars, formname=None):
return "alert('ok')"
elif form.errors:
return "alert('" + XML(TABLE(*[TR(k, v) for k, v in
form.errors.items()])) + "')"
And, I don't understand why, I got an error about date format:
*enter date as 28/08/1963*
what's wrong? validors are great in web2py, but whit date a I have always
problem...
s.
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[web2py] Re: row.id with "L" after upgrading to
thanks for your reply! -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[web2py] Re: row.id with "L" after upgrading to
why I shouldn't convert it to an INT? It is the ID of my table and I need it as integer (as on the preview version) ... Il giorno martedì 18 giugno 2013 18:40:06 UTC+2, Derek ha scritto: > > If you aren't using google app engine, then that should be okay. However > if you are, you shouldn't convert it to an INT because you'll get errors. > > The "L" means it's a LONG and not an INT. > > On Tuesday, June 18, 2013 7:11:14 AM UTC-7, palomar wrote: >> >> I've just updated to 2.5.1 and I found this problem: >> Inside my site have a google map and I need to add an array with several >> marker; >> in my controller I have a simple query with a cycle >> def mappa: >> markers=[] >> for row in db().select(db.produttori.ALL): >>markers.append([row.id, row.lat, row.lng]) >> return dict(markers=XML(*[markers])) >> >> and I obtein ID + L, like this: >> [1L, '12.5', '7.6'] >> >> so I need to do int(row.id) >> In the older version worked well... >> s. >> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[web2py] row.id with "L" after upgrading to
I've just updated to 2.5.1 and I found this problem: Inside my site have a google map and I need to add an array with several marker; in my controller I have a simple query with a cycle def mappa: markers=[] for row in db().select(db.produttori.ALL): markers.append([row.id, row.lat, row.lng]) return dict(markers=XML(*[markers])) and I obtein ID + L, like this: [1L, '12.5', '7.6'] so I need to do int(row.id) In the older version worked well... s. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[web2py] Re: compute field doesn't work on update
up
Il giorno sabato 19 gennaio 2013 18:43:51 UTC+1, palomar ha scritto:
>
> I had the 2.1 and I've just updated to 2.3 (I hoped to solve the
> problem...)
>
> request.vars.id is the vars from the ajax call; it works, I'm sure,
> articolo.p_p is correctly updated
>
> Il giorno sabato 19 gennaio 2013 18:03:34 UTC+1, palomar ha scritto:
>>
>> Other users have the same problem and, sorry but I can't find my
>> solution;
>> i tried with readable=true and writable=true, to update all the field
>> interested in the compute function, to comment the line in DAL.py, but
>> nothing.
>>
>> I have this table:
>> db.define_table('magazzino',
>> Field('id_tipo', 'integer',default=0),
>> Field('p_p','double', default=0.0),
>> Field('pp_tot','double', writable=True, readable=True, compute=lambda
>> r: r['id_tipo']==0 and r['p_p']*1 or r['p_p']*r['id_tipo']*-1),
>> )
>>
>> If I edit a row with a FORM the compute field works but if I edit it in a
>> function with ajax don't...
>>
>> def modArtPrice():
>> newPp = 100
>> articolo = db.magazzino[request.vars.id]
>> articolo.id_tipo=articolo.id_tipo
>> articolo.p_p=newPp
>> articolo.update_record()
>>
>> what's wrong?
>> s.
>>
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[web2py] Re: Web2Py compute fields not working on update
sorry, I posted a new threat about it...
https://groups.google.com/forum/?fromgroups=#!topic/web2py/8RWkVAYVG1c
s.
Il giorno martedì 22 gennaio 2013 23:14:17 UTC+1, Massimo Di Pierro ha
scritto:
>
> What web2py version? I cannot reproduce this.
>
> On Friday, 11 January 2013 14:13:04 UTC-6, palomar wrote:
>>
>> Sorry but I have the same problem; i tried with readable=true and
>> writable=true and to comment the line in DAL.py, but nothing.
>> I have this table:
>> db.define_table('magazzino',
>> Field('id_tipo', 'integer',default=0),
>> Field('p_p','double', default=0.0),
>> Field('pp_tot','double', writable=True, readable=True, compute=lambda
>> r: r['id_tipo']==0 and r['p_p']*1 or r['p_p']*r['id_tipo']*-1),
>> )
>> If I edit a row with a FORM the compute field works but if I edit it in a
>> function with ajax don't...
>>
>> def modArtPrice():
>> newPp = 100
>> articolo = db.magazzino[request.vars.id]
>> articolo.update_record(p_p=newPp)
>>
>> what's wrong?
>> s.
>>
>> Il giorno martedì 21 agosto 2012 18:35:05 UTC+2, Brandon Reynolds ha
>> scritto:
>>>
>>> Thank you so much i got it working. I removed the readable=false and
>>> writable=false and it works on update now. Those are not needed anyway
>>> because when the compute field is added on the model it hides it
>>> automatically.
>>>
>>>
>>> Brandon
>>>
>>> On Thursday, August 9, 2012 2:14:42 PM UTC-6, Deidre wrote:
>>>>
>>>> If you look at issue 822 you will see an example of a thumb that works
>>>> on update. As the comments say, you have to not set writeable to false for
>>>> the thumb. If you do set writeable to false then compute only works on add
>>>> not edit or update.
>>>> So my experience is that compute for images to create a thumb does work
>>>> on update.
>>>> Peter
>>>>
>>>> On Thursday, August 9, 2012 5:04:28 PM UTC+1, Brandon Reynolds wrote:
>>>>>
>>>>> Has anyone found a way to fix this yet? Or is there a thumbnail module
>>>>> out now? Like django's http://djangothumbnails.com/
>>>>>
>>>>> Brandon
>>>>>
>>>>>
>>>>> On Monday, June 18, 2012 10:24:05 AM UTC-6, Brandon Reynolds wrote:
>>>>>>
>>>>>> I have this problem when i try to generate thumbnails. If the field
>>>>>> is empty it inserts the photo thumb into the thumbnail. But when i try
>>>>>> to
>>>>>> update that record the thumbnail doesn't change.
>>>>>>
>>>>>> Here is my model:
>>>>>>
>>>>>> # coding: utf8
>>>>>> from image import THUMBER
>>>>>>
>>>>>> db.define_table('park',
>>>>>> Field('park_name', requires=IS_NOT_EMPTY()),
>>>>>> Field('park_city', requires=IS_NOT_EMPTY()),
>>>>>> Field('park_state', requires=IS_NOT_EMPTY()),
>>>>>> Field('park_address', requires=IS_NOT_EMPTY()),
>>>>>> Field('park_zip', requires=IS_NOT_EMPTY()),
>>>>>> Field('country', default="USA", notnull=True, readable=False,
>>>>>> writable=False),
>>>>>> Field('park_phone', requires=IS_MATCH('[\d\-\(\) ]+')),
>>>>>> Field('park_fax', requires=IS_EMPTY_OR(IS_MATCH('[\d\-\(\) ]+'))),
>>>>>> Field('park_phone_2', 'string',
>>>>>> requires=IS_EMPTY_OR(IS_MATCH('[\d\-\(\) ]+'))),
>>>>>> Field('photo1', 'upload'),
>>>>>> Field('photo_thumb1', 'upload', readable=False, writable=False),
>>>>>> Field('photo2', 'upload'),
>>>>>> Field('photo_thumb2', 'upload', readable=False, writable=False),
>>>>>> Field('photo3', 'upload'),
>>>>>> Field('photo_thumb3', 'upload', readable=False, writable=False),
>>>>>> Field('photo4', 'upload'),
>>>>>> Field('photo_thumb4', 'upload', readable=False, writable=False),
[web2py] Re: compute field doesn't work on update
I had the 2.1 and I've just updated to 2.3 (I hoped to solve the problem...)
request.vars.id is the vars from the ajax call; it works, I'm sure,
articolo.p_p is correctly updated
Il giorno sabato 19 gennaio 2013 18:03:34 UTC+1, palomar ha scritto:
>
> Other users have the same problem and, sorry but I can't find my solution;
> i tried with readable=true and writable=true, to update all the field
> interested in the compute function, to comment the line in DAL.py, but
> nothing.
>
> I have this table:
> db.define_table('magazzino',
> Field('id_tipo', 'integer',default=0),
> Field('p_p','double', default=0.0),
> Field('pp_tot','double', writable=True, readable=True, compute=lambda
> r: r['id_tipo']==0 and r['p_p']*1 or r['p_p']*r['id_tipo']*-1),
> )
>
> If I edit a row with a FORM the compute field works but if I edit it in a
> function with ajax don't...
>
> def modArtPrice():
> newPp = 100
> articolo = db.magazzino[request.vars.id]
> articolo.id_tipo=articolo.id_tipo
> articolo.p_p=newPp
> articolo.update_record()
>
> what's wrong?
> s.
>
--
[web2py] compute field doesn't work on update
Other users have the same problem and, sorry but I can't find my solution;
i tried with readable=true and writable=true, to update all the field
interested in the compute function, to comment the line in DAL.py, but
nothing.
I have this table:
db.define_table('magazzino',
Field('id_tipo', 'integer',default=0),
Field('p_p','double', default=0.0),
Field('pp_tot','double', writable=True, readable=True, compute=lambda
r: r['id_tipo']==0 and r['p_p']*1 or r['p_p']*r['id_tipo']*-1),
)
If I edit a row with a FORM the compute field works but if I edit it in a
function with ajax don't...
def modArtPrice():
newPp = 100
articolo = db.magazzino[request.vars.id]
articolo.id_tipo=articolo.id_tipo
articolo.p_p=newPp
articolo.update_record()
what's wrong?
s.
--
[web2py] Re: Web2Py compute fields not working on update
Sorry but I have the same problem; i tried with readable=true and
writable=true and to uncomment the line in DAL.py, but nothing.
I have this table:
db.define_table('magazzino',
Field('id_tipo', 'integer',default=0),
Field('p_p','double', default=0.0),
Field('pp_tot','double', writable=True, readable=True, compute=lambda
r: r['id_tipo']==0 and r['p_p']*1 or r['p_p']*r['id_tipo']*-1),
)
If I edit a row with a FORM the compute field works but if I edit it in a
function with ajax don't...
def modArtPrice():
newPp = 100
articolo = db.magazzino[request.vars.id]
articolo.update_record(p_p=newPp)
what's wrong?
s.
Il giorno martedì 21 agosto 2012 18:35:05 UTC+2, Brandon Reynolds ha
scritto:
>
> Thank you so much i got it working. I removed the readable=false and
> writable=false and it works on update now. Those are not needed anyway
> because when the compute field is added on the model it hides it
> automatically.
>
>
> Brandon
>
> On Thursday, August 9, 2012 2:14:42 PM UTC-6, Deidre wrote:
>>
>> If you look at issue 822 you will see an example of a thumb that works on
>> update. As the comments say, you have to not set writeable to false for the
>> thumb. If you do set writeable to false then compute only works on add not
>> edit or update.
>> So my experience is that compute for images to create a thumb does work
>> on update.
>> Peter
>>
>> On Thursday, August 9, 2012 5:04:28 PM UTC+1, Brandon Reynolds wrote:
>>>
>>> Has anyone found a way to fix this yet? Or is there a thumbnail module
>>> out now? Like django's http://djangothumbnails.com/
>>>
>>> Brandon
>>>
>>>
>>> On Monday, June 18, 2012 10:24:05 AM UTC-6, Brandon Reynolds wrote:
I have this problem when i try to generate thumbnails. If the field is
empty it inserts the photo thumb into the thumbnail. But when i try to
update that record the thumbnail doesn't change.
Here is my model:
# coding: utf8
from image import THUMBER
db.define_table('park',
Field('park_name', requires=IS_NOT_EMPTY()),
Field('park_city', requires=IS_NOT_EMPTY()),
Field('park_state', requires=IS_NOT_EMPTY()),
Field('park_address', requires=IS_NOT_EMPTY()),
Field('park_zip', requires=IS_NOT_EMPTY()),
Field('country', default="USA", notnull=True, readable=False,
writable=False),
Field('park_phone', requires=IS_MATCH('[\d\-\(\) ]+')),
Field('park_fax', requires=IS_EMPTY_OR(IS_MATCH('[\d\-\(\) ]+'))),
Field('park_phone_2', 'string',
requires=IS_EMPTY_OR(IS_MATCH('[\d\-\(\) ]+'))),
Field('photo1', 'upload'),
Field('photo_thumb1', 'upload', readable=False, writable=False),
Field('photo2', 'upload'),
Field('photo_thumb2', 'upload', readable=False, writable=False),
Field('photo3', 'upload'),
Field('photo_thumb3', 'upload', readable=False, writable=False),
Field('photo4', 'upload'),
Field('photo_thumb4', 'upload', readable=False, writable=False),
Field('photo5', 'upload'),
Field('photo_thumb5', 'upload', readable=False, writable=False),
Field('manager', requires=IS_NOT_EMPTY()),
Field('manager_email', requires=IS_EMAIL()),
Field('spaces', 'integer', requires=IS_NOT_EMPTY()),
Field('vacant', 'integer'),
Field('lot_rent', 'integer', requires=IS_NOT_EMPTY()),
Field('water', 'boolean'),
Field('sewer', 'boolean'),
Field('trash', 'boolean'),
Field('pool', 'boolean'),
Field('playground', 'boolean'),
Field('clubhouse', 'boolean'),
Field('laundromat', 'boolean'),
Field('rv_spaces', 'boolean'),
Field('storage', 'boolean'),
Field('handicap_accessible', 'boolean'),
Field('community_description', 'text'),
format='%(park_name)s')
db.define_table('home',
Field('pid', notnull=True, readable=False, writable=False),
Field('lot'),
Field('year', length=4, requires=IS_NOT_EMPTY()),
Field('make'),
Field('model'),
Field('width', requires=IS_NOT_EMPTY()),
Field('length', requires=IS_NOT_EMPTY()),
Field('wide', requires=IS_NOT_EMPTY()),
Field('for_sale', 'boolean', default=True),
Field('beds', requires=IS_NOT_EMPTY()),
Field('baths', requires=IS_NOT_EMPTY()),
Field('fridge', 'boolean'),
Field('stove', 'boolean'),
Field('dishwasher', 'boolean'),
Field('microwave', 'boolean'),
Field('washer', 'boolean'),
Field('dryer', 'boolean'),
Field('photo1', 'upload'),
Field('photo1_text'),
Field('photo_thumb1', 'upload', readable=False, writable=False),
Field('photo2', 'upload'),
Field('photo2_text'),
Field('photo_thumb2', 'upload', readable=False, writable=False),
Field('photo3', 'upload'),
Field('photo3_text'),
Field('photo_thumb3', 'upload', readable=False, writable=False),
Field('photo4', 'upload'),
Field('photo4_text'),
Field('photo_thumb4', 'upload', readable=False, writable=
Re: [web2py] Re: powerTable AttributeError: 'DAL' object has no attribute 'virtual'
so, with web2py 2.2.1 and powertable: db.acquisti.id_p.represent=lambda id: db.prodotti[id].nomeb #SQLFORM.grid: doesn't work; powertable: works db.acquisti.id_p.represent=lambda id, row: db.prodotti[id].nomeb #SQLFORM.grid: work; powertable: doesn't work Massimo, aiutaci tu! ;) Il giorno sabato 24 novembre 2012 02:40:26 UTC+1, tomt ha scritto: > > I run into the same problem. I don't have a solution other than removing > the row from the represent statement when using powertable. > example: > db.acquisti.id_p.represent=lambda id: db.prodotti[id].nomeb > or > db.task.designer.represent = lambda value: db.staff[value].name > > The problem with this is that it will then generate an error if > SQLFORM.grid is used to display the same table. > > > On Friday, November 23, 2012 1:50:27 PM UTC-6, palomar wrote: >> >> Thanks for your tips but I have one more problem: >> in my model I use represent to view the title instead of the ID of a >> linked table: >> >> #db.acquisti.id_p.represent=lambda id, row: db.prodotti[id].nomeb >> >> that (I think) generate this error whit powertable: >> (() takes exactly 2 arguments (1 given)) >> >> line 286: >> >> elif field.represent: >> r = field.represent(r) >> >> >> Someone can help me? >> ciao ;) >> >> Il giorno venerdì 23 novembre 2012 20:44:02 UTC+1, palomar ha scritto: >>> >>> i think >>> >>> response.files.append(URL(r=request,c='static',f='plugin_powertable/ui/css/%s/jquery-ui-1.8.24.custom.js')) >>> ;) >>> >>> Il giorno giovedì 18 ottobre 2012 06:06:33 UTC+2, tomt ha scritto: >>>> >>>> After a little digging around on the web I found out why I was >>>> powertable was generating errors with the latest web2py. >>>> >>>> jquery version 1.8 requires jquery-ui-1.8.22 >>>> >>>> I went to http://jqueryui.com/ and downloaded legacy v1.8.24 which >>>> provided jquery-ui-1.8.24.custom.zip. This zip file included >>>> jquery-ui-1.8.24.custom.min.js which I then copied to >>>> static/plugin_powertable/ui/js >>>> I modified models/powertable.py to load it: >>>> >>>> >>>> After taking these steps, the error messages are gone and now >>>> powertable works with no problems. >>>> >>>> >>>> >>>> On Sunday, October 14, 2012 9:10:17 PM UTC-6, tomt wrote: >>>>> >>>>> I noticed another problem with powertable and web2py 2.0.9 >>>>> >>>>> When I created a new app under web2py 2.0.9 and tried to implement a >>>>> powertable it exhibited some unusual behaviour. On initial callup, the >>>>> powertable showed all records instead of the number specified by >>>>> iDisplayLength and the columns don't show the column sorting icon. Also >>>>> the >>>>> column id is displayed even though table.showkeycolumn = False >>>>> >>>>> Firebug showed an error in plugin_powertable/jquery.dataTables.min.js: >>>>> "detailed error: TypeError: a.charCodeAt is not a function" >>>>> >>>>> I discovered that if I replaced /static/js/jquery.js with version >>>>> v1.7.1 from an earlier version of web2py, all the powertable problems >>>>> disappeared. >>>>> >>>>> Web2py 2.0.9 uses jQuery v@1.8.0 which apparently triggers the problem >>>>> with powertable. Earlier versions of web2py used jQuery v1.7.1 which >>>>> seems >>>>> to work ok with powertable. >>>>> >>>>> I'm wondering if I can make powertable work if I use a more recent >>>>> version of datatables? Which files from the datatables would I have to >>>>> incorporate? Any suggestions? >>>>> >>>>> - Tom >>>>> >>>>> >>>>> >>>>> >>>>> On Monday, October 8, 2012 5:42:46 PM UTC-6, rochacbruno wrote: >>>>>> >>>>>> Thanks, I will update the repo. >>>>> >>>>> --
[web2py] powertable | insert JSFUNCTION in dtfeatures['fnFooterCallback']
Hi, I'm using the plugin powertable and I need to insert my JS funciont on the footer; the option to change is dtfeatures['fnFooterCallback'] but I have a problem to insert my JS function. What or where I have to insert it? Thanks... --
Re: [web2py] Re: powerTable AttributeError: 'DAL' object has no attribute 'virtual'
Thanks for your tips but I have one more problem: in my model I use represent to view the title instead of the ID of a linked table: #db.acquisti.id_p.represent=lambda id, row: db.prodotti[id].nomeb that (I think) generate this error whit powertable: (() takes exactly 2 arguments (1 given)) line 286: elif field.represent: r = field.represent(r) Someone can help me? ciao ;) Il giorno venerdì 23 novembre 2012 20:44:02 UTC+1, palomar ha scritto: > > i think > > response.files.append(URL(r=request,c='static',f='plugin_powertable/ui/css/%s/jquery-ui-1.8.24.custom.js')) > ;) > > Il giorno giovedì 18 ottobre 2012 06:06:33 UTC+2, tomt ha scritto: >> >> After a little digging around on the web I found out why I was >> powertable was generating errors with the latest web2py. >> >> jquery version 1.8 requires jquery-ui-1.8.22 >> >> I went to http://jqueryui.com/ and downloaded legacy v1.8.24 which >> provided jquery-ui-1.8.24.custom.zip. This zip file included >> jquery-ui-1.8.24.custom.min.js which I then copied to >> static/plugin_powertable/ui/js >> I modified models/powertable.py to load it: >> >> >> After taking these steps, the error messages are gone and now powertable >> works with no problems. >> >> >> >> On Sunday, October 14, 2012 9:10:17 PM UTC-6, tomt wrote: >>> >>> I noticed another problem with powertable and web2py 2.0.9 >>> >>> When I created a new app under web2py 2.0.9 and tried to implement a >>> powertable it exhibited some unusual behaviour. On initial callup, the >>> powertable showed all records instead of the number specified by >>> iDisplayLength and the columns don't show the column sorting icon. Also the >>> column id is displayed even though table.showkeycolumn = False >>> >>> Firebug showed an error in plugin_powertable/jquery.dataTables.min.js: >>> "detailed error: TypeError: a.charCodeAt is not a function" >>> >>> I discovered that if I replaced /static/js/jquery.js with version v1.7.1 >>> from an earlier version of web2py, all the powertable problems disappeared. >>> >>> Web2py 2.0.9 uses jQuery v@1.8.0 which apparently triggers the problem >>> with powertable. Earlier versions of web2py used jQuery v1.7.1 which seems >>> to work ok with powertable. >>> >>> I'm wondering if I can make powertable work if I use a more recent >>> version of datatables? Which files from the datatables would I have to >>> incorporate? Any suggestions? >>> >>> - Tom >>> >>> >>> >>> >>> On Monday, October 8, 2012 5:42:46 PM UTC-6, rochacbruno wrote: >>>> >>>> Thanks, I will update the repo. >>> >>> --
Re: [web2py] Re: powerTable AttributeError: 'DAL' object has no attribute 'virtual'
i think response.files.append(URL(r=request,c='static',f='plugin_powertable/ui/css/%s/jquery-ui-1.8.24.custom.js')) ;) Il giorno giovedì 18 ottobre 2012 06:06:33 UTC+2, tomt ha scritto: > > After a little digging around on the web I found out why I was powertable > was generating errors with the latest web2py. > > jquery version 1.8 requires jquery-ui-1.8.22 > > I went to http://jqueryui.com/ and downloaded legacy v1.8.24 which > provided jquery-ui-1.8.24.custom.zip. This zip file included > jquery-ui-1.8.24.custom.min.js which I then copied to > static/plugin_powertable/ui/js > I modified models/powertable.py to load it: > > > After taking these steps, the error messages are gone and now powertable > works with no problems. > > > > On Sunday, October 14, 2012 9:10:17 PM UTC-6, tomt wrote: >> >> I noticed another problem with powertable and web2py 2.0.9 >> >> When I created a new app under web2py 2.0.9 and tried to implement a >> powertable it exhibited some unusual behaviour. On initial callup, the >> powertable showed all records instead of the number specified by >> iDisplayLength and the columns don't show the column sorting icon. Also the >> column id is displayed even though table.showkeycolumn = False >> >> Firebug showed an error in plugin_powertable/jquery.dataTables.min.js: >> "detailed error: TypeError: a.charCodeAt is not a function" >> >> I discovered that if I replaced /static/js/jquery.js with version v1.7.1 >> from an earlier version of web2py, all the powertable problems disappeared. >> >> Web2py 2.0.9 uses jQuery v@1.8.0 which apparently triggers the problem >> with powertable. Earlier versions of web2py used jQuery v1.7.1 which seems >> to work ok with powertable. >> >> I'm wondering if I can make powertable work if I use a more recent >> version of datatables? Which files from the datatables would I have to >> incorporate? Any suggestions? >> >> - Tom >> >> >> >> >> On Monday, October 8, 2012 5:42:46 PM UTC-6, rochacbruno wrote: >>> >>> Thanks, I will update the repo. >> >> --
[web2py] web2py on HelioHost
HI! I'm a newbie and I would like to try web2py on a free hosting. I found Heliohost <http://www.heliohost.org/home/> but, after installation and following thist post<http://www.helionet.org/index/topic/10963-web2py/page__hl__web2py__fromsearch__1>, I have "500 Internal Server Error". Somebody have already used heliohost? Or somebody can help me with the configuration? Thanks (and sorry for my english...) palomar
