CloudServices/Sync/FxSync/Archived/Weave FAQ: Difference between revisions
< CloudServices | Sync | FxSync | Archived
Jump to navigation
Jump to search
No edit summary |
|||
| Line 64: | Line 64: | ||
:;extensions.weave.syncOnQuit.enabled | :;extensions.weave.syncOnQuit.enabled | ||
::This controls whether or not Weave will sync when Firefox is closed. Values are true (default) and false. Note, however, that Weave does not have the ability to stop an ongoing sync. If a scheduled sync is in progress when Firefox is shut down it will abort, probably leaving a stale lock on the server, and possibly also leaving the server in an inconsistent state (which could require a wipe). Sync on quit avoids that problem because it waits until the sync is finished until exiting. If you turn it off, Firefox will just quit right away. Therefore, if you disable sync on quit, you should probably set extensions.weave.schedule to 0 (manual). | ::This controls whether or not Weave will sync when Firefox is closed. Values are true (default) and false. Note, however, that Weave does not have the ability to stop an ongoing sync. If a scheduled sync is in progress when Firefox is shut down it will abort, probably leaving a stale lock on the server, and possibly also leaving the server in an inconsistent state (which could require a wipe). Sync on quit avoids that problem because it waits until the sync is finished until exiting. If you turn it off, Firefox will just quit right away. Therefore, if you disable sync on quit, you should probably set extensions.weave.schedule to 0 (manual). | ||
== Running your own server == | |||
:;Can i run my own Weave server? | |||
::Check out [http://remcobressers.nl/archives/3 this documentation] about running your own server based on Apache and mod_dav | |||
Revision as of 21:50, 11 July 2008
Back to Labs/Weave.
Weave FAQ
Please feel empowered to edit or add content this FAQ if you find information or details that would be helpful to the wider community.
General
- Where else can I get help if I'm having a problem?
- Check out the Weave discussion forum on the Mozilla Labs site.
- Is the source code available?
- As with all Mozilla projects, Weave is open source. For more information on the source code, please see this forum post.
0.2 Milestone
- How often does Weave connect to the server?
- After the initial data transfer is completed during initial setup, Weave connects to the server periodically when it accumulates enough changes that need syncing or when enough time has passed since the last sync (at least once every 20 minutes if any data has changed). Weave also syncs when you start Firefox, when you quit it, and when you click on the "Sync Now" button in the Weave menu or the preferences.
- Why doesn't my account work anymore?
- Due to server changes, you will need to re-register with Weave. You can do this after installing the new add-on via the Setup Wizard.
- I use the NoScript add-on and the Weave Setup Wizard isn't working. Why not?
- The Weave Setup Wizard is currently reported to conflict with at least the NoScript, Adblock, and Torbutton add-ons. They prevent the "captcha" verification from appearing. Please disable them before attempting to install Weave. Restarting Firefox in safe mode to set up your account should also work.
- It is possible to add an exception filter to Adblock, so it would allow the "captch" verification to appear.
- I have tested the following filters on Adblock plus 0.7.5.5:
- @@|*weave*
- @@|https://services.mozilla.com/
- Note: the @@| at the beginning of the filter means it is an exception filter. I have not tested which of this filters actually solved the problem, but I was able to create the account and use weave.
- How do I make Weave work in Ubuntu 8.04 Hardy Heron?
- 1. Uninstall Weave from Firefox. Close Firefox.
- 2. Install updated and fixed versions of libnss and libnspr:
- These versions are also available in the "hardy-proposed" repository and will soon be in "hardy-updates" as well.
- 3. (64-bit only) If you are using 64-bit Ubuntu (amd64), you need to build Weave yourself, because the official build is 32-bit-only for now. It's easy, just follow the instructions on this page: http://wiki.mozilla.org/Labs/Weave/Building
- 4. Install Weave in Firefox.
- Weave is not working on my Mac, what should I do?
- The official Weave 0.20 add-on release currently works only on Intel-based Macs. If you are not sure what type of Mac you have, you can determine which platform you are running by clicking the Apple menu at the top left of your screen and selecting "About this Mac". If the information to the right of "Processor" does not include "Intel", the cryptography library that the official Weave build uses will not work, and you will get "invalid passphrase" errors when you try to set up your account. Don't despair! You can still use Weave 0.22:
- For now, uninstall the add-on, and you can either use the community-provided PowerPC Weave 0.22 build (unofficial, but recommended) or build your own using the instructions to compile Weave 0.20 (written for a previous version, but will work for the more adventuresome).
Configuration Parameters
- extensions.weave.schedule
- This controls whether or not Weave synchronizes on a schedule. Values are 1 (the default, sync on a schedule; internally set to every 30 seconds), or 0 (sync manually).
- extensions.weave.syncOnQuit.enabled
- This controls whether or not Weave will sync when Firefox is closed. Values are true (default) and false. Note, however, that Weave does not have the ability to stop an ongoing sync. If a scheduled sync is in progress when Firefox is shut down it will abort, probably leaving a stale lock on the server, and possibly also leaving the server in an inconsistent state (which could require a wipe). Sync on quit avoids that problem because it waits until the sync is finished until exiting. If you turn it off, Firefox will just quit right away. Therefore, if you disable sync on quit, you should probably set extensions.weave.schedule to 0 (manual).
Running your own server
- Can i run my own Weave server?
- Check out this documentation about running your own server based on Apache and mod_dav