Added the ability for superuser or creators "remove" / hide the post from the feed#52
Added the ability for superuser or creators "remove" / hide the post from the feed#52Pdzly wants to merge 4 commits into
Conversation
isik-kaplan
left a comment
There was a problem hiding this comment.
Awesome PR, I just have some nitpicks as always
Also I wasn't planning on removal of posts so people who bookmarked posts can always come back and see the posts they bookmarked but we can add it as a separate feature so if someone bookmarks a post it is automatically added to a hidden library so even if the original is deleted/hidden we can let them keep it in their own library
And maybe as a followup we can add a feature similar to repost detection and not allow reposts of previously hidden posts (if a superuser hid them) so less moderation is required. Not in this PR though obviously
| admin.site.unregister(SocialToken) | ||
| admin.site.unregister(SocialAccount) | ||
| admin.site.unregister(EmailAddress) | ||
| # admin.site.unregister(EmailAddress) |
There was a problem hiding this comment.
Whoops sry, as i can not migrate down, i had to redo all so i did it like #7 forgot to undo this. Sry
The reason why i cant migrate down is, the user "wsd" is not available from the host machine and even if i expose the network to the public it always says password is wrong for the user wsd.
This works but it still gets a warning that the runtimewarning.
python manage.py makemigrations core
RuntimeWarning: Got an error checking a consistent migration history performed for database connection 'default': connection failed: connection to server at "127.0.0.1", port 5432 failed: FATAL: password authentication failed for user "wsd"
… handlers, models, serializers, API endpoints, triggers, and UI.
|
@isik-kaplan i am unsure as Posts will still be visibible for example in the Profile view, as that is a server component. And should i make that a client? or what would you do? or is it just ok that it would just show the user "Post not found" message there. Added a "Hidden" flag for the superuser. |
|
I dont know if it is a good idea to keep "hidden" posts of the users data. ( i know most things arent OC but still... could become a drama if a user wants their data gone or hidden but some bookmarked post stays. ) If you want to do it, then just ignore the is_hidden attribute = the bookmarked result. |
Only a superuser can restore it.
@isik-kaplan i know already i will have to rewrite a lot of things as i am not sure how to handle this correctly.