{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihwu6lmeiunturvxtdvyxgtzwz5ozmgogpvw3hk5fmfmh3g6qnkpy",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mjju63itjlj2"
  },
  "path": "/viewtopic.php?t=33298&p=272346#p272346",
  "publishedAt": "2026-04-15T10:06:49.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "this section"
  ],
  "textContent": "> Original GreaseMonkey for PM refuses to check for user script updates if you have auto-updating of extensions in Pale Moon disabled, even if triggered by the user, in which case extensions will be checked, but user scripts will be skipped. I just remembered I deleted this section in the copy of GreaseMonkey I've been using for the last couple of years.\n>\n> I didn't study the meaning of aForced parameter, so just deleting all of these may not be the most correct approach.\n>\n> Edit: I see this value is false on manual check, so I guess it was right to delete all of it.\n\nI have released a new version that fixes this particular issue. If my assumption is right, I think Janek introduced this mechanism, in intention of making the userscripts not check for updates on their own schedule, if the \"Update Add-ons Automatically\" is unchecked. He had that in mind, but I guess he didn't have in mind that this would spawn this bug.\n\nI went ahead and added some lines that would make it possible for you to have the \"Update Add-ons Automatically\" unchecked, but you still want to manually check for updates (From the \"gear\" icon). I also applied a PR from a contributor to make it possible for you to update scripts manually, by right-clicking individual scripts.\n\nIf you have the extension installed on your browser, it should already be updated to the latest version.\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-04-15T10:06:49.000Z"
}