Sorry if this high jack isn’t allowed! But why haven’t mattermost included their own giphy key? I tried to get my key upgraded to a production key and it failed since it didn’t comply with their terms. Is everyone just gonna use a beta key?
We keep Mattermost config in the database. I updated the server to 8.1.3, obtained SDK key from GIPHY and updated SDK key in configurations table in mattermost database. It didnt work. I noticed that after Mattermost restart the value is being overwritten with empty string. Tried multiple times with the same behaviour.
@mayqueeen after upgrading to 8.1.3, is the gif picker not working for you ? This version had a fix that included Giphy as the new gif provider pre-configured and ready for production use out of the box. There shouldn’t need any config changes necessary.
@mayqueeen When I upgraded to 8.1.1, I had to go to developers.giphy.com to create an app and get a sdk key. Once I got the key, I put it in the config.json under “GiphySdkKey”: “paste sdk giphykey here” option in order for gifs to work. I had to restart the mattermost service after I got the key in the config before the gif picker would work, If I remember correctly. I don’t think there is a giphy key in the selfhosted download that is usable as that option was empty…unless something has changed with later 8.1 versions.
Perhaps, nevermind on my reply…upon re-reading your post, you may have a different issue? Seems like the difference is you have the config in the database, while my config is under the config folder under the mattermost installation folder.
Our emoji picker is still broken in Mattermost Version: 8.1.2, Database Schema Version: 113. Our install is bundled with gitlab-ce. I don’t see a GiphySdkKey in our /etc/gitlab/mattermost-config.json file, so perhaps that config wasn’t adequately migrated.
edit: correction, i was wrong, the GiphySdkKey did exist, and was set to empty string. Using our own generated key in that config did fix the emoji picker.
@mayqueen after more investigation, we did find an issue where the Giphy production key was not being set properly for our team edition versions. This is now fixed and you can expect this to be working in the following upcoming dot releases: