If you reached this page, Piggy Bank didn't work for you.
We apologize for the inconvenience but we hope to collect on this page information that might help you solve the problem you have encountered.
If you are the unlucky discoverer of a problem that is not listed above, there are a few ways that you can help us help you:
- Check for existing issues with Piggy Bank on our issue tracking system and if you are the unlucky discoverer of a new issue, please sign up (yes, we are sorry for this, but this helps us avoid spam!) and submit a new issue, we will be following it and you'll be copied via email.
- Subscribe to the SIMILE general mailing list and tell us what the problem is, the developers or other users might help you resolve your problem.
In both cases, make sure to indicate what platform(s) you experienced the problem on (Operating System, Firefox version, Piggy Bank version, Java version), what you were doing, and what error message you received. The more detailed your explanation of the problem, the more likely that the developers will understand what is going on and will be able to help you. A little time spent writing the help request can save you a lot of time in waiting for an answer.
Turning Debug On
If you can't simply wait for help and you want to help yourself, we can help you help yourself (and us and others too if you submit us your findings later!).
Piggy Bank doesn't normally output a lot of information during its operation, this is to increase speed and reduce noise, but it is very useful to turn the debug mode on to understand what's going on (and where is the code that is performing a particular operation, which makes debugging and understanding the code a lot easier).
In order to do this, open "Tools" > "Piggy Bank" > "Options", then go to the "Development" tab and check the "debug" flag. This turns Piggy Bank (and firefox too!) into debug mode. Also select the parts that you want to know more information about. If you are not sure, check them all.
Note: Piggy Bank in debug mode is considerably slower than in the normal mode. So, you might want to turn it off during normal operation.
Turning the debug mode on make Piggy Bank be very verbose about what it's doing. Piggy Bank's tracing output is located in different places:
- firefox's standard output
- Java Plugin's console
Both the java console and firefox standard output are normally hidden, so you need to look for them. Unfortunately, they are found/accessed in different ways depending on your operating system, so follow the section below that matches your operating system.
On windows, you have to start Firefox from the command line with the -console parameter.
C:\Program Files\Mozilla Firefox\firefox.exe -P development -console
The Java part is logged into the Java Console. You can access it by right-clicking on the Java icon that appears on the tray bar after you have started Firefox.
If you don't like to use the DOS prompt, an alternative way to start firefox is to "right-click" on the firefox shortcut that starts it (for example, the one in the task bar), then select Properties and change the Target text box to
"C:\Program Files\Mozilla Firefox\firefox.exe" -P development -console
Now you can run firefox in debug mode just by clicking on the icon as before (this is also a good way of having multiple shortcuts for different profiles, which is very handy when you want to do development with one browser and still use another one to navigate)
On MacOSX, you have to start Firefox from the command line as well, but there is no need for a console parameter:
/Applications/Firefox.app/Contents/MacOS/firefox-bin -P development
The java logs are dumped onto a file. The best option is to type
open ~/Library/Logs/'Java Console.log'
which will execute the Console program over the log.
On Linux, you have to start Firefox from the command line as well, but just like MacOXS, there is no need for a console parameter. In most Linux distributions firefox is in your path so you can just type:
firefox -P development
(assuming that your $JAVA_HOME/bin is your PATH), then select the Advanced tab, expand the Java console tree item and select Show console in the radio menu. Then click Ok and restart firefox. The Java Console will open as soon as the java subsystem is invoked from your browser.
If you are upgrading to Piggy Bank 3.1.0 from a 3.0.x version and you've run into an unrecoverable problem, you can downgrade to your previous version until we can figure out a solution. You'll have to ignore Firefox's requests to upgrade Piggy Bank whenever you start your browser.
First, quit Firefox. To downgrade, locate your profile folder and find the folder(s) named one of
piggy-bank.pre-3.1.0. If only the
piggy-bank folder exists, skip the rest of this paragraph. If both exist, delete the
piggy-bank folder and rename
piggy-bank. It should be a full database of your Piggy Bank data consistent with the prior version.
Now start Firefox and uninstall Piggy Bank, ignoring any errors. Look in the distribution archives for the version corresponding to your previous version (probably the latest, 3.0.2) and install it. Aside from Firefox's notifications about a new version, which you should ignore for now, Piggy Bank should be back up and running.
If your tags have gone missing, either from an upgrade or a downgrade, simply restart Firefox. For some reason, the tag support needs to be rebuilt from a fresh Piggy Bank start. We'll see if we can fix this in future versions.
One user reported on our mailing list that Piggy Bank and Solvent will not work while the McAfee SiteAdvisor add-on is enabled in the same Firefox profile. We are unfamiliar with the root cause of the incompatibility at this time. Thanks to Bob Morris for taking the time to uncover the issue.