I don’t know why this occurs:
We have already tried to rebuild the community, but nothing. It works just without logging in. Also, the .JSON file is correct:
Any idea for how to fix it?
I’ve just created a new account. I can see the topic without problems using Firefox.
Clean your browser or try another.
I’m not the unique one…
Other users have the same problem
What are the plugins you use?
I’m one of the admins of this community. On behalf of @barreeeiroo, the plugins we have installed are:
- discourse-adplugin - 1.0.2
- discourse-assign - 0.1
- discourse-backups-to-dropbox - 0.0.2
- discourse-cakeday - 0.2
- discourse-details - 0.4
- discourse-narrative-bot - 0.0.1
- discourse-nationalflags - 1.0.0
- navigation - 0.0.2
- discourse-nginx-performance-report - 0.1
- Discourse presence - 0.1
- discourse-push-notifications - 0.1.0
- discourse-signatures - 1.0.0
- discourse-slack-official - 1.1.1
- discourse-solved - 0.1
- staff-notes - 0.0.2
- discourse-translator - 0.2.0
- discourse-voting - 0.4
- discourse-whos-online - 1.0
- discourse-yuml - 0.1.1
- docker_manager - 0.1
- Whitelist fa tags - 0.1
- lazyYT - 1.0.1
- poll - 0.9
- Discourse Version: v1.9.0.beta4 +90
It’s not just @barreeeiroo some of the topics aren’t displaying for, it also happens to me. Maybe it’s just an issue with staff?
Signatures is broken with markdown-it. So topics will not appear for people with signatures turned on.
I will try to fix it later today. Should be easy.
4 Likes
I’m fairly certain so is discourse-yuml, due to using addPreProcessor.
3 Likes
It was Discourse Signatures
I’ve disabled it and now everything works fine
1 Like
Discourse Signatures 2.0 works on latest version. Please try and report back any issues.
5 Likes
Yes, now it works 
Thanks 
This topic was automatically closed after 2516 days. New replies are no longer allowed.