Notifications not working.

[GoogleCodeExporter]

What version of Chrome are you using? On what operating system?
35.0.1916.47 BETA 
Windows 7 HP x64

What client (version?) are you connecting to? Are you using SSL?
uTorrent 3.4.1.30768
No SSL

What steps will reproduce the problem?
Have no idea

What is the expected output? What do you see instead?
- The notification box should show up every time I add a new torrent using 
remote-torrent-adder
- There is no popup box but torrent are being send to utorrent client
- This option worked before in earlier Google Chrome version just fine. 
- "hit me" button isn't working as well

Original issue reported on code.google.com by amdr...@gmail.com on 16 Apr 2014 at 8:25

[GoogleCodeExporter]

The webkitNotifications api has been removed in both the dev and beta channel 
of Chrome and I assume soon in stable as well.

The chrome.notifications api will have to be used. 
https://developer.chrome.com/apps/notifications

Original comment by th3...@gmail.com on 20 Apr 2014 at 12:09

[GoogleCodeExporter]

in options.js, make the following change.  There is no good way that I am aware 
of to control the duration of the popup.  But they will stack if there are 
multiple.

change this

var notification = 
webkitNotifications.createNotification('icons/BitTorrent48.png', 'title', 'hi, 
this is a test message!');
notification.show();
setTimeout(function(){notification.cancel();}, localStorage['popupduration']);

to this

chrome.notifications.create(
     '' ,{   
    type: 'basic', 
    iconUrl: 'icons/BitTorrent48.png', 
    title: "This is a test notification", 
    priority: 0,
    message: "This is a test message!" 
    },
function() {} 

);

Original comment by jkro...@gmail.com on 21 Apr 2014 at 5:02

Attachments:

• options.js

[GoogleCodeExporter]

in background.js, make the following change.  There is no good way that I am 
aware of to control the duration of the popup.  But they will stack if there 
are multiple.

change this

function displayResponse(title, message) {
    if(localStorage["showpopups"] == "true") {

var notification = 
webkitNotifications.createNotification('icons/BitTorrent48.png', title, 
message);
notification.show();
setTimeout(function(){notification.cancel();}, localStorage["popupduration"]);

to this

function displayResponse(titleit, messageit) {
    if(localStorage["showpopups"] == "true") {

chrome.notifications.create(
    ''  ,{   
    type: 'basic', 
    iconUrl: 'icons/BitTorrent48.png', 
    title: titleit, 
    priority: 0,
    message: messageit 
    },
function() {} 

);

Original comment by jkro...@gmail.com on 21 Apr 2014 at 5:04

Attachments:

• background.js

[GoogleCodeExporter]

Still not working as of 5/11/2014. Windows 8.1, Chrome 36.

Original comment by arcataroger@gmail.com on 11 May 2014 at 7:21

[GoogleCodeExporter]

I'm wondering if author of this extension is still working on it. 

Original comment by amdr...@gmail.com on 11 May 2014 at 2:32

[GoogleCodeExporter]

Attached is a zip of the extension that I have been using for weeks without 
issue.  The only changes are the changes I posted above and it is based on the 
version that the author posted that has added Tixati support.

Unzip this to a directory on your PC
In Chrome, go to Tools-Extensions
Disable your existing Remote Torrent Adder extension
At top, check the box for Developer Mode
At top, click the new box that says Load Unpacked Extension
Select the directory that you unzipped above
You should now how the updated version.  Reconfigure it
Wait for author to release a formal version

Note that each team you start Chrome it will give you a popup box that you are 
using a developer extension.  I am not aware of any way around this

Original comment by jkro...@gmail.com on 11 May 2014 at 3:46

Attachments:

• remote-torrent-adder-0f3bb98e24b8.zip

[GoogleCodeExporter]

Thanks. It's working great !

Original comment by amdr...@gmail.com on 11 May 2014 at 4:25

[GoogleCodeExporter]

N ice work!

Original comment by pax0...@gmail.com on 15 May 2014 at 10:53

[GoogleCodeExporter]

When will this be added to the extension?

Original comment by Joe.Pellett@gmail.com on 16 May 2014 at 12:26

[GoogleCodeExporter]

No one knows. 

I think that the original author of this extension abandoned the project. I 
hope I'm wrong but this is what I think. 

Last update of Remote Torrent Adder is from january 2013. Since then there was 
no update that I'm aware of. 

It's very annoying.

Original comment by amdr...@gmail.com on 16 May 2014 at 5:43

[GoogleCodeExporter]

The author is responsive to my emails but says he is too busy right now to 
release a new version.

Original comment by jkro...@gmail.com on 16 May 2014 at 5:45

[GoogleCodeExporter]

It's good to know that I was wrong :D

I hope that even if we will have to wait for "big" update bringing new 
features, author will at least fix the bugs sooner than later. 

A message from him would be nice. 

Original comment by amdr...@gmail.com on 16 May 2014 at 5:52

[GoogleCodeExporter]

AWESOME! Thank you so much! Changes at the top worked perfectly.

Original comment by Jeff.Ky...@gmail.com on 23 May 2014 at 3:10

[GoogleCodeExporter]

"Note that each team you start Chrome it will give you a popup box that you are 
using a developer extension.  I am not aware of any way around this"

I found a way to fix that. Tutorial is for Windows but should work with Linux 
after modifications. 

0. Remove all Remote Torrent Adder installed in developers mode.
1. Install Remote Torrent Adder from Chrome Web Store.
2. Go to chrome://extensions/ (in your chrome browser)
3. Find Remote Torrent Adder installed from Web Store and copy its ID.
4. Close all Google Chrome windows.
5. Go to %localappdata%\Google\Chrome\User Data\Default\Extensions (might be 
diffrent if your using multiple users in chrome browser)
6. Search for folder with the same name as your extension ID.
7. Open it and go to \1.1.10_0\miscapis (DO NOT close this window). Go to point 
8.
8. Download and extract .zip file from attachment (thanks to jkro...@gmail.com)
9. Go to \remote-torrent-adder-0f3bb98e24b8\miscapis and copy two files: 
background.js and options.js.
10. Past those two files in your opened extension folder. 
11. Thats all. Close all windows and run your Google Chrome browser. 

It worked for me. Should work your all you guys as well. After author of the 
original extension release an update. Chrome should apply it normaly without 
errors. 

Original comment by amdr...@gmail.com on 24 May 2014 at 4:57

Attachments:

• remote-torrent-adder-0f3bb98e24b8.zip

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

OK, the method on post #14 to disable the develop popup worked for me!  Great 
find!!!

For anyone wanting Tixati support, it is more than just those 2 files needed.  
Shut down Chrome and unzip all the files from this zip into you 1.1.10_0 
directory mentioned above.  Replace all the files.  And select Buffalo Webui in 
your configuration but put all your Tixati information in there.   My zip only 
has one file changed from the zip I posted above, the BuffaloWebUI.js.  It 
seems that Chrome is smart enough with these extensions to know there is no 
"addTorrentToTixatiWebUI" function and so it won't work even if a routine 
references it.  So I modified the "addTorrentToBuffaloWebUI" function with the 
Tixati code.

Original comment by jkro...@gmail.com on 24 May 2014 at 6:06

Attachments:

• 1.1.10_0_Tixati.zip

[GoogleCodeExporter]

Since the latest Chrome update, this extension continues to work, but pop-ups 
have  stopped. So I no longer get the visual confirmation that a torrent has 
been successfully added. Not a big deal as I just have to switch to a different 
browser tab to confirm, but a bit less convenient. This seems to be different 
from the other issues discussed in this thread. Any thoughts?

Original comment by mpf...@gmail.com on 25 May 2014 at 5:48

[GoogleCodeExporter]

#18, this discussion is exactly about the pop-ups not working that you 
mentioned.  Follow the instructions in comment #6 to resolve it.  Comment #14 
detailed a further method that can be used to eliminate Chrome warning about 
running extensions in developer mode which is what happens with #6.

Original comment by jkro...@gmail.com on 25 May 2014 at 7:10

[GoogleCodeExporter]

Oops, you're right, it is the same issue. Thanks much!

Original comment by mpf...@gmail.com on 25 May 2014 at 7:16

[GoogleCodeExporter]

Does this still work? It seemed to bring back the "hit me" function when i test 
in in the options, but there's still no popup when i download a torrent...

Original comment by francor...@gmail.com on 7 Jun 2014 at 1:02

[GoogleCodeExporter]

Yes it still works.  When it doesn't popup upon adding a torrent that most 
likely means that the configuration is not right.  And so the torrent didn't 
really get added.  And so there is no popup.

You can check this by verifying whether or not the torrent was added.

In the extensions menu you can find Remote Torrent Adder and click the 
'background page' link and it can show you debug information.  When your login 
doesn't work, it should show you some information.  

I saw a weird issue the other day were it was cutting off the last letter of my 
username.  So I reentered all of the info and it started working.  I think that 
is some type of extension bug and not due to the popup change.

Original comment by jkro...@gmail.com on 7 Jun 2014 at 1:50

[GoogleCodeExporter]

That's the thing, it works fine. I downloaded the zip above and used it, and 
now the "hit me" button works, it pops up, but adding a torrent still won't 
show the popup. But it gets added to the torrent. I'm using ruTorrent webui 
btw, if that's any help.

I don't see the "background page" link. Do I need to turn on some option/switch 
for that to show up?

Original comment by francor...@gmail.com on 7 Jun 2014 at 4:17

[GoogleCodeExporter]

I verified there isn't anything special about rutorrent with respect to the 
message boxes.  So if it used to work it still should.  I am attaching a new 
file that should directly put a "Success" message box no matter what.  This 
should at least give you positive feedback that your submission happened.  
Replace the rutorrent file in the miscapis directory.

Click the 'developer mode' checkbox at the top of the Extensions list and it 
will show the background info link.  I tested it out and it does put error 
messages here although for some types of login errors it also puts a 
notification box.  But that was with utorrent.

I added one line to the file at the end:
    displayResponse("Success", "Torrent added successfully.");

Original comment by jkro...@gmail.com on 7 Jun 2014 at 6:35

Attachments:

• ruTorrentWebUI.js

[GoogleCodeExporter]

I used your file and wow it works. The funny thing is now it shows the popup 
twice. I compared the existing file to yours, and the only difference was the 
display message.

In any case, it's working fine now, i may revert back to the original and see 
if it would still work without the duplicate popup.

Thanks for the help!!!

Original comment by francor...@gmail.com on 7 Jun 2014 at 6:52

[GoogleCodeExporter]

Solution provided here in answer 14 works flawlessly. Thank you for finding and 
fixing the issue. 

Original comment by tr13dg3...@gmail.com on 25 Jun 2014 at 6:58

[GoogleCodeExporter]

While solution in answer 14 works (and thanks), the popup doesn't clear after 
the specified duration. I'm not a js programmer, but after searching the API 
help, I believe that it's possible to get the "old" functionality back using 
the following:

In background.js:

    var opt = {
        type: 'basic', 
        iconUrl: 'icons/BitTorrent48.png', 
        title: titleit, 
        priority: 0,
        message: messageit 
    };
    chrome.notifications.create('id', opt, function(id) {});
    setTimeout(function(){chrome.notifications.clear('id', function() {});}, localStorage['popupduration']);

and in options.js:

    var opt = {
        type: 'basic', 
        iconUrl: 'icons/BitTorrent48.png', 
        title: "This is a test notification", 
        priority: 0,
        message: "This is a test message!" 
    };
    chrome.notifications.create('id', opt, function(id) {});
    setTimeout(function(){chrome.notifications.clear('id', function() {});}, localStorage['popupduration']);

Original comment by david.ea...@gmail.com on 24 Jul 2014 at 9:49

[GoogleCodeExporter]

Version 38.0.2125.58 beta-m (64-bit) disables the extension because "This 
extension may have been corrupted by malware." due to the fix.

Original comment by pax0...@gmail.com on 16 Sep 2014 at 5:05

[GoogleCodeExporter]

go to chrome://flags and check the setting of "Extension Content Verification". 
 Mine is set to default with the same version of Chrome as you and it works.  
Make sure this is not 'enabled'.  I googled that error and that is the setting 
being pointed to.

Original comment by jkro...@gmail.com on 16 Sep 2014 at 6:37

[GoogleCodeExporter]

Here are some more detailed steps:
1. Go to chrome://flags
2. Find the flag "Extension Content Verification" 
(chrome://flags/#extension-content-verification)
3. Set it to "Bootstrap"
4. Relaunch Chrome.
5. Uninstall affected extensions.
6. Add the extensions again.
7. Enjoy your extensions (and don't forget to check the options because they 
get reset).

Original comment by jkro...@gmail.com on 16 Sep 2014 at 6:38

[GoogleCodeExporter]

fixed in r0a49bcb5300b. thanks a lot jkro & david for pointing out the fixed 
syntax.

sorry for making everyone wait for this one. a push to the chrome web store 
will come soon.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:34

• Changed state: Verified

[GoogleCodeExporter]

Issue 106 has been merged into this issue.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:45

[GoogleCodeExporter]

Issue 101 has been merged into this issue.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:47

[GoogleCodeExporter]

Issue 102 has been merged into this issue.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:48

[GoogleCodeExporter]

Issue 103 has been merged into this issue.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:48

[GoogleCodeExporter]

Issue 100 has been merged into this issue.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:48

[GoogleCodeExporter]

Issue 99 has been merged into this issue.

Original comment by jul...@gmail.com on 16 Sep 2014 at 7:51