problems with add-on version 1.3 - very angry

[Brian Moore]

So i got the update for version 1.3 happy I was.
until
a few days later.

Greasemoneky decided to redownload ALL my scripts again saying that they were "updated".
NONE of the scripts had been "officially" updated by the script author.

So now ALL of my customizations to those scripts have been lost FOREVER.

I thought it was it was random error that caused this but NO, every pc i use that has Firefox and the latest version of Greasmonkey has had every dam script redownload claiming it was "updated".

I am MAD as hell, WHY did this happen?

[Anthony Lieuallen]

On Thu, Oct 4, 2012 at 5:57 PM, Brian Moore <digi...@gmail.com> wrote:

I am MAD as hell, WHY did this happen?

Because sometimes human beings are fallible.

[LWChris@LyricWiki]

How about implementing a warning: generate a hash of the script source
during installation and safe it in the config.xml.
Then, add something like a flag "updateCustomCode" for each script in
the config, which defaults to "false".

Rehash the script file content before an update and require the user to
do anything confirmative if install hash and current hash do not match:
On mismatch and if that uCC flag says "false", display a message box:

-----
Confirm update
-----
A new version of the script "<name>" is available, but it seems you
customized the code.
Updating will overwrite your changes irreversibly! Update the script anyway?


[ Yes, always ] [ Yes, once ] [ Not now ] [ No, never ]

-----

Answer 1: Update, set uCC flag to "true".
Answer 2: Update, set uCC flag to "false".
Answer 3: Don't update, set uCC flag to "false".
Answer 4: Don't update, set uCC flag to "false", disable "autoUpdate".

The flag can be altered from the script's context menu ("Update if
customized") in the script manager.

Chris

[Anthony Lieuallen]

On Thu, Oct 4, 2012 at 6:54 PM, LWChris@LyricWiki <lwc...@gmx.de> wrote:

How about...

It was a bug.  The code already said don't update in this case (locally modified scripts), but the bug overrode that.  Because it was a bug.

[Digideth]

thanks for all the info everyone.

By customization I mean... modified a color, a size, a url.

what makes the script really work I do not touch


OK.

so is this my bug report or is there another place to report?

What other info do you need to help find and squash the bug?


thanks for the help!

Brian

--
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemon...@googlegroups.com.
To unsubscribe from this group, send email to greasemonkey-us...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.

[Anthony Lieuallen]

On Thu, Oct 4, 2012 at 11:39 PM, Digideth <digi...@gmail.com> wrote:

What other info do you need to help find and squash the bug?

It's already fixed, pending release soon.

[Digideth]

OK this is getting ridiculous.

all my scripts on 2 pcs have now been updated 2 times.

what the hell.

Brian

[LWChris@LyricWiki]

Am 05.10.2012 16:31, schrieb Digideth:
> OK this is getting ridiculous.
>
> all my scripts on 2 pcs have now been updated 2 times.
>
> what the hell.
>
> Brian

Until the update for Greasemonkey is deployed, the bug will keep causing
the scripts to update.
Please wait until Greasemonkey is updated to the next version.

[mike cupcake]

On Friday, 5 October 2012 15:31:52 UTC+1, Brian Moore wrote:

OK this is getting ridiculous.

all my scripts on 2 pcs have now been updated 2 times.

I assume you've tried turning off auto-updates in the options?

I just realised I'm still on 1.0b7,  glad to be made aware of this issue before I update.

[Digideth]

yup its off.

Brian

--

You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/greasemonkey-users/-/sdCJGw9f0w0J.

[mjh563]

On Oct 5, 3:31 pm, Digideth <digid...@gmail.com> wrote:
> OK this is getting ridiculous.
>
> all my scripts on 2 pcs have now been updated 2 times.
>
> what the hell.
>
> Brian

This is affecting all my scripts, judging by how much the install
counts have increased over the last couple of days.

Am I right in thinking that it only happens if the script was
installed from a secure (https:) URL or the '@downloadURL' metadata in
the script points to an https: URL? (Assuming 'require secure updates'
is set.)

In an attempt to fix it, I've updated all my scripts with

// @downloadURL http://userscripts.org/scripts/source/[script_no].user.js

so that the next time they auto-update, the download URL will change
to http. I'm hoping that will then stop the updates from happening
again.

[mjh563]

On Oct 6, 12:12 pm, mjh563 <mjh...@yahoo.co.uk> wrote:
> In an attempt to fix it, I've updated all my scripts with
>
> // @downloadURL  http://userscripts.org/scripts/source/[script_no].user.js
>
> so that the next time they auto-update, the download URL will change
> to http. I'm hoping that will then stop the updates from happening
> again.

Well, that didn't work...

If the user disables automatic updates in GM prefs (or for individual
scripts), will that stop it happening?

This seems like a major bug to me. But is it affecting all users? It
sounds as though it should be, but I've seen very few comments about
it (just this thread and one person who reported it to me).

[Miranda Jones]

On Sunday, October 7, 2012 7:31:59 AM UTC-4, mjh563 wrote:

If the user disables automatic updates in GM prefs (or for individual
scripts), will that stop it happening?

No, it doesn't.  I've turned off automatic updates and a script that I wrote keeps updating to the first test version that I put in that had nothing in it but an alert message multiple times a day.  I have to keep opening up the final version that I saved outside of Greasemonkey and re-pasting it in multiple times a day.  I don't even know where it's "updating" from, since this is a script that I wrote, not one that I downloaded from somewhere.

[GmUser]

It would be nice if, when a script is updated, the script that was there is
either backed up to a backup sub-directory, or renamed so that it can be
restored, or whatever. Multiple backup copies to a sub-dir would be my
preference, with some sort of a naming convention. Something simple
like ScriptName[001].user.js, ScriptName[002].user.js would be fine.
It's not like the backup directory is going to end up with a huge number
of files in it. (except in odd cases like the update bug)

Please seriously consider this, as a strong feature request.

[mike cupcake]

On Friday, 12 October 2012 14:38:53 UTC+1, GmUser wrote:

It would be nice if, when a script is updated, the script that was there is
either backed up to a backup sub-directory, or renamed so that it can be
restored, or whatever. Multiple backup copies to a sub-dir would be my
preference,

You could configure pretty much any backup software to do this already,  doesn't seem like it'd be a good use of the GM developer's time.

[Matt Sargent]

I use the free Cobian Backup 10 program to automatically keep a rolling
14 day archive of my script directory. It takes up very little space,
and once set up, you don't even have to think about it. The backup takes
less than 2 seconds to run.

> --
> You received this message because you are subscribed to the Google
> Groups "greasemonkey-users" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/greasemonkey-users/-/Qe4xLw8myOcJ.