Why does Greasyfork not work?
-
I can no longer use Greasyfork with my chromium browsers. This is the site: https://greasyfork.org/en.
If I click on a link to a particular script in the list, I get a practically blank page with only an error message that it is not working. Why? Safari is fine, and so are Pale Moon and SeaMonkey. So if I want a particular script to add, I need to go to the code page for it with one of the other browsers, copy the code, then paste it into Violentmonkey as a new script. -
@streptococcus You can add userscripts to Vivaldi directly, no need to use an extension. Enable developer mode and simply drag & drop the script unto the extensions page.
-
@luetage
Wow, that works. How would I tell that the script is actually doing anything if it is not obvious, such as changing colours? Also, updating would still involve the same hassles because the page for an individual script will not load.The scripts in Violentmonkey do work, and the workaround I use to get them in there works as well. Updating them works once I get them in there. It is strange that
particular webpages would be blocked somehow by chromium browsers. -
@streptococcus I don’t know, I only run userscripts I wrote myself and update them just like I installed them. When you can’t tell whether a particular userscript works, you probably shouldn’t use it in the first place.
-
@streptococcus I can tell you that GreasyFork works just fine with Vivaldi. I use it on a semi-regular basis, I can install scripts directly with TamperMonkey and they update.
I recommend you have a look at the Devtools network log (F12, Network), and look for blocked/failing request, as well as go through the regular troubleshooting steps like disabling extensions and testing in a clean profile.
https://help.vivaldi.com/desktop/troubleshoot/troubleshooting-issues/ -
It seems to have been Trace that was causing the problem. I changed some settings and then changed them back again, and the problem is still apparently cured.
-
By experimenting with extensions, I discovered that the server problems with Greasyfork are caused by the extension Trace. I have tried adding greasyfork.org to Trace's whitelist, but that does not make any difference. Why is it that only disabling Trace will make it possible to access a script with Greasyfork with Vivaldi, or Slimjet?
-
@Streptococcus said in Why does Greasyfork not work?:
I have tried adding greasyfork.org to Trace's whitelist
When you click to install a script it opens a new tab with your script manager, in my case Tampermonkey:
chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/ask.html?...So probably it won't help to whitelist
greasymonkey.orgif Trace blocks this URL.You did not say what URL the failing page leads to, or what the error message is (a screenshot would help), and did you examine the Devtools network log?
Opening Devtools on a
chrome-extension://URL will open it undocked, and you can try refreshing the failing page. If requests are blocked, then something is blocking.I don't use Trace myself, and from a quick glance it seems to have a lot of configuration options that would need to be examined to figure out where it fails. I also doubt this is specific to Vivaldi, the other browsers you mention testing with are not Chromium-based, so will work totally different.
-
Even this page gives me an error:
https://greasyfork.org/en/scripts/382833-wikipedia-dark-themeThe error:
This page isn’t working
greasyfork.org is currently unable to handle this request.
HTTP ERROR 500Devtools network has Blocked requests checked and the messages at the bottom are:
Failed to load resource: the server responded with a status of 500 () chrome-error://chromewebdata/:1
VM76:6791 crbug/1173575, non-JS module files deprecated.I have no idea what that means, except that something is blocked, which I already know.
The other browser I mentioned was Slimjet, which is also a chromium browser, and is also using Trace.
