Track changes made by front-end users

[anupa...@gmail.com]

Hi

I have a web-app that crowdsources information about entities through simple forms. Users can either edit information of an existing entity or add a new entity. I want to track any changes that these users make in a history (like in a wiki) and this history may also be visible to the users in the long run. 

After searching through different solutions/libraries for Django, it seems django-reversion would be very helpful here. I have set it up and done the admin integration but it seems, out-of-the-box  it supports edits made by the admin users only. I added a new entity from the frontend and it didnt appear in the history.

I have seen some SO posts that also discuss the above use-case and django-reversion being helpful. My question is, is django-reversion good for the above usecase? If yes, is there a quick switch/confirguration to track all model changes including those that happen through the app (alongwith user details of users making the changes, again coming in from the app).

thanks a bunch

Anupam

[anupa...@gmail.com]

Sorry, I think I just have to use the API:

https://django-reversion.readthedocs.io/en/stable/api.html#overview

[Dave Hall]

You got it!

--
You received this message because you are subscribed to the Google Groups "django-reversion discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-reversi...@googlegroups.com.
To post to this group, send email to django-r...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-reversion.
For more options, visit https://groups.google.com/d/optout.

[Anupam Jain]

Dave, 

I have been reading many google group posts, issues on the repo, etc. about django-reversion since I started using it yesterday and I must commend your persistence in proactively responding back to queries, for all these years. Thats pretty consistent, is not common and is appreciated. 
(Sorry, not very relevant to this thread but wanted to explicitly mention it somewhere!)

best,

Anupam

On Tue, May 16, 2017 at 3:46 PM, Dave Hall <da...@etianen.com> wrote:

You got it!

On Tue, 16 May 2017 at 11:15 <anupa...@gmail.com> wrote:

Sorry, I think I just have to use the API:

https://django-reversion.readthedocs.io/en/stable/api.html#overview

On Tuesday, May 16, 2017 at 12:48:24 PM UTC+5:30, anupa...@gmail.com wrote:

Hi

I have a web-app that crowdsources information about entities through simple forms. Users can either edit information of an existing entity or add a new entity. I want to track any changes that these users make in a history (like in a wiki) and this history may also be visible to the users in the long run. 

After searching through different solutions/libraries for Django, it seems django-reversion would be very helpful here. I have set it up and done the admin integration but it seems, out-of-the-box  it supports edits made by the admin users only. I added a new entity from the frontend and it didnt appear in the history.

I have seen some SO posts that also discuss the above use-case and django-reversion being helpful. My question is, is django-reversion good for the above usecase? If yes, is there a quick switch/confirguration to track all model changes including those that happen through the app (alongwith user details of users making the changes, again coming in from the app).

thanks a bunch

Anupam

--
You received this message because you are subscribed to the Google Groups "django-reversion discussion group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to django-reversion+unsubscribe@googlegroups.com.
To post to this group, send email to django-reversion@googlegroups.com.

Visit this group at https://groups.google.com/group/django-reversion.
For more options, visit https://groups.google.com/d/optout.

--

"What is meditation?" (http://www.heartfulness.org/)