Note on "[id]" replacement on CRUD

[dartg]

Note on "[id]" replacement on CRUD

[BuhtigithuB]

I can apply you PR if you guarrantee me that you made some test and it works properly... You have to know (if you don't already know it) that CRUD is "deprecated" we leaving there, but it not maintain anymore and the core team has no intention to maintaining it in the future. At some point it will disapear... The only usage a developer should have of it is rapid prototyping as proof of concept, but even so, there is not so much advantage not using SQLFORM knowing that you will have to refactoring it if your demonstration is validated... The extra mile involve in using SQLFORM from the start doesn't worth the extra work you will have to refactor you code...

Also in your example I doubt that someone who intent to use next with URL('index') would ever pass the ID of the created record with crud.create() except if your form would be inside your index page controller function, which is not the case in the following example you showed us...

So maybe with :
­

def people():
    form = crud.create(db.person, next=URL('people/[id]'),
                       message=T("record created"))

It would make some sens... But I am curious what the default behavior of :

form crud.create(db.person, message=T("record created"))  # without specifiying the "next" argument

[dartg]

I didn't know CRUD is not maintained anymore. However I don't see what needs testing here, it is just a side note in the documentation. I've noted this issue while using a CRUD form in an old application a year ago and solved it using url_encode=False.

Also, URL("index") is just an example. It is logical to redirect to the record once created, then you need to know its ID. I can edit the issue and put next=URL("show_the_just_created_record/[id]") so it is self-explanatory.