Opened 9 years ago

Closed 9 years ago

#2268 closed defect (invalid)

https-everywhere no clobber option!

Reported by: rosc2112 Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


When upgrading the https-everywhere addon, it should NOT clobber existing files which may have been customized. It deletes all of my custom-made files, as well as clobbering its own included xml rule files. BAD BAD BAD! I call this a major bug.

At least give us a no clobber option!!

Child Tickets

Change History (2)

comment:1 Changed 9 years ago by pde

Priority: majornormal

Hi rosc2112,

Sorry you had your rulesets clobbered! I know that sucks. We will try to fix this if possible, but the extension upgrade process is largely controlled by the browser itself I'm not sure if there's any hook we can get to learn if HTTPS Everywhere specifically is about to be upgraded.

(Mike, do you know if there's an observer we could use for this?)

Perhaps we should be clearer in advising people to make sure they use their profile's ruleset directory instead of editing the extension's rulesets in place.

comment:2 Changed 9 years ago by rransom

Resolution: invalid
Status: newclosed

Firefox replaces the contents of an extension's directory whenever it updates the extension. There is nothing that the authors of HTTPS Everywhere can do to prevent this.

If you are only adding new rules to HTTPS Everywhere, put your ruleset files in the HTTPSEverywhereUserRules directory, which is not clobbered when HTTPS Everywhere is updated or reinstalled.

If you are making other changes to HTTPS Everywhere, there are at least three options:

  • store your changes in a Git repository, use the provided Makefile to build a new XPI, and install your XPIs manually;
  • store your changes in another directory, install your modified extension by copying the contents of your HTTPS Everywhere directory into the Firefox HTTPS Everywhere extension directory, and never allow Firefox to update HTTPS Everywhere; or
  • store your changes in another directory, put a text file containing the path to your HTTPS Everywhere directory in the Firefox extensions directory, and never allow Firefox to update HTTPS Everywhere.
Note: See TracTickets for help on using tickets.