indie-wiki-buddy
indie-wiki-buddy copied to clipboard
clicking "or, you can see the original page on Fandom (ugh)" when trying to view fandom link causes breezewiki warning page to appear again
when attempting to view the original fandom link, the addon does not detect that i am attempting to view it and as such, instantly goes back to the warning page.
Hmm, I'm not sure if there's a good way for IWB to detect when the user is clicking that link specifically, but perhaps IWB can avoid redirecting back to BreezeWiki if it can detect that the user has navigated to Fandom from a BreezeWiki instance. I shall look into it.
Another possible solution is to ask the BreezeWiki dev to append a query parameter to that link, which IWB can detect.
Hi, this is an issue to me as well. The workaround, turning the extension off for a while, is annoying.
Back in the days when I thought using Wikiwand was a good idea, if I ever needed to use the original Wikipedia, there was a button which simply appended ?oldformat=true
to the standard Wikipedia URL, so the extension would know not to activate and I would see the standard layout.
For Indie Wiki Buddy, I think it should be a little different. Instead of designing a button for this, it should simply append something like fandom=allow
to the "or, you can see the original page on Fandom (ugh)" link, so the extension would be disabled for that URL.
@fabiorzfreitas Thanks for the suggestion! I've pushed a commit to have IWB append a fandom=allow
query parameter to all Fandom links on BreezeWiki (this includes the "ugh" link, as well as some links in the footer). These links won't be redirected back to BreezeWiki. Expect this to the available in the next update, v3.4.0
.
One limitation is that this will only apply for that initial navigation from BreezeWiki to Fandom. If the user continues to navigate on Fandom, they'll be sent back to BreezeWiki. I'm guessing most users would want to stay on Fandom for the duration of that "session". I'll experiment with ways to carry the fandom=allow
as the user navigates. I've got some ideas but not all solutions work in both Chrome and Firefox.
v3.4.0
is now released and includes the change mentioned in the last comment.