Home › Forums › Bugs

"cycle through modes" issue

Sun, 11/15/2009 - 02:58 — Prodigy

Hello,
 
The "cycle through modes" option once set to a mouse button will not cycle anymore between the different proxies set when it finishes a full cycle and reaches "Use proxies based on their pre-defined patterns and priorities". Furthermore if set on "Use proxies based on their pre-defined patterns and priorities" it will not cycle through the other proxies at all. The issue is noticed with both FoxyProxy status bar and Toolbar icon.
 
Foxy Proxy Standard 2.15
FireFox version 3.5.5

‹ 2.17 DNS leakage FP v2.18 seems to ignore blacklisting ›
Sun, 11/15/2009 - 20:35 — ericjung

Hi, I'm not able to

Hi,

I'm not able to duplicate this. How many proxies do you have defined? Which mode are starting from? Can you send me your foxyproxy.xml?

Eric

Mon, 11/16/2009 - 07:01 — thewer

Problem Confirmed

I have run into the same problem - version 2.15 and ff 3.5.5 on Windows 7 32 bit.

I have 7 proxies and a default set - only some of the proxies have patterns to trigger their use, the rest I left-click to cycle thru them (hence why I found the bug). 5 SOCKS ones (mix and 4 4a and 5), 2 HTTP, and default is direct connection.

I start from the "Patterns" mode, and as of the update this morning left clicking on petterns mode (status bar tested) nothing happens. If I right click and choose one, then left clicking to cycle works until it gets stuck on patterns again.

In the error console I get this error:
Error: this.proxies is undefined
Source File: file: <triple_slash> C:/Users/John/AppData/Roaming/Mozilla/Firefox/Profiles/yi4pmdrs.default/extensions/foxyproxy@eric.h.jung/components/foxyproxy.js
Line: 318

That line is the first in this function:
function _getNextAfterPatterns() {
  var p = this.proxies.item(0);
  (!p || !p.enabled || !p.includeInCycle) && (p = _getNextInCycle(this.proxies.item(0).id));
  return p?p.id:"disabled";     
}

thewer

Mon, 11/16/2009 - 14:49 — ericjung

Thanks for the detailed

Thanks for the detailed reply. I've now duplicated the problem and am working on a fix.

Eric

Mon, 11/16/2009 - 15:00 — ericjung

Hi, I've fixed the bug and

Hi,

I've fixed the bug and it will be in the next release.

Thanks for reporting it!

Eric

Wed, 12/02/2009 - 04:14 — ericjung

Fixed in FoxyProxy Standard

Fixed in FoxyProxy Standard version 2.16 and FoxyProxy Basic 1.3.

Wed, 12/02/2009 - 22:56 — thewer

Thanks! 1.6.1 works

Thanks! 1.6.1 works great!

thewer

Thu, 12/03/2009 - 16:07 — ericjung

I think you mean 2.16.1.

I think you mean 2.16.1. You're welcome !

Eric

Sat, 01/23/2010 - 08:39 — urmel

Problem is still alive...

Using FoxyProxy Standard 2.18 (the current one) on iceweasel (aka debian firefox) 3.0.6 I still have exact the same behaviour as described here (means, the problem stayed even after the update).

Error message is:
this.proxies is undefinded in line 297 of foxyproxy.js

function _getNextAfterPatterns() {
var p = gFP.proxies.item(0);
-> (!p || !p.enabled || !p.includeInCycle) && (p = _getNextInCycle(this.proxies.item(0).id));
return p?p.id:"disabled";
}

Seems to be a different trigger... Do you need further information?

Thanks
Stefan