Solved. I had made a change which involved storing a rows object in the
session. This was working (eliminating some duplicated database queries)
but evidently interfered with ticketing. Now that I've reversed this
ticketing is working fine.
On Monday, December 7, 2020 at 6:42:47 PM UTC-5
UTC-4, David Manns wrote:
>
> In my development environment, on Windows, with web2py 2.18.5, error
> tickets are truncated, no details are displayed. An example is included
> below. The ticket file is only ~2kb, so the stored ticket is actually
> truncated. Any idea why this is happen
In my development environment, on Windows, with web2py 2.18.5, error
tickets are truncated, no details are displayed. An example is included
below. The ticket file is only ~2kb, so the stored ticket is actually
truncated. Any idea why this is happening?
In the same environment /admin/default/er
This is a duplicate of
https://groups.google.com/forum/#!topic/web2py/2oVcXiUCAiE this one
originally seemed to disappear so I resubmitted it.
On Thursday, June 6, 2019 at 11:10:14 AM UTC-4, David Manns wrote:
>
> Here is my table definition:
>
> db.define_table('AccTr
Yes, I'm pretty sure it worked fine with 2.14.6!
On Friday, June 7, 2019 at 5:42:12 PM UTC-4, Dave S wrote:
>
>
>
> On Friday, June 7, 2019 at 8:43:43 AM UTC-7, David Manns wrote:
>>
>> It turns out the orderby is redundant.
>>
>> Field('A
y=
> db.CoA.Name)),
>
> To me, it looks like you are using "name" to reference the COA, instead of
> the ID.
>
> http://www.web2py.com/books/default/search/29?search=IS_IN_DB
>
> *Ben Duncan*
> DBA / Chief Software Architect
> Mississippi State Su
running Python 2.7, web2py 2.18.5
table:
db.define_table('AccTrans',
Field('Timestamp', 'datetime', default=request.now, writable=False),
Field('Bank', 'reference Bank_Accounts', writable=False),#e.g.
PayPal, Cambridge Trust, ...
Field('Account', 'reference CoA',
Here is my table definition:
db.define_table('AccTrans',
Field('Timestamp', 'datetime', default=request.now, writable=False),
Field('Bank', 'reference Bank_Accounts', writable=False),#e.g.
PayPal, Cambridge Trust, ...
Field('Account', 'reference CoA',
requires=IS_IN_DB
puts
an error on the console "*** DO_CLEAR failed Non-numeric breakpoint number
(all})"
On Saturday, October 6, 2018 at 3:07:30 PM UTC-4, Massimo Di Pierro wrote:
>
> We will address this in 2.17.3
>
> On Friday, 5 October 2018 13:52:17 UTC-7, David Manns wrote:
>>
, db.Members.ALL,
left=[db.Colleges.on(db.Colleges.id==db.Affiliations.College),
db.Members.on(db.Members.id==db.Affiliations.Member)], ...
takes no time at all.
On Monday, April 15, 2019 at 12:24:44 PM UTC-4, David Manns wrote:
>
>
> here is my smartgrid (s
here is my smartgrid (simplified to show only essential pieces):
grid = SQLFORM.smartgrid(db.Members, linked_tables=['Affiliations'],
constraints=dict(Members=query),
deletable=False, details=False, editable=True,
create=True)
Members is a table wit
The original version works with 2.18.5 Thank you!
On Thursday, April 4, 2019 at 4:52:37 PM UTC-4, David Manns wrote:
>
> The table in question has a field:
>
> Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
> IS_EMPTY_OR(IS_MEMBERSHIP_YEAR_EN
PS this is not backward compatible to 2.17.2
On Thursday, April 4, 2019 at 4:52:37 PM UTC-4, David Manns wrote:
>
> The table in question has a field:
>
> Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
> IS_EMPTY_OR(IS_MEMBERSHIP_YEAR_EN
at 4:52:37 PM UTC-4, David Manns wrote:
>
> The table in question has a field:
>
> Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
> IS_EMPTY_OR(IS_MEMBERSHIP_YEAR_END())]),
>
> The custom validator is:
>
> class IS_MEMBERSHIP_YEAR_EN
le Drive\Oxcamne Archive\Web
Site\OxCamNE.2.2\gluon\html.py", line 917, in _traverse
newstatus = self._validate()
File "C:\Users\David\Google Drive\Oxcamne Archive\Web
Site\OxCamNE.2.2\gluon\html.py", line 1895, in _validate
raise Exception(msg)
Exception: Validation erro
Created a ticket: https://github.com/web2py/web2py/issues/2170
On Thursday, April 4, 2019 at 4:52:37 PM UTC-4, David Manns wrote:
>
> The table in question has a field:
>
> Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
> IS_EMPTY_OR(IS_MEMBE
The table in question has a field:
Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
IS_EMPTY_OR(IS_MEMBERSHIP_YEAR_END())]),
The custom validator is:
class IS_MEMBERSHIP_YEAR_END(object):
def __init__(self, error_message='Not a membership year end'):
self.error_mess
I recently implemented stripe checkout in my site which runs on
Pythonanywhere. Initially, I followed the recipe in the manual, using
/gluon/contrib/stripe.py. Worked in local test, but failed on my test site
which is a free Pythonanywhere account, although PA say Stripe is
whitelisted.
The of
I know your post is a long time ago, but since I have just been dealing
with the same issue ...
Initially, I followed the implementation described in the web2py manual,
using /gluon/contrib/stripe.py.
This worked locally but not on my (free) test account at PA. I
re-implemented, following the
Thanks, I think this is it. In the normal case session.email would not be
None at this point but I think its possible to force this with the use of
the browser back key after logging off, I hadn't thought of that. Duh...
On Monday, October 8, 2018 at 7:46:59 PM UTC-4, Leonel Câmara wrote:
>
> Lo
A well trodden path through my code seems to fail occasionally as below.
The statement which fails:
rows = db(db.Members.Alias.contains(session.email, case_sensitive =
False)).select()
rows in db.Members contain a column Alias which is 'list:string' containing a
set of alternate
email addresse
I occasionally use the admin debugger package to investigate problems when
running in my test environment on Windows 10 using the source distribution
of web2py and Python 2.7
When I place a breakpoint on the code and execute my test case the
interactive debugger is triggered, and I can step thr
I have this problem too, there are a few forms where for information
clarity I want to show fields which cannot be changed in a particular
context.
On Monday, October 1, 2018 at 7:43:06 AM UTC-4, Awe wrote:
>
> Well, yes I think it breaks something,
> in 2.16.1 this was fine:
> form = SQLFORM.fa
In the past my site has used two variations of login. For internal users
with comprehensive access to our database, it has used a conventional email
+ password implemented via Auth. For a broader population of users who
interact with the site to maintain their membership and register for events
x27;
David
On Monday, March 12, 2018 at 5:56:08 PM UTC-4, David Manns wrote:
>
> This can be demonstrated with the welcome app.
>
> Start web2py
>
> Display the admin page, go into debug, breakpoints and set breakpoint on
> line 9 of the welcome app default.py
>
> Launc
This can be demonstrated with the welcome app.
Start web2py
Display the admin page, go into debug, breakpoints and set breakpoint on
line 9 of the welcome app default.py
Launch the welcome page - the breakpoint is hit.
Click continue ... the welcome page displays
The admin/breakpoint page sti
My app is installed on PythonAnywhere. The PythonAnywhere environment
includes the current web2py distribution 2.14.6 including the admin
console. I simply added my init application to the PA setup web2py project.
On desktop browsers on my PC the admin application works just fine.
If I try to r
I don't agree. Other emails from elsewhere using mail.send() in the
application go out just fine. This despite the 'allow insecure apps' option
being off on the email account used. Only the emails generated by the
auth() registration and password reset processes are affected. There must
be some
On Friday, January 6, 2017 at 6:05:54 PM UTC-5, David Manns wrote:
>
> I don't know how long this has been broken. Login is working, password
> change is working. Noticed this in my local test environment, on Windows,
> running latest 2.14.6 web2py with local sqlite test da
By playing with earlier versions, I established that 2.12.3 did not seem to
have this problem. The problem was in both earlier and later versions.
Don't know if 2.12.3 was the only version without the problem.
On Friday, January 6, 2017 at 6:51:16 PM UTC-5, David Manns wrote:
>
> Run
on() at line 3609)
On Friday, January 6, 2017 at 6:05:54 PM UTC-5, David Manns wrote:
>
> I don't know how long this has been broken. Login is working, password
> change is working. Noticed this in my local test environment, on Windows,
> running latest 2.14.6 web2py with local sql
Running 2.14.6 in production on GAE. Notice can't send the verification's
so can't register or recover passwords. (have another problem with lost
passwords which reported separately).
Using all the standard setup to initialize auth.settings.mailer in db.py
AND that same auth.settings.mailer is
I don't know how long this has been broken. Login is working, password
change is working. Noticed this in my local test environment, on Windows,
running latest 2.14.6 web2py with local sqlite test database. The reset
email is sent out, and looks like:
Click on the link
http://127.0.0.1:8000/in
day, April 22, 2016 at 7:11:36 PM UTC+2, David Manns wrote:
>>
>> I'm resubmitting as this has not been fixed. I understand the problem
>> better and have a workaround.
>>
>> My application runs on GAE and has been stuck on 2.9.12.
>>
>> Runs fine
I'm resubmitting as this has not been fixed. I understand the problem
better and have a workaround.
My application runs on GAE and has been stuck on 2.9.12.
Runs fine in web2py test environment and with 2.9.12 (pre pyDAL)
In both production and SDK GAE various pages fail.
This failure relate
Yes, I saw that, but I don't have git installed, have never used it. I
download web2py in source form from web2py.com. As far as I know, this
includes pyDAL, indeed I assume it must do otherwise I wouldn't be able to
run my database app in web2py test environment. Isn't this what the error
mean
This is probably a stupid question. I'm running on Windows 10 with latest
version of Python 2.7.11 and the latest source code version of web2py.
Actually, I downloaded the source code version 2.14.3 and updated via the
admin console to 2.14.4 and then to 2.14.5.
My application runs fine in the
This problem is still in 2.14.4. This use case suggests the problem is
within form handling, nothing to do with database or adapter.
David Manns
On Monday, April 11, 2016 at 10:06:41 AM UTC-4, David Manns wrote:
>
> There is a similar problem with SQLFORM.factory. E.g:
>
>
There is a similar problem with SQLFORM.factory. E.g:
searchform=SQLFORM.factory(
Field('name', 'string', default='', comment='(start of) last name'),
Field('status', 'string', requires=IS_EMPTY_OR(IS_IN_SET(['Full',
'Student', 'Comp', 'Inactive']))),
Field('paid_year'
Here is the current definition of the relevant table:
#current annual rates based on latest record:
db.define_table('Duesrates',
Field('Date', 'date', default=request.now.date(), writable=False),
Field('Full', 'decimal(5,2)'),
Field('Student', 'decimal(5,2)'))
However, when this table was first
My application runs on GAE and has been running on 2.9.12. In conjunction
with some application changes decided to update web2py to latest version
2.12.3.
Runs fine in web2py test environment.
In both production and SDK GAE various pages fail.
This failure relates to using a set in a validato
My application runs on GAE and has been running on 2.9.12. In conjunction
with some application changes decided to update web2py to latest version
2.12.3.
Runs fine in web2py test environment.
In both production and SDK GAE various pages fail. The first failure I have
looked at in detail conce
Using MARKMIN helper, if the string includes something like "... text
some...@somewhere.com. Another sentence ..." the period following the
email address is incorrectly included in the email link.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/we
I'm trying to build a test database using csv_import_from_file to load an
entire database (I successfully use csv_export_to_file to create a file
from my application running in the GAE SDK; that database was copied from
GAE production using bulk upload).
However, the import process seems to run
Tried this - didn't help
On Thursday, April 10, 2014 5:17:38 PM UTC-4, Sebastian Cambeo wrote:
>
> Try deleting memcache and browser cache
>
> Am Donnerstag, 10. April 2014 21:13:39 UTC+2 schrieb David Manns:
>>
>> I am still seeing this in released version 2.9.5??
&
I am still seeing this in released version 2.9.5??
On Sunday, March 9, 2014 9:04:49 PM UTC-4, Massimo Di Pierro wrote:
>
> This is fixed in trunk.
>
> On Friday, 7 March 2014 21:11:08 UTC-6, Leonardo Pires Felix wrote:
>>
>> Looks like that this is happening with the REDIS too, Upgraded from 2.8.3
It was the 2.9.3 Windows source code in my case - as I discovered
afterwards, a brand new release. The version file has Version
2.9.3-stable+timestamp.2014.03.03.16.38.00.
I backtracked to the version I was using previously 2.8.2 and everything is
fine. I normally use memcache when running on G
Its worse. If the memcache lines are commented out and the alternative line
to connect and put tickets and sessions in the database, it still fails
with both GAE SDK and production, this time with error
ProtocolBufferEncodeError: int64 too big
when executing
session.connect(request, response,
Using db.import_from_csv_file(...) to restore a complete database from a
file created using db.export_to_csv_file(...) used to work.
With 2.8.2 the process (at least in the development environment - I haven't
tried in production environment) loops forever.
The problem seems to be in gluon\dal.p
Here is the solution. The trick that is not well documented relates to how
the new GAE SDK opens service ports.
After starting the application using the launcher the GAE SDK log shows:
2013-12-23 08:32:28 Running command: "['C:\\Python27\\pythonw.exe',
'C:\\Program Files (x86)\\Google\\google_a
> On Wednesday, December 4, 2013 8:46:31 AM UTC-8, David Manns wrote:
>>
>> My application runs on GAE. Using Google's bulk loader I make occasional
>> backups of the database. It used to be that I could use the GAE SDK (appcfg
>> tool in this case) to upload all t
My application runs on GAE. Using Google's bulk loader I make occasional
backups of the database. It used to be that I could use the GAE SDK (appcfg
tool in this case) to upload all the data into the development server on my
development machine, thus creating the full data context for the SDK.
I plan to start with a clean 2.7.4 distribution and re-integrate my
application. Hopefully this will solve the problem.
On Thursday, October 31, 2013 4:52:42 PM UTC-4, David Manns wrote:
>
> Running standalone in the web2py dev environment, errors produce good
> tickets. However, whe
Running standalone in the web2py dev environment, errors produce good
tickets. However, when running in the GAE SDK, all I get is "Ticket
issued: unknown".
I have done these things that I found in the users group:
Attention all users: For pre 2.6 applications to work with web2py
>=2.6,
30 items in the set) on GAE datastore.
>>> Current version does not support 'belongs' on GAE datastore. I have worked
>>> around this and now have my application working again. Thanks Scott and
>>> Massimo.
>>>
>>> On Wednesday, October 30, 20
in. Thanks Scott and
Massimo.
On Wednesday, October 30, 2013 7:39:54 AM UTC-4, David Manns wrote:
>
> Scott is probably right - I will do some experiments to check. Earlier
> versions of web2py supported 'belongs' on GAE so long as the set contained
> 30 or fewer members (by
Scott is probably right - I will do some experiments to check. Earlier
versions of web2py supported 'belongs' on GAE so long as the set contained
30 or fewer members (by experiment, not documented). I can see how this
limited support may have been dropped in a DAL rewrite!
On Tuesday, October 2
This validator is only used if affs is non-empty, I.e. the member has known
college affiliations. Otherwise the standard validator is used, allowing any
college in the table to be selected. In the failure case, affs was non-empty.
So that doesn't seem to be the problem.
--
Resources:
- http://
n a IS_IN_DB somewhere.
>
> On Tuesday, 29 October 2013 08:28:06 UTC-5, David Manns wrote:
>>
>> I have been running my application on GAE using Python 2.7 and web2py
>> 2.4.6.
>>
>> Recently made minor application change and deployed with web2py 2.7.4,
>>
I have been running my application on GAE using Python 2.7 and web2py 2.4.6.
Recently made minor application change and deployed with web2py 2.7.4, the
current version. I am getting an error in at least one part of the
application. The GAE log is attached.
Re-deployed with the same application
dded, and web2py has been
updated to current version 2.3.2. When adding a new user web2py fails:
Traceback
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Traceback (most recent call last):
File "C:\Documents and Settings\David Manns\My
Documents\ocsnedb\gluon\restricted.py", line 2
Thanks,
I added, issue 719.
Reply_to is supported by GAE but the interface doesn't currently
implemented.
The following 2 lines need to be added to web2py.gluon.tools.py at line 600:
if reply_to:
xcc['reply_to'] = reply_to
I had the same problem. Although GAE supports 'reply_to' its not
implemented in web2py.
I inserted two lines in web2py/gluon/tools.py; here is what the code looks
like now:
elif self.settings.server == 'gae':
xcc = dict()
if cc:
x
In my application which is hosted on GAE I have backup/restore
functions which use export_to_csv_file/import_from_csv_file.
While this is not a practical backup/restore for GAE (restore would
take far too long and timeout, so for this purpose I use GAE bulk
loader tool), I have used it in the past
David
On Nov 17, 1:50 am, Massimo Di Pierro
wrote:
> I believe this is a bug and it has already been fixed in trunk and
> nightly build. can you confirm?
>
> On Nov 16, 8:23 pm, Anthony wrote:
>
>
>
>
>
>
>
> > On Wednesday, November 16, 2011 8:39:54 PM U
One of the recent releases has broken computed fields.
My application uses several instances of computed fields. They all
worked perfectly in 1.94.6 to which I have now reverted.
In 1.99.2 (and possibly intervening releases) the behavior of computed
fields is unpredictable. In my case, they are
ntroller manually does it work properly? If so, it must
> > be a wrong type coming from your request.vars, you can try to convert to
> > the proper type int(request.vars.membid) for example.
>
> > Richard
>
> > On Mon, Nov 7, 2011 at 10:44 AM, David Manns wrote:
>
>
In my application I use computed fields in two ways. Examples:
Name is represented in record as separate fields, e.g., Title, First
name, Last name, Suffix. Use a computed field to concatenate last+first
+title+suffix and convert to lower case to make a field for use in
sorting for display.
Use a
; appropriate constraining domain...
>
> doubleIS_FLOAT_IN_RANGE(-1e100, 1e100)decimal(n,m)IS_DECIMAL_IN_RANGE(-1e100,
> 1e100)
> Richard
>
>
>
>
>
>
>
> On Sat, Oct 15, 2011 at 10:15 AM, David Manns wrote:
> > This problem appeared when I moved my application from x
(most recent call last):
File "C:\Documents and Settings\David Manns\My
Documents\ocsnedb\gluon\restricted.py", line 194, in restricted
raise
File "C:/Documents and Settings/David Manns/My Documents/ocsnedb
saved/applications/init/controllers/default.py"
<http
71 matches
Mail list logo
