This is really bad. I had hoped to release Wary 5.1.3 with SM 2.2, however, I am going to stay with 1.1.18 as in Wary 5.1.2.
Hopefully I will be able to upgrade SM for Wary 5.2.
Comments:Posted on 12 Aug 2011, 20:53 by FeodorF
Composer Broken ?
O.k. try this:
Before you try the right-click for "Image properties" save your Composer page first.
After you have saved your Composer page you will be able to do the right-click for your "Image properties".
B W, FeodorF
Posted on 12 Aug 2011, 22:16 by gjuhasz
This bug has been fixed in Seamonkey 2.3 beta
Posted on 13 Aug 2011, 7:34 by BarryK
The bug I get is when open an existing web page, it is already saved.
Posted on 14 Aug 2011, 6:05 by GCMartin
I understand that you have reverted SM in WARY release. But, would it had been prudent to leave 2
2 with the understand that auto-update will take care of SM?
Appears that SM 1.x does NOT have update ability to latest SMs so newbie WARY users will not have an auto system path to latest SM until the next WARY comes along.
Just a thought. if helpful, use it.
Posted on 23 Aug 2011, 18:40 by abushcrafter
SM Composer Is Rubbish
It produces rubbish, large, full of junk code. Don't borther with it! Amaya is fantastic! Put you efforts in to Amaya!
Posted on 25 Aug 2011, 16:48 by Dewbie
YouTube unsupports SM 1.1.18
I can't believe this; it's only what...two years old?
Posted on 31 Aug 2011, 20:42 by Dewbie
...and Bruce B has a workaround for this :
Posted on 6 Sep 2011, 18:07 by BarryK
Compiling it right now. I hope it fixes the Composer bug, but I can't see anything in the changelog that specifically mentions the bug that I have experienced.