I have a Sage tier subscription. Unfortunately, while signed in, my players (with advanced writer roles, and then one player who is a co-owner) see ads on World Anvil. This is regardless of device (tablets and windows/ubuntu machines have all had the problem) or browser (among us we have Chrome, Safari, Opera, and Firefox), and is a universal experience for all of them. It has been occurring consistently for the last several months. The ads are intrusive, often full-page ads. Interestingly, just visiting the ordinary world while not signed in doesn't seem to cause these ads, at least not that we have noticed or that external testing has revealed. This could just be anecdotal, though. World is wiki.aen.quest
Unsure of how one could reproduce this without have a role in my world, unless you have a backend login option, but: 1) sign in to world anvil with a role in the world (at least advanced writer or co-owner, but other roles might do it too). 2) navigate to various pages until an ad pops up.
Hello! I have a quick question - are your Co-Owner and Writers that are seeing the ads accessing your world through your world's custom domain? Or are they seeing them through the normal worldanvil.com domain? Or both? For clarification, the custom domain system is ONLY intended for presentation - any authoring (including co-owner, Writers, Editors etc.) should be accessed through the normal WA domain.
Hey there! They are getting the ads when they access it through worldanvil.com—as far as any of us can tell, there aren't any ads on wiki.aen.quest directly
Gotcha - thanks for the clarification. Can you take a screenshot of one of the ads showing? (it will help us identify which system isn't reacting to co-owner status)
Hey there Xuroth--sorry for the late response. Still waiting for one of them to grab me a screenshot, but it may not be til this weekend. Just wanted to put out an update. Thanks!
https://imgur.com/a/iYkPkqc
There are some screenshots from a couple of my players. Thank you so much!
Thanks for the screenshots! I'm communicating this with the backend developers to investigate further!