[Anna Iosif, Ushahidi] @chiefObiorah_twitter Try following the guides here https://docs.ushahidi.com/platform-developer-documentation/development-and-code/setup_alternatives/setting-up-the-platform-client to setup the platform client thumbsup emoji:skin-tone-3:
I just set up this test platform, https://ireport.majalisah.com, and can't seem to be able to login in with either admin@example.com or the email address I configured with crontab -e or even admin/admin option. How could I get around this, please?
@webong upon trying to signup I got the error shown on this screenshot https://prnt.sc/1nfh8dq. Dunno what I have got wrong.
@webong I would also want to know how to force an HTTPS redirection. In Ushahidi version 2 web, there's a setting at the backend that helps one to achieve this. On the latest version, there seems to be such functionality on the document root's .htaccess but after uncommenting the recommended lines, there's no forced HTTPS redirection achieved.
@tuxpiper the actual file where the HTTPS redirection was mentioned could be found in this screenshot: https://prnt.sc/1q52vya
Hi all, I'm trying to use Ushahidi API (media endpoint to be more precise). So I'm trying to fetch all media objects by using GET method of /media endpoint. But I get response 405 (method not allowed). I'm using ushahidi version 5.1.1. If I try to use GET /media/{media_id} then it works. On another instance (version 4) I can use this endpoint without any error. Any help/advice would be appreciated
Another issue that I have is with POST /media (uploading new media). I cannot get file extension stored in the original_file_url. And when I try to access this link without the extension it offers download and not preview since the browser cannot recognize the mime type. I'm using python and I'm retrieving images from URL and uploading them to ushahidi
headers_media = {'Authorization': "Bearer " + access_token}
img = Image.open(requests.get(image_url, stream=True).raw)
img_format = img.format
img_byte_arr = BytesIO()
img.save(img_byte_arr, format=img_format)
img_byte_arr = img_byte_arr.getvalue()
files = {'file': img_byte_arr}
response = requests.post(USHAHIDI_BASE_URL + USHAHIDI_API_VERSION + '/media', files=files, headers=headers_media)
[David Losada, Ushahidi] @dcardinal is the “AllowOverride all” configuration directive applied to the folder where Apache is serving the Ushahidi Platform from?
[David Losada, Ushahidi] @dcardinal this directive: https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride . In order for .htaccess files to actually have any effect, config overriding must be allowed from the apache configuration file, under the <Directory> section you probably have inside the <VirtualHost> definition
@tuxpiper I added these code just below the
RewriteEngine On on the .htaccess file in the root directory and the full HTTPS redirection took effect:RewriteCond %{HTTP_HOST} !^www\.RewriteRule ^(.*)$https://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L]RewriteCond %{HTTPS} offRewriteRule ^(.*)$https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
[cecilia hinga, Ushahidi] Hello @dcardinal for the favicon, sign up on gravatar.com or if you already have an account, add the email address you used to create your deployment, add an image for that email address and it will be automatically displayed as your favicon.
Hello @sameroom-bot, Cecilia Hinga, how could I insert a favicon here https://prnt.sc/1qh3tsz. That of the user login section worked great with the gravatar.com signup but how could I insert a favicon on the title bar section of the browser, see screenshot: https://prnt.sc/1qh3tsz.
@tuxpiper @webong greetings guys. I am currently testing the plattform release which is kind of all-in-one unlike the predecessor that has both the platform and client versions separate. I am having issues linking the deployment to the mobile app. This https://prnt.sc/1sek1yr screenshot shows the error message. Is there a workaround? This https://github.com/ushahidi/platform-release/releases/tag/v5.1.1 is what I deployed and it's not connecting to the mobile app.
[David Losada, Ushahidi] @dcardinal “watch group.com” doesn’t seem to be a valid domain name (they usually don’t contain blank spaces, I believe). What is the address that you type in the browser’s address bar in order to access your deployment? that same address would be what you should provide to the mobile app as well
@tuxpiper many thanks David for your quick response, this is the correct screenshot, https://prnt.sc/1seuytw, the domain in question is watchngr.com. Autocorrect error led to the wrong screengrab that resulted in sending the wrong one.
[David Losada, Ushahidi] right, I see there is a redirect from watchngr.com to www.watchngr.com the app is probably being stumped by that. Can you please try www.watchngr.com ?
@tuxpiper thanks a lot David by your unwavering attempt to help lead me out of the woods. www.watchngr.com didn't work either. The deployment as I stated earlier is built with the platform release https://github.com/ushahidi/platform-release/releases/tag/v5.1.1 and not the unification of the platform and platform-client components. Could this be the cause of this?
[David Losada, Ushahidi] @dcardinal , I see in https://www.watchngr.com/config.json
…
"backend_url": "watchngr.com",
…
}
`\{…
"backend_url": "watchngr.com",
…
}
``
thatbackend_url` doesn’t seem very tight because it doesn’t specify the protocol and because of the redirection mentioned before. If you could edit that file in your server and change that value for https://www.watchngr.com , that may work.