Composer 3 Beta keeps expiring - How do I get it back?
Hi Fletcher,
I've had this issue with v3 expiring and having to download the latest version. Now v3.0b33 has expired and I cannot use it or update it. I realize v3 isn't official but I've become accustomed to working with it and much prefer the integrated Info at the bottom of the page to the floating panels of v2.
Is there any way to get my beta working again? Also, when will v3 be available for upgrade?
Thanks in advance,
Dylan
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on 16 Jun, 2015 12:09 PM
v3 betas are just that -- betas. They are not finished, have bugs
(hopefully just small ones, but bugs nonetheless), and are released to
help get more eyeballs looking for those bugs.
Unfortunately, a lot of people download a beta, and just keep using that
same version, rather than updating once in a while to the latest beta.
So I end up getting bug reports on a bug that was fixed days, weeks, or
even months previously. Or even worse, someone loses data because of a
bug that had actually been fixed weeks ago but they had not updated yet.
So I do a few things to help ensure everyone can keep up to date:
1. The beta has the ability to use Sparkle to update whenever a new
release comes up. Not everyone turns this feature on, unfortunately.
The last beta improves this feature, so it *should* still be able to
update, even if it has expired. We'll find out in 35 days, I suppose....
2. For major updates, or if I miss a beta expiration deadline, I send an
email to the MMD Software mailing list which includes direct download
links to the latest version. You can signup to be sure to get the
latest announcement (I try to do this infrequently -- 5 emails in the
last 6 months):
http://multimarkdown.com/signup
3. As a last resort, the betas expire (previously 28 days, now 35 days).
I don't want the betas floating out there forever, and I want to
ensure that users are reminded if they have an old version. If you use
the app at once a month, and have the auto-updating feature enabled, you
should stay up to date. *EXCEPT* that I have been really busy at my day
job the last few months, and I missed the 28 day deadline a couple of
times. So in those cases, I had to send out an email to the mailing list.
4. I don't know when v3 will be finalized. Software deadlines are
notoriously unreliable, so I don't make predictions. Which is good,
because I've already missed my prediction. ;)
Hopefully this explains things and answers your questions. Sign up for
the mailing list to be sure to get important information, and the
download links to the latest version are here:
http://files.fletcherpenney.net.s3.amazonaws.com/MultiMarkdown%20Composer%20%28Non-Sandboxed%29-3.0b34.zip
http://files.fletcherpenney.net.s3.amazonaws.com/MultiMarkdown%20Composer%20Pro%20%28Beta%29-3.0b34.zip
Thanks!!
Fletcher
2 Posted by mmcomposer on 16 Jun, 2015 04:50 PM
Very clearly explained Fletcher. Thank you.
I thought I was on the mailing list but it seems not.
I am now.
Still loving Composer. Thanks for all your work on it.
Fletcher closed this discussion on 21 Aug, 2015 09:13 PM.