For support with specific websites
Moderator: trava90
Forum rules
Please
always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
- Clear any current output
- Navigate or refresh the page in question
- Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
-
Gemmaugr
- Lunatic
- Posts: 420
- Joined: 2025-02-03, 07:55
Post
by Gemmaugr » 2025-12-06, 04:10
It was working just fine a few hours ago, but now it just shows a blank page.
The console error message is pretty clear cut and self-explanatory. Seems there's not much to do about it, except report it to Next.js (somehow).
Anyone know any workarounds in the mean-time?
Code: Select all
Error: Invariant: Expected document.currentScript to be a <script> element. Received null instead. This is a bug in Next.js.
undefined:1:313
-
adoxa
- Astronaut
- Posts: 580
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Post
by adoxa » 2025-12-06, 06:58
Modify HTTP Response filter workaround.
Code: Select all
[["gab.com",["/\\.js$/",["let e=document.currentScript","return \"\""]]]]
But then there's all the Tailwind CSS problems...
-
Moonchild
- Project founder
- Posts: 38826
- Joined: 2011-08-28, 17:27
- Location: Sweden
Post
by Moonchild » 2025-12-06, 07:13
adoxa wrote: ↑2025-12-06, 06:58
Tailwind
One synonym for tailwind is a "fart". Apply as you will.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
Gemmaugr
- Lunatic
- Posts: 420
- Joined: 2025-02-03, 07:55
Post
by Gemmaugr » 2025-12-06, 08:36
adoxa wrote: ↑2025-12-06, 06:58
Modify HTTP Response filter workaround.
Code: Select all
[["gab.com",["/\\.js$/",["let e=document.currentScript","return \"\""]]]]
But then there's all the Tailwind CSS problems...
Thanks, that helped! I knew I was going to have to use one of your excellent Modify HTTP Response code comments one day, so I had already gotten the addon.
I'm not seeing any Tailwind CSS problems, personally, though. Maybe it's a logged out thing. Sad to hear that those problems exists too.
-
Gemmaugr
- Lunatic
- Posts: 420
- Joined: 2025-02-03, 07:55
Post
by Gemmaugr » 2025-12-06, 19:38
Turns out that they reverted the bad design due to huge amounts of pushback.. for a little while. Now it's back and it's the same problem. The modify code doesn't do anything, but then again, how it's supposed to be used in not intuitive at all in the addon. I can see where to initially paste it but following up in the editor, it just all one string, unlike the previous entry I had. Which has URL, path, search.
-
adoxa
- Astronaut
- Posts: 580
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Post
by adoxa » 2025-12-06, 23:49
If you've only got this filter then the "Filters" text field should be exactly as above. I don't know how you get it to be "one string" without it throwing an error.
-
Gemmaugr
- Lunatic
- Posts: 420
- Joined: 2025-02-03, 07:55
Post
by Gemmaugr » 2025-12-07, 00:04
adoxa wrote: ↑2025-12-06, 23:49
If you've only got this filter then the "Filters" text field should be exactly as above. I don't know how you get it to be "one string" without it throwing an error.
I did have an existing filter, and I think I got it to be one string by using the editor first, and saving it at the first stage. I removed the previous string and it works. Including the wonky Tailwind CSS. Thanks.
How would one go about having multiple strings though?
-
adoxa
- Astronaut
- Posts: 580
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Post
by adoxa » 2025-12-07, 06:37
