{"action":"created","issue":{"url":"https://api.github.com/repos/etianen/django-reversion/issues/465","labels_url":"https://api.github.com/repos/etianen/django-reversion/issues/465/labels{/name}","comments_url":"https://api.github.com/repos/etianen/django-reversion/issues/465/comments","events_url":"https://api.github.com/repos/etianen/django-reversion/issues/465/events","html_url":"https://github.com/etianen/django-reversion/issues/465","id":118213506,"number":465,"title":"Problem with proxy models and inlines","user":{"login":"RamezIssac","id":6247918,"avatar_url":"https://avatars.githubusercontent.com/u/6247918?v=3","gravatar_id":"","url":"https://api.github.com/users/RamezIssac","html_url":"https://github.com/RamezIssac","followers_url":"https://api.github.com/users/RamezIssac/followers","following_url":"https://api.github.com/users/RamezIssac/following{/other_user}","gists_url":"https://api.github.com/users/RamezIssac/gists{/gist_id}","starred_url":"https://api.github.com/users/RamezIssac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RamezIssac/subscriptions","organizations_url":"https://api.github.com/users/RamezIssac/orgs","repos_url":"https://api.github.com/users/RamezIssac/repos","events_url":"https://api.github.com/users/RamezIssac/events{/privacy}","received_events_url":"https://api.github.com/users/RamezIssac/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":27,"created_at":"2015-11-21T18:31:14Z","updated_at":"2015-12-16T12:16:16Z","closed_at":null,"body":"Use case: model and a sub model, both are proxies, created and edited via admin using inline,\r\nProblem: The history view show only changes done to the parent model.\r\nin other terms:\r\nRecorded changes for proxy models within inlines are not visible on the history view\r\n\r\nDuring investigation, i noticed in the version table, changes recorded foreignkey content_type to concrete model.  (changes in parent proxy are recorded pointing to concrete model, same with the child model)\r\nwhile in django_admin_log -as example- ,  changes (in parent or child) are recorded pointing to the parent proxy model, which makes it easier to retrieve.\r\n\r\nHow can i go about solving the Problem? any hints where to start ?"},"comment":{"url":"https://api.github.com/repos/etianen/django-reversion/issues/comments/165089809","html_url":"https://github.com/etianen/django-reversion/issues/465#issuecomment-165089809","issue_url":"https://api.github.com/repos/etianen/django-reversion/issues/465","id":165089809,"user":{"login":"RamezIssac","id":6247918,"avatar_url":"https://avatars.githubusercontent.com/u/6247918?v=3","gravatar_id":"","url":"https://api.github.com/users/RamezIssac","html_url":"https://github.com/RamezIssac","followers_url":"https://api.github.com/users/RamezIssac/followers","following_url":"https://api.github.com/users/RamezIssac/following{/other_user}","gists_url":"https://api.github.com/users/RamezIssac/gists{/gist_id}","starred_url":"https://api.github.com/users/RamezIssac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RamezIssac/subscriptions","organizations_url":"https://api.github.com/users/RamezIssac/orgs","repos_url":"https://api.github.com/users/RamezIssac/repos","events_url":"https://api.github.com/users/RamezIssac/events{/privacy}","received_events_url":"https://api.github.com/users/RamezIssac/received_events","type":"User","site_admin":false},"created_at":"2015-12-16T12:16:16Z","updated_at":"2015-12-16T12:16:16Z","body":":)  One more idea:\nwe can make the behavior also controllable -project wide- via an option,\nalong side with the per model registration.\n\nI'm very happy we reached this point.\nGreat work man !!\n\nShall I work on a PR for this?\nOn Dec 16, 2015 1:17 PM, \"Dave Hall\" <notifications@github.com> wrote:\n\n> Yes, perfect. :)\n>\n> On Wed, 16 Dec 2015 at 10:45 Ramez Ashraf <notifications@github.com>\n> wrote:\n>\n> > Very Cool, A tiny detail left, the admin \"implicit\" registration .\n> > Add an admin option reversion_for_concrete_model maybe ?!\n> >\n> > —\n> > Reply to this email directly or view it on GitHub\n> > <\n> https://github.com/etianen/django-reversion/issues/465#issuecomment-165063446\n> >\n> > .\n> >\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/etianen/django-reversion/issues/465#issuecomment-165070220>\n> .\n>\n"}}