File.save documentation does not mention that contents must be a Django file object

[pauldwaite]

The documentation for the revised FileField (​http://www.djangoproject.com/documentation/files/) documents the replacement for save_FOO_file, File.save(name, content, save=True).

However, as far as I can tell from testing Beta 2, the content to be saved can no longer be a string. It must be an instance of the new Django File class (or at least an object that has a chunks attribute).

The documentation makes no mention of this.

[Julien Phalip]

This request for modifying the docs was, I think, approved by Marty Alchin in : ​http://groups.google.com/group/django-users/browse_thread/thread/d7e9263cd2c5587e

Bumping this to 1.0 as it is likely a common trap for users.

[Julien Phalip]

#8675 was closed as dupe.

[Julien Phalip]

I've attached a patch to fix the bug in the doc and to add some clarification about the need to use a Django File object for storage saving. Can you think of any other place where more clarification is required?

[Julien Phalip]

Fixed doc bug, and added clarification about the expected format for saving files

[John Shimek]

Added clarifiction on conent for the File.save method

[John Shimek]

I think both patches can be used since they clarify different sections of the docs.

[James Bennett]

(In [8759]) Fixed #8641: Documented the fact that file-saving methods must receive a File instance

[Jacob]

Milestone 1.0 deleted