Difference between revisions of "Broken/Autoconnect"
(autoConnect=true broken atm) |
(→autoConnect (for the widget on a per channel basis): especcially when using a chrome browser) |
||
| Line 5: | Line 5: | ||
**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. | + | '''Note:''' this setting seems to make the connection to the server fail in some cases atm (endless spinning, especcially when using a chrome browser), we are working on a fix. |
Revision as of 18:52, 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, especcially when using a chrome browser), 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
