MESSAGING - no messages if you did not click on the checkbox when registering

[camelPhonso]

Steps to recreate:

I've signed up for KINDLY but forgot to click on the next checkbox.

As a result, I don't have access to the messaging feature.

1. When I go to items, I don't see the enquiry button.

However, I can add items for donations and I did post this one - https://cool-creponne-3e1272.netlify.app/item/191

The issue I've got: I've received a message regarding my item, but because I did not click on the check box when registering, I cannot view it. I know that I've got a message because I received the following email:

.

Currently, there is no way for me to change the settings and view the message.

Suggested solution: I think many potential users of our website may not self-identify as refugees, but they may still want to donate items. We can make the messaging feature accessible to all users and possibly delete the checkbox when registering

[camelPhonso]

Hi @nataliiazab - Thanks for adding this issue

Not having a message button is an intended feature as only refugees should be able to receive donations. However, if a refugee has started a conversation with you and sent a message you should be able to see it in your /conversations route, so if that's not happening we will need to triage that potential bug 🤔

I'll try to test this out soon and update here 👍

[camelPhonso]

Hi @nataliiazab I've tested this on my local environment (from the dev branch) and it seems to be working normally. With a refugee user I message my donor account and receive the messages normally.

The one thing we still don't have is a notification showing in the main page that there are new messages (which is planned for the future), but other than that the feature is working as expected.

You mentioned before that you tested this with another contributor, can I just confirm if you were both accessing the same containerised copy of the database when you tested? Since our development environment accesses a local copy of the database you would need to share the same api url in order to interact with the same set of data, or test this with two users logged from the same server. In my case, I logged with one user on my arc browser and another user in my chrome browser

[nataliiazab]

Hi @camelPhonso Sorry that was my fault! I was testing in the deployed environment (link) and in my local one (with the main db) but I did not synch my fork :woozy_face: After synchronising it, I tested again and I can see the messages locally.

Thank you very much for taking the time to test and explain the logic! :bow:

[camelPhonso]

Hi @camelPhonso Sorry that was my fault! I was testing in the deployed environment (link) and in my local one (with the main db) but I did not synch my fork 🥴 After synchronising it, I tested again and I can see the messages locally.

Thank you very much for taking the time to test and explain the logic! 🙇

Ah no worries! I'm glad everything's working as intended 😅

I'm closing this issue now but maybe if you think the documentation for set up needs any additions to avoid a similar mistake in future feel free to make a new issue suggestion for it :)