Letractively / minimalist

Automatically exported from code.google.com/p/minimalist
0 stars 0 forks source link

Deleted modules reappear #196

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What is the problem? Describe completely:
I created a new module but left it blank.  I then deleted the blank module as 
well as the "Google Reader" and "null" module.  I opened Gmail and edited my 
"Gmail" module options, saving multiple times.  I quit Chrome.  When I relaunch 
Chrome later and go to Minimalist extension options (from extension menu in 
Chrome preferences), all the deleted modules are there again, including my 
blank one.

Minimalist version   -   0.5.20
Relevant core module -   All
Chrome version       -   18.0.1025.11 beta
Operating System     -   OS X 10.7.3 Lion
Language             -   English
Google Apps user?    -   Yes
Other extensions     -   1-ClickWeather for Chrome (v1.1.0.3); Adblock 
(v2.5.16); Docs PDF/PowerPoint Viewer (by Google) (v3.7); Faviconize Google 
(v2.1); Google Mail Checker (v3.2); Hover Zoom (v3.8); Speed Dial 2 (v1.5.9.1)

Please provide any additional information below and attach screenshots if
relevant.

Original issue reported on code.google.com by tyler2e...@gmail.com on 14 Feb 2012 at 1:14

GoogleCodeExporter commented 8 years ago
I'm having the same problem as above, with the same version of Minimalist for 
all, but it only seems to appear in GMail. Un-enabling and then re-enabling 
Minimalist for GMail works, but doing that every time I re-open the browser 
gets old pretty fast.

Minimalist version   -   Minimalist for Everything [Beta] 0.5.20
Chrome version       -   17.0.963.56 m (Release)
Operating System     -   MS Windows 7 Pro (SP1)
Language             -   English
Other Extensions     -   Copy Plain Text 0.1; eMusic Download Manager 1.0; 
goo.gl URL Shortener 0.7.2; YouTube Options for Google Chrome™ (Full 
Version)1.8.61

Original comment by TheBoa...@gmail.com on 24 Feb 2012 at 8:18

GoogleCodeExporter commented 8 years ago
Same as [Issue 124](http://code.google.com/p/minimalist/issues/detail?id=124)

Here is a solution

--- js/libs/background.js.ori   2012-02-24 15:15:02.578952400 +0800
+++ js/libs/background.js       2012-02-26 01:33:22.417749600 +0800
@@ -54,7 +54,7 @@
 };

 minDB.delete = function(i, callback) {
-       var db = html5rocks.indexedDB.db,
+       var db = minDB.db,
                trans = db.transaction(["Modules"], webkitIDBTransaction.READ_WRITE),
                store = trans.objectStore("Modules"),
                request = store.delete(i);

Original comment by jief...@gmail.com on 25 Feb 2012 at 5:46

GoogleCodeExporter commented 8 years ago
After enabling "Developer Mode" and thus revealing "Background.html" and then 
hitting [Esc] to open the window at the bottom for the code, then pasting said 
code above into the area and hitting [Enter], the following error occurred:

> SyntaxError: Unexpected number
 > arguments: Array[0]
 > get message: function getter() { [native code] }
 > get stack: function getter() { [native code] }
 > set message: function setter() { [native code] }
 > set stack: function setter() { [native code] }
   arguments: null
   caller: null
   length: 1
   name: "setter"
   prototype: setter
   > constructor: function setter() { [native code] }
   > __proto__: Object
   __proto__: function Empty() {}
   > apply: function apply() { [native code] }
     arguments: null
   > bind: function bind() { [native code] }
   > call: function call() { [native code] }
     caller: null
   > constructor: function Function() { [native code] }
     length: 0
     name: "Empty"
   > toString: function toString() { [native code] }
   > __proto__: Object
  type: "unexpected_token_number"
> __proto__: Error

Original comment by TheBoa...@gmail.com on 25 Feb 2012 at 6:05

GoogleCodeExporter commented 8 years ago
The method in Issue 124 does not work for me, so I mentioned it here.

Did you try the above one in Comment 2?

Original comment by jief...@gmail.com on 25 Feb 2012 at 6:16

GoogleCodeExporter commented 8 years ago
The method in Comment #2 is what resulted in the error code pasted into Comment 
#3, and thus didn't work, which is why I pasted into Comment #3 in the first 
place. Sorry to not have made that entirely plain.

Original comment by TheBoa...@gmail.com on 25 Feb 2012 at 7:33

GoogleCodeExporter commented 8 years ago
The code lines in [#c2] mean to modify the file `js/libs/background.js`, not to 
type them in the console to execute.

It works here (Chrome 19.0.1049.3 dev-m).

Original comment by jief...@gmail.com on 26 Feb 2012 at 2:42

GoogleCodeExporter commented 8 years ago
Ah! I copied and pasted the entire lot in. HOORAY, this might work then!

I'll try a continually diminishing part of that above until it stops 
complaining then!

Original comment by TheBoa...@gmail.com on 26 Feb 2012 at 3:09

GoogleCodeExporter commented 8 years ago
Clearly this is beyond me. I'll stop trying to do things I can't.

Thanks for your time.

Original comment by TheBoa...@gmail.com on 26 Feb 2012 at 3:12

GoogleCodeExporter commented 8 years ago

Original comment by anst...@gmail.com on 23 Jan 2013 at 12:27