On Wed, Jul 25, 2012 at 2:20 AM, Anthony wrote:
> How about I move the Crud section to the end of the chapter, change the
> section heading to "CRUD (Deprecated)", and add the following note at the
> top of the section:
>
> Note: Although the CRUD system described in this section will remain
> av
How about I move the Crud section to the end of the chapter, change the
section heading to "CRUD (Deprecated)", and add the following note at the
top of the section:
Note: Although the CRUD system described in this section will remain
available for backward compatibility, it is no longer recomm
Nop, nothing like that.
Ok, now the behavior is changed. The problem persists just with the boolean
(when I set it to False...i have to submit twice). Text fields are ok now.
It's funny, because i have very straightforward app.
Model:
db.define_table('blog',
Field('naslov','string',label='N
http://www.bennadel.com/blog/2236-Empty-SRC-And-URL-Values-Can-Cause-Duplicate-Page-Requests.htm
http://www.nczonline.net/blog/2009/11/30/empty-image-src-can-destroy-your-site/
--
In your view, do you have any link or any or any ?
My be you have an empty href='' or an empty src='' ?
If you have it, so that is the problem!
empty href or src or rel attributes leads on to form submit problems
--
Can you post a minimalist app or instructions to reproduce the problem?
Could you also open a ticket on google code so this gets tracked? Thanks.
On Tuesday, 24 July 2012 08:56:36 UTC-5, Najtsirk wrote:
>
> I still have the same strange behaviour with SQLFORM.process().
>
>
> On Monday, 23 July 2
I still have the same strange behaviour with SQLFORM.process().
On Monday, 23 July 2012 23:55:49 UTC+2, Najtsirk wrote:
>
> Hi,
>
> each time i want to update crud, i have to submit changes twice to get it
> actually updated.
>
> I set crud.settings.detect_record_change = False, which helps with
Crud is much quicker to implement then SQLFORM (or maybe i just do not
understand it and I'm wrong on that). This was cool for the purpose of
making web app prototypes.
But i agree on the principle to go with one (and better) tool.
Thanks for explanation.
Kristjan
On Monday, 23 July 2012 23:
I think we should but I am afraid people may misunderstand. Crud is not
going away (because of backward compatibility), simply it is no longer the
recommended way to implement the functionality.
On Monday, 23 July 2012 23:16:18 UTC-5, Anthony wrote:
>
> Should we mark Crud as deprecated in the b
I think we should.
On Monday, 23 July 2012 23:16:18 UTC-5, Anthony wrote:
>
> Should we mark Crud as deprecated in the book?
>
> On Monday, July 23, 2012 11:55:14 PM UTC-4, Massimo Di Pierro wrote:
>>
>> Please do not use crud. It is not needed any more. You can do everything
>> and better with S
Should we mark Crud as deprecated in the book?
On Monday, July 23, 2012 11:55:14 PM UTC-4, Massimo Di Pierro wrote:
>
> Please do not use crud. It is not needed any more. You can do everything
> and better with SQLFORM().process().
> We are not going to change the behavior of curd now that we hav
Please do not use crud. It is not needed any more. You can do everything
and better with SQLFORM().process().
We are not going to change the behavior of curd now that we have a more
powerful tool (SQLFORM).
On Monday, 23 July 2012 16:55:49 UTC-5, Najtsirk wrote:
>
> Hi,
>
> each time i want to u
12 matches
Mail list logo
