Code

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#14712 closed (fixed)

Example for post_syncdb signal.

Reported by: frankwiles Owned by: nobody
Component: Documentation Version: 1.2
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

While in retrospect, the documentation for post_syncdb does inform the user it wasn't entirely clear to me that you need to pass the models.py itself as sender and not a specific model. I figured this docs patch might clarify it for others. It adds a simple example at the bottom of the current post_syncdb docs.

Attachments (1)

post_syncdb_example.diff (708 bytes) - added by frankwiles 3 years ago.
docs patch

Download all attachments as: .zip

Change History (4)

Changed 3 years ago by frankwiles

docs patch

comment:1 Changed 3 years ago by gabrielhurley

  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 3 years ago by timo

  • Resolution set to fixed
  • Status changed from new to closed

(In [15104]) Fixed #14712 - Add an example for the post_syncdb signal. Thanks Frank Wiles for the patch.

comment:3 Changed 3 years ago by timo

(In [15105]) [1.2.X] Fixed #14712 - Add an example for the post_syncdb signal. Thanks Frank Wiles for the patch.

Backport of r15104 from trunk.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.