I downloaded 5 minutes ago and it gives me this error (see the screen shot).
On Thursday, March 24, 2016 at 5:06:50 AM UTC-4, Dave S wrote:
>
> On Wednesday, March 23, 2016 at 9:41:36 PM UTC-7, Dave S wrote:
>>
>> I've brought up one of my older apps in the beta. Looks like that is
>> working,
On Wednesday, March 23, 2016 at 9:41:36 PM UTC-7, Dave S wrote:
>
> I've brought up one of my older apps in the beta. Looks like that is
> working, except for some layout.html/css issues
>
>
I've now done it with my home app (not an app for home, an app at home).
It's pretty simple, and seems
I've brought up one of my older apps in the beta. Looks like that is
working, except for some layout.html/css issues
-- menu bar is green
-- my logo is missing from the banner.
(but favicon is ok!)
Oh, I caught up with using appconfig.ini in db.py.
For this app, I'd give 3/4 of a thumbs
OK. It is very strange because the code works for me with and without those
lines. I tried with SQL and noSQL and with japanese chars. My guess is that
it depends on the version of the driver that you have. Anyway. We will keep
those lines uncommented.
On Wednesday, 23 March 2016 19:22:28 UTC-5
Correct.
On Wednesday, March 23, 2016 at 7:16:07 AM UTC-7, Massimo Di Pierro wrote:
>
> Making sure I understand. Uncommenting these fixed your problem?
>
> # if not 'charset' in driver_args:
>
> # driver_args['charset'] = 'utf8'
>
>
> Massimo
>
>
>
>
> On Wednesday, 23 March 2016 01:05:35 UTC
Making sure I understand. Uncommenting these fixed your problem?
# if not 'charset' in driver_args:
# driver_args['charset'] = 'utf8'
Massimo
On Wednesday, 23 March 2016 01:05:35 UTC-5, webmas...@trytha.com wrote:
>
> I'm on it, Pierbro!
>
> Ooh, cool, just found a bug in my code that d
I'm on it, Pierbro!
Ooh, cool, just found a bug in my code that didn't account for a user
clicking on a requires_login() link after a server restart resulted in them
being logged out with the page still up. Paying dividends!
テスト成功しました、先輩！！萌〜
Yeah, that seems to have fixed it (at least for thi
Can you provide a simple two lines of code to reproduce the problem with
dev_appserver?
On Tuesday, 22 March 2016 20:03:52 UTC-5, webmas...@trytha.com wrote:
>
> Then, as the Japanese say: ピンポン!
>
> This is disturbing. Massimo thinks he *fixed* GAE database stuff in the
> change from 2.12.2 t
Can you help us with a test? In pydal/adapters/google_adapter.py lines 51/21
# if not 'charset' in driver_args:
# driver_args['charset'] = 'utf8'
Can you uncomment and check if this fixed the problem?
On Tuesday, 22 March 2016 19:15:28 UTC-5, webmas...@trytha.com wrote:
>
> Guess I coul
Then, as the Japanese say: ピンポン!
This is disturbing. Massimo thinks he *fixed* GAE database stuff in the
change from 2.12.2 to 2.12.3, but this is the second thing I've found that
went the exact opposite direction. I wonder if he fixed a bunch of code,
then saved over 2.12.2 with the correct
Nop!
On Tue, Mar 22, 2016 at 8:53 PM, wrote:
> Are you using GAE?
>
> On Tuesday, March 22, 2016 at 5:42:33 PM UTC-7, Richard wrote:
>>
>> I use to store fr uft8 and didn't have any issue with 2.13.4
>>
>> Richard
>>
>> On Tue, Mar 22, 2016 at 8:33 PM, wrote:
>>
>>> It could possibly be somethi
Are you using GAE?
On Tuesday, March 22, 2016 at 5:42:33 PM UTC-7, Richard wrote:
>
> I use to store fr uft8 and didn't have any issue with 2.13.4
>
> Richard
>
> On Tue, Mar 22, 2016 at 8:33 PM, > wrote:
>
>> It could possibly be something specific to GAE. As I said, I don't have
>> time for a
I use to store fr uft8 and didn't have any issue with 2.13.4
Richard
On Tue, Mar 22, 2016 at 8:33 PM, wrote:
> It could possibly be something specific to GAE. As I said, I don't have
> time for a lot of tests right now. Try uploading this in a database
> somewhere: テスト
>
> On Tuesday, March
It could possibly be something specific to GAE. As I said, I don't have
time for a lot of tests right now. Try uploading this in a database
somewhere: テスト
On Tuesday, March 22, 2016 at 5:29:02 PM UTC-7, Richard wrote:
>
> All my functional tests had passed just fine...
>
> Richard
>
> On Tue,
All my functional tests had passed just fine...
Richard
On Tue, Mar 22, 2016 at 8:15 PM, wrote:
> Guess I could have posted here first, but it's not an error in the new
> version, it's in multiple versions:
>
> Unicode is not working in "string" DB entries. WTF mate?
> https://groups.google.co
Guess I could have posted here first, but it's not an error in the new
version, it's in multiple versions:
Unicode is not working in "string" DB entries. WTF mate?
https://groups.google.com/forum/#!topic/web2py/T5eQExgTP1w
On Tuesday, March 22, 2016 at 4:19:15 PM UTC-7, Dave S wrote:
>
> Ne
Never mind, this one is fixed by restarting the web2py instance.
/dps
On Tuesday, March 22, 2016 at 4:16:11 PM UTC-7, Dave S wrote:
>
>
>
> On Monday, March 21, 2016 at 3:38:16 PM UTC-7, Massimo Di Pierro wrote:
>>
>> Please help us check it (for testers version)
>>
>> http://web2py.com/init/def
On Monday, March 21, 2016 at 3:38:16 PM UTC-7, Massimo Di Pierro wrote:
>
> Please help us check it (for testers version)
>
> http://web2py.com/init/default/download
>
> and let us know if it does not work with your code. I will be released as
> stable in 2 days. So better check it sooner rather
On Tuesday, March 22, 2016 at 3:57:26 PM UTC-7, Massimo Di Pierro wrote:
>
> very confused by this traceback. This line:
>
> from upwatcher import uploadwatch
>
> is not in the scheduler code. where is it? In your code? Do you have this
> library installed somewhere? Did it work before?
>
>
It's
very confused by this traceback. This line:
from upwatcher import uploadwatch
is not in the scheduler code. where is it? In your code? Do you have this
library installed somewhere? Did it work before?
Massimo
On Tuesday, 22 March 2016 16:39:06 UTC-5, Dave S wrote:
>
>
>
> On Monday, March 21,
On Monday, March 21, 2016 at 3:38:16 PM UTC-7, Massimo Di Pierro wrote:
>
> Please help us check it (for testers version)
>
> http://web2py.com/init/default/download
>
> and let us know if it does not work with your code. I will be released as
> stable in 2 days. So better check it sooner rather
I assume these print statements(in *gluon/sqlhtml.py*), probably added
while debugging, will be removed in the 2.14.1?
print dbset.query
print tablenames
print tables
Thanks
On Monday, March 21, 2016 at 6:38:16 PM UTC-4, Massimo Di Pierro wrote:
>
> Please help u
22 matches
Mail list logo
