Mattermost v5.29 E10 Academic License Server on Ubuntu 20.04 LTS:
I can no longer access the Marketplace page as it shows up just blank (white).
I can see the Search field and text ‘All plugins / Installed plugins’ as well as ‘Loading …’ for a brief moment before it goes completly white. It did work with v5.28
I tried with Firefox, Chrome (Incognito too) and the Windows App.
Any help is appreciated.
Hello, I’m sorry to hear that you’re having issues. Have you made any modifications to the URL of the Mattermost Marketplace API?
No. I only did the upgrade steps according to the documentation.
Alright, and if you open the Google Chrome Developer’s Console when you load the marketplace, do you see any errors in red? You can open the developers console in google chrome using the keyboard shortcut
ctrl+shift+i or from the side menu under “More Tools.”
Here is a screenshot of what my marketplace looks like when it loads and is processed through the developer’s console, I’m running my instance on Ubuntu 18.04 Bionic.
(Note: I did redact the URL to my install instance for privacy reasons, that’s all that was covered though)
I get these error messages
Alright, so definitely possibly that there is an error in the code then, I would say. @amy.blais would you be able to provide any further insight into this, or is this something that the devs should be notified about?
I contacted support and provided logfiles etc. Hope they will solve this problem.
Thanks for your help.
This looks like it might be caused by a plugin without a description, but there aren’t any such plugins in the marketplace – from the developer console that @XxLilBoPeepsxX kindly demoed, can you capture and share the response payload of the API request to
/api/v4/plugins/marketplace? Note that this will include local plugins that aren’t actually in the marketplace, so be sure to sanitize anything if you don’t want to share it here.
Thanks for the hints. I found that the BigBlueButton plugin is causing this problem. Without it the marketplace page shows up.
The response to the API request is this
Bug was already reported yesterday.