yodadacoda / chrome-transmission-remote-plus Goto Github PK

Recent update broke the download popup option. Unchecking the box on the options page does not supres the popup dialog anymorel

Now the default behavior on install is that it is not checked, and the dialog appears. Relentlessly

When I use KickassTorrents to search for shows, the magnet link isn't picked up by RT.
I reported this in the Chrome Store that it worked on the search results page but not on the show organization page. Well it has since changed and the magnet links don't work on any of the pages.

I'm guessing it is something on their site as magnet links work on other sites.

Thanks

Otherwise that debug statement clutters the console for everyone. See:

https://github.com/jeffehobbs/chrome-transmission-remote-plus/commit/5ada881064e8b939a2cc468dee31cf82d0c0ffb2

When a download is finished I would suggest to hide it from the dropdown menu. Presently it shows with green color, the same as seeding. I would like to keep the history around in Transmission, but I don't want it to show in the 'Remote Transmission ++' dropdown menu.

Pull request #20 refers.

Test page http://plnkr.co/edit/aBASZc55tSPWm0mZUPvK?p=preview

Partially fixed in 49a6239

Reference https://developer.chrome.com/extensions/storage

Blocks #21

I have transmission-daemon which is listening on localhost. In order to access it i have this configuration in nginx:

location /transmission {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass http://127.0.0.1:9091/transmission;
proxy_pass_request_body on;
proxy_pass_request_headers on;
proxy_pass_header X-Transmission-Session-Id;
}

Nginx is also configured for http2. In this case Remote Transmission++ is unable to connect to transmission. Problem is that extension expects in fail function errorThrown==='Conflict' but with http2 this string is empty. I made a small patch in order to resolve this:

--- background.js.orig  2018-01-25 04:42:59.000000000 +0200
+++ background.js       2023-09-01 15:16:16.963952091 +0300
@@ -62,7 +62,7 @@
     }
   })
   .fail(function (jqXHR, textStatus, errorThrown) {
-    if (errorThrown === 'Conflict') {
+    if (errorThrown === 'Conflict'|| jqXHR.status==409) {
       // X-Transmission-Session-Id should only be included if we didn't include it when we sent our request
       let xSid = jqXHR.getResponseHeader('X-Transmission-Session-Id');
       localStorage.sessionId = xSid;
  

And now everything is fine. This patch should also preserve the original behavior with HTTP1.1
If you find this useful please include it in the next release.

File name in torrent was not displayed.

When add torrent using transmission-remote-plus, I can't see full file name in 'Save Torrent' dialog.
(But, after add torrent, I could saw full file name.)

I think.... This problem is cause my Windows 10 (Korean) use default encoding MS949.

(Example Torrent Link : https://torrentkim12.com/bbs/download.php?bo_table=torrent_tv&wr_id=135233&no=0 )

Could you add a badge to the toolbar icon that shows how many active torrents?

Using the extension with Chrome, its awesome by the way.
However something happened and nothing comes up when I click a torrent link.
Reinstalling the extension has not helped.
Fully reinstalling and wiping all Chrome data fixed it. However a few days later it broke again.

Anyone have any suggestions?

I'm using several Transmission daemons and would like to use all of them using this extension.
Any chance to add support for that?

If Chrome is closed and reopened, the options.html?newvar=true page is loaded with default vaults.

Done in 9db570a. Needs testing.

Tabs must be refreshed before extension will register clicks on magnet/torrent links after an upgrade or first installation.

When I try to use custom directories it just says there was an error adding the torrent. No other information. Is there something special I have to do to get custom directories to work?

Hello, since updating Transmission to version 2.92 when I attempt to add a torrent, I receive "download directory path is not absolute" error message. I can still see torrents in Transmission, it just seems to be the adding functionality that is broken.
Thanks.

The link sent to transmission may be relative and the base domain may be not sent.

In inject.js:40, instead of: var url = $(this).attr("href");

it is preferable to get the absolute url
var url = this.href;
see: http://stackoverflow.com/questions/2639070/get-the-full-uri-from-the-href-property-of-a-link

OSX 10.12.06
Chrome 63
https://thepiratebay.org/

Click on magnet link doesn't work.
Right click -> "Download with Remote Transmission" works.

When the download list is empty, the dropdown menu for settings (gear-symbol) is not shown right. It disappears because the popup window is too small. Not a big problem, but it is sometimes convenient to go to the fullscreen app from that menu...

Whenever I refer to my server ip directly (http://ip:someport/transmission), and save the settings, the extension works. If I open the options window again, everything shows up as I left it. However, if I refer to my nginx reverse proxy (https://someaddress:443/transmission) everything works, but the options screen is completely blank. The save button also stops reacting. Nevertheless, if Iwrite the direct ip again, everything works. Is this a chrome issue or an extension issue?

Thanks!

(this is mostly to warn other people attempting to not waste time on this)

As Fetch is usually referred to as the successor to XMLHttpRequest, I attempted to convert the rpcTransmission function to use that instead.

Unfortunately, this doesn't seem to be possible. When using the fetch API, it is impossible to see the X-Transmission-Session-Id header which the server is returned. See "Reading response headers with Fetch API" on StackOverflow for more information.

This does work (basically it's done now inside jQuery):

var xhr = new XMLHttpRequest();
xhr.open('POST', localStorage.server + localStorage.rpcPath, true);
xhr.addEventListener('load', function () {
    console.log('xhr: ' + xhr.getResponseHeader('X-Transmission-Session-Id'));
});
xhr.send();

This does not work:

fetch(localStorage.server + localStorage.rpcPath, {method: 'POST'})
.then(function (response) {
    console.log('fetch: ' + response.headers.get('X-Transmission-Session-Id'));
});

This is not really an issue, as we can just continue to use XmlHttpRequest. Just a note.

Thank you for this extension, it's really useful!

I've been noticing that notifications for completed torrents on my Mac sporadically appear for torrents which have already completed. I haven't tried to properly diagnose the issue, but I suspect the notifications might pop up when a torrent stops uploading as well as downloading. Could this be the problem?

When connecting directly to remote transmission with url kind of http://192.168.1.5:9091/ it works fine. But when adding a proxy the extension cannot connect to url http://torrent.my-domain.com/ . I discovered that might be missconfiguration of basic auth of my proxy. After I changed the url to this http://username:[email protected] it started to work.

upstream transmission  {
      server localhost:9091; #Transmission
}
server {
    if ($host = torrent.my-domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot
  listen 80;
  server_name   torrent. my-domain.com
  # enforce https
  return 301 https://$server_name$request_uri;
  server_tokens off;
    # Redirect non-https traffic to https
    # if ($scheme != "https") {
    #     return 301 https://$host$request_uri;
    # } # managed by Certbot
}
server {
      listen 443;
      ssl    on;
    ssl_certificate  ################
    ssl_certificate_key ################
server_tokens off;
      server_name torrent.my-domain.com
      location / {
          return 301 http://$server_name/transmission/;
      }
      location ^~ /transmission {
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          proxy_set_header Host $http_host;
          proxy_set_header X-NginX-Proxy true;
          proxy_http_version 1.1;
          proxy_set_header Connection "";
          proxy_pass_header X-Transmission-Session-Id;
          auth_basic "Restricted Content";
          auth_basic_user_file /etc/nginx/.htpasswd;

          location /transmission/rpc {
              proxy_pass http://transmission;
          }
          location /transmission/web/ {
              proxy_pass http://transmission;
          }
          location /transmission/upload {
              proxy_pass http://transmission;
          }
          location /transmission/web/style/ {
              alias /usr/share/transmission/web/style/;
          }
          location /transmission/web/javascript/ {
              alias /usr/share/transmission/web/javascript/;
          }
          location /transmission/web/images/ {
              alias /usr/share/transmission/web/images/;
          }
          location /transmission/ {
              return 301 http://$server_name/transmission/web;
          }
      }
}

ever since the previous update all i get (on muliple devices) is the header at the top with the logo and the torrent numbers, but below where you see the torrents listed i just have a blank white space.

i am running 0.9.9.8 on two systems (one mac one windows) and experience the same on both.
problem wasn't there before either 0.9.9.7 or 0.9.9.8.

With enabled "Show download popup" on Save click there is no any action

With disabled "Show download popup" i got erron on screenshot -

After commit 2192d13, the torrent popup is empty after clicking the extension icon.

The top interface elements are shown (Icon, number of torrents, DL/UL rate), but the list of torrents is missing.

As the title says it, no notifications for finished torrents are sent in spite of enabling the feature in the settings.

Notifications for added torrents work, though.

Help wanted as I am not actively using the extension at this time.

Images should be 1,280x800 or 640x400 to comply with Chrome webstore requirements.

Images should show the list of torrents in various states and stages of completion. All torrents must be legally obtained, i.e. no TV shows / movies / games. Recommend Linux distributions and such.