Patreon error in the dashboard...Won't go away

AI-generated summary

A user, tommeyboy, encountered an error in their Discourse dashboard after mistakenly enabling and then disabling the Patreon plugin. The error message states that the Patreon creator access token and refresh token values are wrong. vinothkannans acknowledged the issue, stating that a successful sync or disabling the plugin should remove the error message.

vinothkannans later added an expire time for the admin problem message, which will automatically remove it after 7 hours. However, this update may not resolve the issue for tommeyboy since the error message was already added.

vinothkannans suggested running a command in the console to clear the problem message, but tommeyboy does not have shell access or access to the /admin/upgrade page.

When I was setting up discourse, I was playing around with all the different plugins and I mistakenly enabled pantreon. I have since disabled the plugin, but I’m still getting the following errors:

Some problems have been found with your installation of Discourse:

  • Patreon creator access token and refresh token values in your site settings are wrong.

Last checked: July 31, 2018 1:20 PM Refresh


How do I clear the error?

-T-

It’s already in my list for a while. I will try to fix it soon.

Thank you. I’ll keep an eye out for the update. :slight_smile:

I added expire time for the admin problem message. So it will get removed automatically after 7 hours.

awesome. My discourse forum is currently hosted on nodechef. How will these updates get pushed out to other hosting companies?

I am not sure about their hosted option. Normally you can upgrade any plugin by navigating to the URL /admin/upgrade. Else you should contact them.

Also I realized since the error message is already added in your case the above solution may not work for you. So I recommend you to run the below command in your console.

cd /var/discourse
rails c
AdminDashboardData.clear_problem_message(Patreon::Api::ACCESS_TOKEN_INVALID)

Thanks. Unfortunately, I don’t have shell access or access to /admin/upgrade.