Hi
First off, there are issues with the website not showing updates to 2.46. That was my oversight and is being followed up with a patch.
Secondly, updating 2.40 to 2.46 is not working (as like 2.39-> 2.40). That is currently being worked on.:ewong
-
Recent Posts
Recent Comments
- Kami on Checksums were fixed… but… where are the binaries?
- Ricardo Palomares on Checksums were fixed… but… where are the binaries?
- Ant on Checksums were fixed… but… where are the binaries?
- ElTxolo on LTNS…
- Ant on Checksums ‘fixed’.
Archives
- July 2019
- February 2019
- January 2019
- December 2018
- September 2018
- July 2018
- May 2018
- April 2018
- February 2018
- November 2017
- October 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- December 2016
- October 2016
- September 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- April 2015
- August 2014
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- October 2011
- September 2011
- August 2011
- June 2011
- April 2011
- March 2011
- February 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- July 2009
- June 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- April 2006
- February 2006
- January 2006
- December 2005
- November 2005
- September 2005
Categories
Meta
Tried to download 2.46 just now:
http://i.imgur.com/yQFqsf5.png
I’m using SM 2.40
@Hales: Without information on which webpage you clicked which link with the shown result we can’t do anything.
Do you use noscript?
Hey Rainer,
Apologies. I get the cert error when I click the main links in the green ‘Download Now’ box on http://www.seamonkey-project.org/ or any of the official build download links on http://www.seamonkey-project.org/releases/ .
It does look like NoScript is related. Enabled scripts on seamonkey-project.org does not help, but disabling noscript or starting a new profile in seamonkey (without noscript installed) does prevent the message coming up.
Perhaps noscript is replacing some cdn-related script with something of its own? I’m not familiar with cdn integration, other than it can be fiddly/difficult.
This is a known issue that I’m working on. Unfortunately, I couldn’t get it fixed in time for 2.46’s release. I’m hoping by the next release it should be fixed.
Thanks Ewong. Good to know that it’s not something horrible happening.
It was an update of looking forward to, but unfortunately 2.46 can’t be made a current browser.
When it’s localized even if it’s no problem in English, don’t be better for it to be indicated. But only the fatal fault that I make a specific game (It’s PSO2 of SEGA company.) end can’t be approved. It was reported to SEGA, but it doesn’t seem to correspond. The game in which watch software like nProtect isn’t included is no problem.
Unless this is settled, I can’t shift from 2.40.