Forum: Typo [ANN] Typo 5.0.3

Hello,

Typo 5.0.3 "Don Mc Cullin" released on February 2008 the 24th is
mostly a bugfix and refactoring release, going along with some
improvements, everything leading slowly but surely to 5.1.

*** Less bugs, more speed ***

Typo has never been so fast and so bugless as well. We've rewriten
most of the caching engine, and it's now running flawlessly. Our
effort to speed up the code has also been pursued and we can be proud
of what we're releasing.

*** Brand new editor ***

The blog editor has been rewriten too, to be more functionnal and user
friendly. We've also switched the rich text editor from TinyMCE to
FCKEditor for 4 important features :
– Fullscreen edition (kicks ass baby)
– Spellchecking
– Safari compatibility
– Impressive localization

*** More localisation ***

We're continuing the localization effort to port Typo in your
language. Default themes has been localized, and we now provide up to
8 languages :
– English (default)
– French
– German
– Italian
– Japanese
– Mexican Spanish
– Polish
– Romanian

Many thanks to all the translators. Currently, only French translation
is really complete.

*** No gem? ***

We won't provide you the habitual gem we used to. Rails app installer
– formerly known as Typo installer – is brocken with Rails 2.0.2 and
Typo instances installed this way just don't work.

We hope you'll enjoy Typo 5.0.3 as much as we enjoyed bringing it to
you.

Cheers,
Frédéric de Villamil / neuro`

On Sun, Feb 24, 2008 at 9:56 AM, Frederic de Villamil
<frederic@de-villamil.com> wrote:
>  *** No gem? ***
>
>  We won't provide you the habitual gem we used to. Rails app installer
>  – formerly known as Typo installer – is brocken with Rails 2.0.2 and
>  Typo instances installed this way just don't work.

I'm sorry for the stupid question, but how are you distributing Typo
now if not by gem? Tarball? Source repository tag? Rsync? Native
installer(s)?

--
Cheers,

Kevin Williams
http://bantamtech.com/
http://almostserio.us/
http://kevwil.com/

Tarball seems to be the weapon of choice:
http://www.typosphere.org/pages/download

Le 24 févr. 08 à 18:23, Codeblogger a écrit :

> Tarball seems to be the weapon of choice:
> http://www.typosphere.org/pages/download

Oh, sorry, I thought I had put the URL in th mail but it was only on
the release post at 
http://blog.typosphere.org/articles/2008/02/24/typ...

Btw Kevin, I'm looking forward seeing your perfs using the now
repaired cache.
Frédéric

Yes, I'm looking forward to testing it.

Thanks for the clarification on the download. :)

On Sun, Feb 24, 2008 at 11:08 AM, Frederic de Villamil
<frederic@de-villamil.com> wrote:
>
> Btw Kevin, I'm looking forward seeing your perfs using the now repaired
> cache.
> Frédéric
> _______________________________________________
>  Typo-list mailing list
>  Typo-list@rubyforge.org
>  http://rubyforge.org/mailman/listinfo/typo-list
>



--
Cheers,

Kevin Williams
http://bantamtech.com/
http://almostserio.us/
http://kevwil.com/

Here's my status report.

With both the action_controller.fragment_cache_store set to
:mem_cache_store and CachedModel.use_memcache = true, I get 500 errors
at times, especially when using the admin console. If I grep for
/Error/ in my logs there are a number of different ones, so I'm not
sure what the error is.

Before upgrading today, I had
config.action_controller.fragment_cache_store commented out and
CachedModel.use_memcache set to false. Right now I'm running with the
fragment_cache_store set to the original :file_store.

I think most of my caching problems stem from my numerous attempts to
use memcache as the cache.

One final thing. In /admin/resources/list, the sub-nav menu doesn't
seem to have the new 'Manage foo' names.

On Sun, Feb 24, 2008 at 11:30 AM, Kevin Williams <kevwil@gmail.com> 
wrote:
>
>  > cache.
>
>
> --
>  Cheers,
>
>  Kevin Williams
>  http://bantamtech.com/
>  http://almostserio.us/
>  http://kevwil.com/
>



--
Cheers,

Kevin Williams
http://bantamtech.com/
http://almostserio.us/
http://kevwil.com/

On Mon, Feb 25, 2008 at 4:25 AM, Kevin Williams <kevwil@gmail.com> 
wrote:
>  CachedModel.use_memcache set to false. Right now I'm running with the
>  fragment_cache_store set to the original :file_store.
>
>  I think most of my caching problems stem from my numerous attempts to
>  use memcache as the cache.
>
>  One final thing. In /admin/resources/list, the sub-nav menu doesn't
>  seem to have the new 'Manage foo' names.

Ah, memcache support hasn't been a priority with us because we're
expecting to see Typo deployed in places where there is no memcache
available (my blog's currently running on a site that doesn't even let
me run mongrel or thin, it's fcgi all the way). Our recent cache
fixing spree has been focussed on getting page caching and sweeping
working correctly because the more pages that get served without
touching typo, the better. Looking at your blog's sidebar, you should
be able to switch to page caching with impunity.