我最近安装了这个插件并设置好了一切，大部分功能都正常工作。用户可以从 Patreon 获得奖励。大多数已经将 Discourse 邮箱与其 Patreon 邮箱共享的用户已立即获得其群组。但是，有一个用户（可能还有更多用户）通过偏好设置将 Patreon 连接到其 Discourse 账户，但没有共享 Discourse 邮箱与 Patreon 账户。我甚至刷新并同步了数据，但他们仍然没有获得群组。有什么原因会导致这种情况发生吗？
如果 Patreon 电子邮件和 Discourse 电子邮件不相同，集成将无法工作。他们需要更新他们在 Discourse 或 Patreon 中的电子邮件。
那连接的意义何在？仅仅是为了登录吗？
我遇到了同样的问题，并且已经仔细检查过电子邮件是否相同。最近，我有很多用户遇到此问题，而以前没有。我尝试手动同步，但它仍然不起作用。
有没有办法查看日志？（我可以提供对我的论坛/安装的访问权限，以便您进行检查）
1 个赞
是的，我让用户将他们的 Patreon 和 Discourse 电子邮件设置为相同，已同步，但他们仍然没有收到奖励。
这有什么原因吗？
请问有什么支持吗？这是一个相当严重的错误，特别是当人们为奖励付费时。
我恐怕对这个插件不太熟悉。最近有一个关于电子邮件验证的问题。这些未同步的用户是否在 Patreon 端验证了他们的电子邮件？
1 个赞
是的，他们的电子邮件已在 Patreon 上得到验证。
1 个赞
嗯。 
按下“更新 Patreon 数据并同步群组”时，控制台中是否有任何错误？
1 个赞
如果您是指“检查元素”控制台，那么没有发生错误。
我已经多次验证电子邮件是相同的。我遇到了多个用户的问题。
是否有办法查看同步日志或类似内容？
是的，我不确定发生了什么，似乎没有人知道，哈哈。
抱歉，这不是我用过的插件，所以我的故障排除工作包括检查近期更改和搜索类似主题。
有一个类似的，里面有一些内容，但它已经很旧了 Patreon Plugin Not Updating
周末这里可能会比较安静，但希望很快就会有有经验的人能阐明一下。
1 个赞
有关于此事的任何更新吗？
我也在此事上跟进一下……
您总共有多少位顾客？
您可以在用户详细信息管理页面中查看顾客详细信息吗？
1 个赞
是在 Patreon 上还是 Discourse 上？
Patreon 页面本身显示有
对于某些用户可以，但对于那些不起作用的用户则不行。
我今天还在错误控制台中发现了这个错误：
Patreon-API : {"errors":[{"code":1,"code_name":"generic-error","detail":"A runtime check failed.","id":"4462cdbf-XXXX-XXXX-86a4-4ddac9780368","status":"403","title":"A runtime check failed."}]}
堆栈跟踪
/var/www/discourse/plugins/discourse-patreon/lib/api.rb:15:in `campaign_data'
/var/www/discourse/plugins/discourse-patreon/lib/campaign.rb:13:in `update!'
/var/www/discourse/plugins/discourse-patreon/lib/patron.rb:9:in `update!'
/var/www/discourse/plugins/discourse-patreon/app/jobs/scheduled/patreon_sync_patrons_to_groups.rb:11:in `execute'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:284:in `with_connection'
rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:77:in `with_connection'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
/var/www/discourse/app/jobs/base.rb:217:in `each'
/var/www/discourse/app/jobs/base.rb:217:in `perform'
/var/www/discourse/app/jobs/base.rb:279:in `perform'
mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:93:in `process_queue'
mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:37:in `block (2 levels) in initialize'
这是我在错误日志中找到的另一个错误：
(patreon) Authentication failure! csrf_detected: OmniAuth::Strategies::OAuth2::CallbackError, csrf_detected | CSRF detected
带堆栈跟踪
omniauth-1.9.1/lib/omniauth/strategy.rb:163:in `log'
omniauth-1.9.1/lib/omniauth/strategy.rb:486:in `fail!'
omniauth-oauth2-1.7.2/lib/omniauth/strategies/oauth2.rb:87:in `callback_phase'
omniauth-1.9.1/lib/omniauth/strategy.rb:238:in `callback_call'
omniauth-1.9.1/lib/omniauth/strategy.rb:189:in `call!'
omniauth-1.9.1/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.1/lib/omniauth/strategy.rb:192:in `call!'
omniauth-1.9.1/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.1/lib/omniauth/strategy.rb:192:in `call!'
omniauth-1.9.1/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.1/lib/omniauth/strategy.rb:192:in `call!'
omniauth-1.9.1/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.1/lib/omniauth/strategy.rb:192:in `call!'
omniauth-1.9.1/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.1/lib/omniauth/strategy.rb:192:in `call!'
omniauth-1.9.1/lib/omniauth/strategy.rb:169:in `call'
omniauth-1.9.1/lib/omniauth/builder.rb:45:in `call'
/var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:50:in `call'
rack-2.2.3/lib/rack/tempfile_reaper.rb:15:in `call'
rack-2.2.3/lib/rack/conditional_get.rb:27:in `call'
rack-2.2.3/lib/rack/head.rb:12:in `call'
actionpack-6.1.6.1/lib/action_dispatch/http/permissions_policy.rb:22:in `call'
/var/www/discourse/lib/content_security_policy/middleware.rb:12:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:361:in `call'
/var/www/discourse/config/initializers/008-rack-cors.rb:25:in `call'
rack-2.2.3/lib/rack/session/abstract/id.rb:266:in `context'
rack-2.2.3/lib/rack/session/abstract/id.rb:260:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/cookies.rb:689:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
activesupport-6.1.6.1/lib/active_support/callbacks.rb:98:in `run_callbacks'
actionpack-6.1.6.1/lib/action_dispatch/middleware/callbacks.rb:26:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/actionable_exceptions.rb:18:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/debug_exceptions.rb:29:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
logster-2.10.1/lib/logster/middleware/reporter.rb:43:in `call'
railties-6.1.6.1/lib/rails/rack/logger.rb:37:in `call_app'
railties-6.1.6.1/lib/rails/rack/logger.rb:28:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:23:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:31:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/request_id.rb:26:in `call'
/var/www/discourse/lib/middleware/enforce_hostname.rb:23:in `call'
/var/www/discourse/plugins/communiteq-features/plugin.rb:119:in `call'
rack-2.2.3/lib/rack/method_override.rb:24:in `call'
rack-2.2.3/lib/rack/sendfile.rb:110:in `call'
actionpack-6.1.6.1/lib/action_dispatch/middleware/host_authorization.rb:142:in `call'
rack-mini-profiler-2.3.3/lib/mini_profiler/profiler.rb:249:in `call'
message_bus-4.0.0/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:198:in `call'
rails_multisite-4.0.0/lib/rails_multisite/middleware.rb:26:in `call'
/var/www/discourse/plugins/communiteq-features/plugin.rb:137:in `call'
railties-6.1.6.1/lib/rails/engine.rb:539:in `call'
railties-6.1.6.1/lib/rails/railtie.rb:207:in `public_send'
railties-6.1.6.1/lib/rails/railtie.rb:207:in `method_missing'
rack-2.2.3/lib/rack/urlmap.rb:74:in `block in call'
rack-2.2.3/lib/rack/urlmap.rb:58:in `each'
rack-2.2.3/lib/rack/urlmap.rb:58:in `call'
unicorn-6.1.0/lib/unicorn/http_server.rb:634:in `process_client'
unicorn-6.1.0/lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn-6.1.0/lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn-6.1.0/lib/unicorn/http_server.rb:143:in `start'
unicorn-6.1.0/bin/unicorn:128:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/bin/unicorn:23:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/bin/ruby_executable_hooks:22:in `eval'
/var/www/discourse/vendor/bundle/ruby/2.7.0/bin/ruby_executable_hooks:22:in `<main>'
但奇怪的是，这似乎是一个身份验证错误，因为我可以按管理插件中的“同步”按钮，并得到“上次同步：刚刚”，而且它确实有效。
你在哪里找到这些日志？