Are you sure you want to go to an external site to donate a monetary value?
WARNING: Some countries laws may supersede the payment processors policy such as the GDPR and PayPal. While it is highly appreciated to donate, please check with your countries privacy and identity laws regarding privacy of information first. Use at your utmost discretion.
Not sure if it's just me, but I've noticed update banners from YoutubeCenter for version 2.1.5, when I'm on v2.1.4.
Shouldn't the userscript auto-update from this site, or is it different from userscripts.org?
Re: @Fironet:
The current metadata block contains these keys:
// @updateURL https://yeppha.github.io/downloads/YouTubeCenter.meta.js // @downloadURL https://yeppha.github.io/downloads/YouTubeCenter.user.js... which is not OpenUserJS (OUJS)... assuming you are using a user.js engine that is capable of updating with these keys. The automatic meta routine here on OUJS is routinely tested just about daily. It is currently working for me with Fx + GM... so look to your user.js engine or the referenced site for downtime/bugs. :)
Re: @Marti:
Huh, strange. I'm using GreaseMonkey, so from what you've described it seems that GM should auto-update from github instead. I know it did for scripts from userscripts.org, so perhaps it's just the checking interval?
Thanks for the info either way, do hope it updates itself.
Re: @Fironet:
Check about:config?filter=extensions.update.interval for your setting. The default is once a day with
86400seconds. You can always do a manual check in about:addons too and see if it appears or updates. Occasionally GM needs a browser restart for an intermittent bug that comes and goes over Fx versions to show the version number correctly.Welcome. :)
Well no updates still. Had hoped it would update itself from Github, but nothing. If it can't update from Github it's unfortunate for users who install from the OUJS site, although from the above description it sounds like it shouldn't make any difference where it's DL'd from.
Re: @Fironet:
That is peculiar. What GM version are you running? Are you Add-ons (Extensions) updating? Did you try in a clean profile to make sure it's not profile corruption? Do you have the version value in your config.xml for that particular script? Once you find this in your config.xml you can shutdown Fx, edit and save that value to an earlier version number, restart Fx and do a manual check to see if the Greasemonkey Updater (GMU) via the Add-on Updater (AOU) is working for any script. Is secure updates on or off in GM? Since it's an .io page on GH it may be misconfigured... although seems to be okay here. Are you running a proxy or a piece of software that might be filtering the checks out?
Re: @Fironet:
Hmm perhaps GH is having some growing pains too.
Getting this on a differently hosted script of mine. :\
Re: @Marti:
Wonder if this affects anyone else with hosted scripts there.
Re: @Fironet:
Since you've confirmed it's an earlier version in the config.xml the redundant test isn't needed.
Try a clean temporary profile with the newest GM release. I don't think there are any real major updating related changes in the code but try with only GM. You can install this script, close Fx, edit the config.xml for this script to an earlier version and try running the update check manually in the Add-ons Manager (AOM)... if it still doesn't do it then it's something outside of Fx... which could still include .io pages... although those work for me with a manual check (version down bump in config.xml). I have checked this sources meta.js and user.js again and everything appears to be in order. shrugs
Re: @Marti:
Oh and newer Fx since GM will require it... you can always go back to 28 if you need to at http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/28.0/