kawa_v

Problems to see the NSFW (Patreon)

Published:

2018-11-07 18:20:22

Edited:

2018-11-12 11:44:44

Imported:

2021-02

Content

Recently, a Patron told me that he had problems with my website, he can not see the NSFW. You can read the conversation here.

So, I need to ask if someone has the same problem.

I do not know what is happening! Why can not he synchronize? D:

My last option is to change the Access Tokens (I don't know how this works), but I think that means that aaaaall user need to resync (and I want to avoid that)

Ah! I took the opportunity to do a tutorial explaining how to sync and to see the exclusive content... (Tutorial: http://kawa-v.com/how-sync-with-patreon/)

EDIT:

I asked on the official forums of Patreon Plugin. They said:

"Its unlikely that it is tokens or anything similar."

So, no tokens.

"Since other people are able to have everything normally, chances are high that the other users are encountering various situations due to their browser/device, or even isp.

Browser caching on some browser/device combinations may be more aggressive. In some cases some isps may be doing caching in their proxy servers, causing stale pages to be served at times. Depends on the quality of isp."

Well, I do not think the problem is the isp.

"There is also a chance that those users have issues with their cookies due to their os/antivirus setup.

Asking them to try from other devices with other browsers and seeing if the issue persists may provide pointers."

I'm not sure about the antivirus, but we can try from other browsers, right?

"Also, your wp site’s cachung plugin must not be set aggressively. Ie you shouldnt have any option that says ‘cache pages for known (logged in) users’ on etc."

Hmmm... I had a cache plugin, but it has been disabled for several months. I've deleted it just in case.

In summary, the official support says that the problem could be the cache. I do not think that is the problem because the cache usually lasts for days / hours and this problem has persisted for a longer time, but please, clear your cache and try again.

At least to rule out problems.

Sorry for the inconveniences D: