From f7392bc94edbcae4a93e246ca545ea5d0cd36352 Mon Sep 17 00:00:00 2001 From: ShraddhaAg Date: Mar 03 2019 22:06:45 +0000 Subject: [Docs] Add to FAQ the solution to no messages in Archives This commit adds the steps to follow when no sample messages on the main page and no messages in Archives question is raised.The necessary steps are added in the faq.html template. --- diff --git a/docs/faq.rst b/docs/faq.rst index 3d7cc31..43021e2 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -6,13 +6,35 @@ This page contains frequently asked questions about fedora-happiness-packets. It includes troubleshooting steps and other project details. -ERROR: Couldn't connect to Docker deamon at http+docker://localhost-is it running? +ERROR: Couldn't connect to Docker deamon at http+docker://localhost-is it running? Verify the logged in user is member of the docker group. To verify logged in user run:: sudo usermod -aG docker ${USER} - + If logged in user is not member of the docker group add it using:: sudo gpasswd -a${USER} +No sample messages on the main page and no messages in Archives, even though both sender and receiver approved to display message publicily. + + This is due to ``admin_approved_public`` not being set. This has to be done manually using shell. + Steps to resolve: + + 1. Access the shell of the container web using:: + + docker-compose exec web sh + + 2. Acess the Django shell using:: + + python manage.py shell + + 3. Import the ``Message`` model and query the necessary message. + [Assuming the variable ``message`` points to the queried object] + + 4. Set the ``admin_approved_public`` attribute to True and save the modified object:: + + message.admin_approved_public = True + message.save() + + Now when you access Archives, the message can be seen.