ERRORS:
config.Link.owner: (fields.E304) Reverse accessor for 'Link.owner' clashes with reverse accessor for 'Link.owner'.
HINT: Add or change a related_name argument to the definition for 'Link.owner' or 'Link.owner'.
config.SideBar.owner: (fields.E304) Reverse accessor for 'SideBar.owner' clashes with reverse accessor for 'SideBar.owner'.
HINT: Add or change a related_name argument to the definition for 'SideBar.owner' or 'SideBar.owner'.
typeidea.Link.owner: (fields.E304) Reverse accessor for 'Link.owner' clashes with reverse accessor for 'Link.owner'.
HINT: Add or change a related_name argument to the definition for 'Link.owner' or 'Link.owner'.
typeidea.SideBar.owner: (fields.E304) Reverse accessor for 'SideBar.owner' clashes with reverse accessor for 'SideBar.owner'.
HINT: Add or change a related_name argument to the definition for 'SideBar.owner' or 'SideBar.owner'.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The mistake I see a lot of similar information on the Internet, to say that because of all the newly added field names from the conflict solution are added in Settings
WSGI_APPLICATION = 'project name + User'
I can only say that this is the solution most people might use,
but we have to understand the error, the error is the response to an access violation, and the emergence of reverse access violation more than this kind of reason ,
I encountered this problem occurs because the method in Django been altered, when a new field for the return, change parameter access mechanism is caused
to Shimo want to change it, because of the new project it is a user-defined field needs to be filtered, the made changes.
Note: This article is a personal summary for reference purposes only. If other problems arise, regardless of the writer, do not get welfare for business!
If you do not have a summary, or communication and learning, please contact written! qq: 923644827