I hear you and it makes perfect sense. However, I just quadruple-
checked the model file and I guarantee (no lying this time) that every
IS_DATE() and IS_DATETIME() validator corresponds to a Field of type
'date' or 'datetime" respectively.
--
You received this message because you are subscribed
No this it not the problem than. Yes your traceback:
Traceback (most recent call last):
File "gluon/restricted.py", line 173, in restricted
File "D:/web2py/applications/myapp/controllers/admin.py", line 962,
in
File "gluon/globals.py", line 96, in
File "gluon/tools.py", line 1847, in f
Massimo, I checked all the fields with IS_DATE or IS_DATETIME
validators and all are correctly declared either 'date' or 'datetime'.
However, some of the validators are IS_NULL_OR(IS_DATE()) and
IS_NULL_OR(IS_DATETIME()). Might this cause the ticket, if a field
were None instead of a date/time?
On
We can make it into a plugin.
On Jan 26, 2:58 pm, Jonathan Lundell wrote:
> On Jan 26, 2010, at 10:19 AM, mdipierro wrote:
>
> > Than it bust be an application bug. I think you may have a IS_DATE
> > validator on a 'string' field instead of a 'date' field.
> > You also need to move over the new a
On Jan 26, 2010, at 10:19 AM, mdipierro wrote:
> Than it bust be an application bug. I think you may have a IS_DATE
> validator on a 'string' field instead of a 'date' field.
> You also need to move over the new appadmin(s) into your app. Normally
> this is not required during upgrades since they
Than it bust be an application bug. I think you may have a IS_DATE
validator on a 'string' field instead of a 'date' field.
You also need to move over the new appadmin(s) into your app. Normally
this is not required during upgrades since they become part of your
app. Nevertheless there was an issue
Wiadomość napisana przez weheh w dniu 2010-01-26, o godz. 19:00:
> Massimo, the db is MySQL, not SQLITE. I think this is going to be more
> complicated than what you suggest. I am going to do a wipe and clean
> install. It's been awhile since I upgraded my server's version of
> web2py. I honestly
Massimo, the db is MySQL, not SQLITE. I think this is going to be more
complicated than what you suggest. I am going to do a wipe and clean
install. It's been awhile since I upgraded my server's version of
web2py. I honestly do not like the install mechanism behind web2py.
Seems error prone, as mea
Did you ever edit appadmin in your app?
Please backit up and replace
- controllers/appadmin.py
- views/appadmin.html
with the ones from the new welcome app. This may partially fix your
last two problems.
The main problem is either you have an invalid combination of
validators OR you have corrupted
I just re-downloaded the source from
http://www.web2py.com/examples/default/download
(not the latest dev snapshot) and re-installed it. I couldn't even get
web2py to start. It looked like an incomplete set of files to me.
So, I installed the Windows version on the server and then restarted
web2py
I have to wiat 'til my server is less busy before I can try Thadeus'
and Alex's suggestions. That'll probably be tomorrow morning.
On Jan 25, 10:04 pm, Thadeus Burgess wrote:
> Insight: I put this in the same category as "printer trouble"
>
> -Thadeus
>
>
>
> On Mon, Jan 25, 2010 at 8:55 PM, mdip
Insight: I put this in the same category as "printer trouble"
-Thadeus
On Mon, Jan 25, 2010 at 8:55 PM, mdipierro wrote:
> I have no clue. Please share any insight on this matter.
>
> On Jan 25, 6:45 pm, Thadeus Burgess wrote:
>> I also have noticed an inability to upgrade web2py from an ol
I have no clue. Please share any insight on this matter.
On Jan 25, 6:45 pm, Thadeus Burgess wrote:
> I also have noticed an inability to upgrade web2py from an older
> version to a newer version, I always have to wipe the web2py
> installation, and untar/clone from scratch. I have yet to run int
13 matches
Mail list logo
