Difference between revisions of "Broken/Autoconnect"
m (Category additons.) |
(autoConnect=true broken atm) |
||
Line 3: | Line 3: | ||
==autoConnect (for the widget on a per channel basis)== | ==autoConnect (for the widget on a per channel basis)== | ||
*Modify the [[Uri parameters]] for your widget: | *Modify the [[Uri parameters]] for your widget: | ||
− | **Add '''&autoConnect=true''' | + | **Add '''&autoConnect=true''' |
+ | |||
+ | '''Note:''' this setting seems to make the connection to the server fail in some cases atm (endless spinning), we are working on a fix. | ||
+ | |||
+ | |||
**Add '''&delay=30''' for heavily visited pages (default is 2) | **Add '''&delay=30''' for heavily visited pages (default is 2) | ||
**Remove all &xxx'''Prompt'''=true parameters (they override autoConnect) | **Remove all &xxx'''Prompt'''=true parameters (they override autoConnect) |
Revision as of 12:39, 24 April 2010
autoConnect (for the widget on a per channel basis)
- Modify the Uri parameters for your widget:
- Add &autoConnect=true
Note: this setting seems to make the connection to the server fail in some cases atm (endless spinning), we are working on a fix.
- Add &delay=30 for heavily visited pages (default is 2)
- Remove all &xxxPrompt=true parameters (they override autoConnect)
- You must have &settings=<yourManagerID>
- Switching autoconnect:
- Join #yourChannel using the mibbit client
- Make yourself op (or higher).
- Use the command "/autoconnect on (or off)" (only needed once, the setting is stored in a db, if you use the full client it will take effect after ten minutes)
Auto-connect for the main client is done in the "Channels" tab, see: Autoidentify