There are sometimes things that can go wrong when updating bliss. Here's a description of each one with what to do if it happens, plus a catch-all solution.
This normally happens when the update worked but the parts of bliss that were updated could not be restarted. The reasons for this may be many but they tend to boil down to: I goofed up. Send me an email to point this out, if you like.
The easiest solution is to restart bliss. If that doesn't work, see the 'catch-all workaround'.
Again, this normally happens when some internal parts of bliss couldn't be restarted after updating.
First, try restarting. If that doesn't work, see the 'catch-all workaround'.
Here's what to do if an update appears to have FUBARed bliss.
First, just try restarting bliss. Restarting bliss clears out the internal cached wiring between different bliss modules and can sometimes fix problems.
The next thing to do is remove a folder called
felix-cache. This contains the update and the latest version of bliss.
But before you do that... stop bliss! If bliss is still running,
felix-cache may be updated after you delete, causing further problems.
Once bliss is stopped, you can find
felix-cache in the following location:
|Windows XP||C:\Documents and Settings\[username]\.bliss|
|Windows Vista, 7, 8 and 10||C:\Users\[username]\.bliss|
|Mac OS X (see below)||/Users/[username]/Library/Application Support/bliss|
Once you find
felix-cache delete it and its children.
felix-cache is removed bliss will regress to the very first version of bliss that you installed. You can then continue to use this version, or uninstall completely and re-install from scratch with the latest installer from blisshq.com.
I hope this covers most eventualities of updating bliss. If you have further problems, let me know via email or in the comments section below.blog comments powered by Disqus