From dmitry.sustretov at gmail.com  Tue Dec 11 19:03:35 2007
From: dmitry.sustretov at gmail.com (Dmitry Sustretov)
Date: Wed, 12 Dec 2007 01:03:35 +0100
Subject: [typo] typo 4.1.1 admin interface issue
Message-ID: <85a11e30712111603i61587914r33b828353a234bc1@mail.gmail.com>

Hello,

try to post a trackback to one of your posts and then the feedback
page in the admin interface
(http://new.shenme.de/blog/admin/feedback). Clicking on an icon "Show
contents" or "Edit contents" to the right of a trackback will lead to
an "ActiveRecord::RecordNotFound (Couldn't find Comment with ID=?? AND
(feedback.article_id = ??))" exception (according to logs), in other
words typo tries to search for a comment with an id of the trackback,
and fails.

I did not find any mentioning of this bug on the list, so I thought I
should report it.

-- 
Dmitry Sustretov
------------------------------------------------------------
-- PhD student at INRIA Lorraine-LORIA
-- http://www.loria.fr/~sustreto/
------------------------------------------------------------

From orangej2 at gmail.com  Thu Dec 13 11:06:08 2007
From: orangej2 at gmail.com (John Gedeon)
Date: Thu, 13 Dec 2007 08:06:08 -0800
Subject: [typo] Help Rails 2.0 with typo 4.1.1
Message-ID: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>

I have typo 4.1.1 installed on my host that just upgraded to rails 2.0.1.
They still have rails 1.2.6 installed but typo is using 2.0.1 and is broken
with a huge stack trace that I didn't have before, and I have made no
changes myself so it must be that. I know I should have frozen the gem
before, but now I do not know how to switch it so that typo uses the old
rails plugin. I tried adding RAILS_GEM_VERSION = '1.2.6' in my
environment.rb file but that doesn't help.

Please let me know if there is any other useful info I can send. Mostly I
think I just need to know how to freeze rails to a previous version of the
plugin which is installed in /usr/lib/ruby/gems along side the latest.

Also I can't use rake rails:freeze:edge TAG=rel_1-2-6 because my host
doesn't have svn installed.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071213/799e703b/attachment.html 

From cyril.mougel at gmail.com  Thu Dec 13 11:11:23 2007
From: cyril.mougel at gmail.com (Cyril Mougel)
Date: Thu, 13 Dec 2007 17:11:23 +0100
Subject: [typo] Help Rails 2.0 with typo 4.1.1
In-Reply-To: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>
References: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>
Message-ID: <ac23b0bb0712130811v10044860o1cdf2cf4dcaf34b0@mail.gmail.com>

On Dec 13, 2007 5:06 PM, John Gedeon <orangej2 at gmail.com> wrote:
> I have typo 4.1.1 installed on my host that just upgraded to rails 2.0.1.
> They still have rails 1.2.6 installed but typo is using 2.0.1 and is broken
> with a huge stack trace that I didn't have before, and I have made no
> changes myself so it must be that. I know I should have frozen the gem
> before, but now I do not know how to switch it so that typo uses the old
> rails plugin. I tried adding RAILS_GEM_VERSION = ' 1.2.6' in my
> environment.rb file but that doesn't help.
>
> Please let me know if there is any other useful info I can send. Mostly I
> think I just need to know how to freeze rails to a previous version of the
> plugin which is installed in /usr/lib/ruby/gems along side the latest.
>
> Also I can't use rake rails:freeze:edge TAG=rel_1-2-6 because my host
> doesn't have svn installed.
>

You can download Rails 1.2.6 in other computer and copy all file in
/vendor/rails it's like the rake task

-- 
Cyril Mougel
http://blog.shingara.fr

From orangej2 at gmail.com  Thu Dec 13 11:19:20 2007
From: orangej2 at gmail.com (John Gedeon)
Date: Thu, 13 Dec 2007 08:19:20 -0800
Subject: [typo] Help Rails 2.0 with typo 4.1.1
In-Reply-To: <ac23b0bb0712130811v10044860o1cdf2cf4dcaf34b0@mail.gmail.com>
References: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>
	<ac23b0bb0712130811v10044860o1cdf2cf4dcaf34b0@mail.gmail.com>
Message-ID: <68dc58930712130819h2b0abce8m3bf79e7da5f353ad@mail.gmail.com>

I wonder if that is different from the /usr/lib/ruby/gems/1.8/gems/rails-
1.2.6 install of rails since I tried copying that to vendor rails and it
complained of not finding railties/lib/initializer.

script/about
./script/../config/boot.rb:16:in `require': no such file to load --
script/../config/../vendor/rails/railties/lib/initializer (LoadError)
        from ./script/../config/boot.rb:16
        from script/about:2:in `require'
        from script/about:2

I am downloading 1.2.6 from the site now though and will give that a shot.

Thanks for the tip.

John


On 12/13/07, Cyril Mougel <cyril.mougel at gmail.com> wrote:
>
> On Dec 13, 2007 5:06 PM, John Gedeon <orangej2 at gmail.com> wrote:
> > I have typo 4.1.1 installed on my host that just upgraded to rails 2.0.1
> .
> > They still have rails 1.2.6 installed but typo is using 2.0.1 and is
> broken
> > with a huge stack trace that I didn't have before, and I have made no
> > changes myself so it must be that. I know I should have frozen the gem
> > before, but now I do not know how to switch it so that typo uses the old
> > rails plugin. I tried adding RAILS_GEM_VERSION = ' 1.2.6' in my
> > environment.rb file but that doesn't help.
> >
> > Please let me know if there is any other useful info I can send. Mostly
> I
> > think I just need to know how to freeze rails to a previous version of
> the
> > plugin which is installed in /usr/lib/ruby/gems along side the latest.
> >
> > Also I can't use rake rails:freeze:edge TAG=rel_1-2-6 because my host
> > doesn't have svn installed.
> >
>
> You can download Rails 1.2.6 in other computer and copy all file in
> /vendor/rails it's like the rake task
>
> --
> Cyril Mougel
> http://blog.shingara.fr
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071213/aef26770/attachment.html 

From rick.denatale at gmail.com  Thu Dec 13 11:45:45 2007
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Thu, 13 Dec 2007 11:45:45 -0500
Subject: [typo] Help Rails 2.0 with typo 4.1.1
In-Reply-To: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>
References: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>
Message-ID: <deb2337a0712130845u43f10527s7e75b46eee5348aa@mail.gmail.com>

On 12/13/07, John Gedeon <orangej2 at gmail.com> wrote:
> I have typo 4.1.1 installed on my host that just upgraded to rails 2.0.1.
> They still have rails 1.2.6 installed but typo is using 2.0.1 and is broken
> with a huge stack trace that I didn't have before, and I have made no
> changes myself so it must be that. I know I should have frozen the gem
> before, but now I do not know how to switch it so that typo uses the old
> rails plugin. I tried adding RAILS_GEM_VERSION = ' 1.2.6' in my
> environment.rb file but that doesn't help.
>
> Please let me know if there is any other useful info I can send. Mostly I
> think I just need to know how to freeze rails to a previous version of the
> plugin which is installed in /usr/lib/ruby/gems along side the latest.
>
> Also I can't use rake rails:freeze:edge TAG=rel_1-2-6 because my host
> doesn't have svn installed.

I think you can use
 rake freeze:gems VERSION=1.2.6

The freeze:gems task seems to use the VERSION environment variable.


-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

From orangej2 at gmail.com  Thu Dec 13 12:02:27 2007
From: orangej2 at gmail.com (John Gedeon)
Date: Thu, 13 Dec 2007 09:02:27 -0800
Subject: [typo] Help Rails 2.0 with typo 4.1.1
In-Reply-To: <deb2337a0712130845u43f10527s7e75b46eee5348aa@mail.gmail.com>
References: <68dc58930712130806r12af9ea2n5c652d9ceb04171a@mail.gmail.com>
	<deb2337a0712130845u43f10527s7e75b46eee5348aa@mail.gmail.com>
Message-ID: <68dc58930712130902j3067eef7s4278b010f5643743@mail.gmail.com>

Thanks for the follow up. I tried rake rails:freeze:gems VERSION=1.2.6 and
found this result:


Freezing to the gems for Rails 1.2.6
ERROR:  While executing gem ... (Gem::Exception)
    Cannot load gem at [/usr/lib/ruby/gems/1.8/cache/activesupport-1.4.4.gem
]
gedeonsc at gedeons.com [~/custom_apps/typo-4.1.1-ctpd]#
script/about              ./script/../config/boot.rb:16:in `require': no
such file to load --
script/../config/../vendor/rails/railties/lib/initializer (LoadError)
        from ./script/../config/boot.rb:16
        from script/about:2:in `require'
        from script/about:2


So that seems like it would have worked but maybe my hosts install of
1.2.6is incomplete. Fortunately the downloaded tgz of rails had the
vendor/rails
directory I needed. and putting that in vendor/rails of typo fixed the
issue.

Thanks again for the quick reply

John

On 12/13/07, Rick DeNatale <rick.denatale at gmail.com> wrote:
>
> On 12/13/07, John Gedeon <orangej2 at gmail.com> wrote:
> > I have typo 4.1.1 installed on my host that just upgraded to rails 2.0.1
> .
> > They still have rails 1.2.6 installed but typo is using 2.0.1 and is
> broken
> > with a huge stack trace that I didn't have before, and I have made no
> > changes myself so it must be that. I know I should have frozen the gem
> > before, but now I do not know how to switch it so that typo uses the old
> > rails plugin. I tried adding RAILS_GEM_VERSION = ' 1.2.6' in my
> > environment.rb file but that doesn't help.
> >
> > Please let me know if there is any other useful info I can send. Mostly
> I
> > think I just need to know how to freeze rails to a previous version of
> the
> > plugin which is installed in /usr/lib/ruby/gems along side the latest.
> >
> > Also I can't use rake rails:freeze:edge TAG=rel_1-2-6 because my host
> > doesn't have svn installed.
>
> I think you can use
> rake freeze:gems VERSION=1.2.6
>
> The freeze:gems task seems to use the VERSION environment variable.
>
>
> --
> Rick DeNatale
>
> My blog on Ruby
> http://talklikeaduck.denhaven2.com/
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071213/da6f777b/attachment-0001.html 

From robjlucas at googlemail.com  Fri Dec 14 06:15:20 2007
From: robjlucas at googlemail.com (rob lucas)
Date: Fri, 14 Dec 2007 11:15:20 +0000
Subject: [typo] LoadError starting typo: Expected
	(...)app/models/category.rb to define Category
Message-ID: <486be5dc0712140315g49dc6d36g67ce2f9df2d64b41@mail.gmail.com>

Hi,

I'm having some problems getting Typo running.

Anyone got any idea why this is happening?

LoadError (Expected
> /var/www/FoggedUpBeyondAllRecognition/app/models/category.rb to define
> Category):
>

If I turn off class caching, instead I get:

NameError (undefined local variable or method `acts_as_list' for
> #<Class:0x40b5a960>):
>     /var/lib/gems/1.8/gems/activerecord-2.0.1/lib/active_record/base.rb:1459:in
> `method_missing'
>     /app/models/category.rb:2
>     ...etc...
>

It seems that a problem with acts_as_list is breaking the Category class.

Any help would be much appreciated.

Thanks,

Rob.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071214/ece278ef/attachment.html 

From dmitry.sustretov at gmail.com  Fri Dec 14 09:36:35 2007
From: dmitry.sustretov at gmail.com (Dmitry Sustretov)
Date: Fri, 14 Dec 2007 15:36:35 +0100
Subject: [typo] LoadError starting typo: Expected
	(...)app/models/category.rb to define Category
In-Reply-To: <486be5dc0712140315g49dc6d36g67ce2f9df2d64b41@mail.gmail.com>
References: <486be5dc0712140315g49dc6d36g67ce2f9df2d64b41@mail.gmail.com>
Message-ID: <85a11e30712140636m3014a1f8ve29b36f8d3a87560@mail.gmail.com>

I had those messages when I tried to run typo on Rails 2.0.

Try to run it with Rails 1.2.

On 14/12/2007, rob lucas <robjlucas at googlemail.com> wrote:
> Hi,
>
> I'm having some problems getting Typo running.
>
> Anyone got any idea why this is happening?
>
> > LoadError (Expected
> /var/www/FoggedUpBeyondAllRecognition/app/models/category.rb
> to define Category):
> >
>
> If I turn off class caching, instead I get:
>
> > NameError (undefined local variable or method `acts_as_list' for
> #<Class:0x40b5a960>):
> >
> /var/lib/gems/1.8/gems/activerecord-2.0.1/lib/active_record/base.rb:1459:in
> `method_missing'
> >     /app/models/category.rb:2
> >     ...etc...
> >
>
> It seems that a problem with acts_as_list is breaking the Category class.
>
> Any help would be much appreciated.
>
> Thanks,
>
> Rob.
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>


-- 
Dmitry Sustretov
------------------------------------------------------------
-- PhD student at INRIA Lorraine-LORIA
-- http://www.loria.fr/~sustreto/
------------------------------------------------------------

From frederic at de-villamil.com  Fri Dec 14 10:07:33 2007
From: frederic at de-villamil.com (Frederic de Villamil)
Date: Fri, 14 Dec 2007 16:07:33 +0100
Subject: [typo] Test with new address
Message-ID: <BF1D7B9C-CC1C-44C9-9CB5-A22DF790CC19@de-villamil.com>

Test list as it seems my current address doesn't work, sorry for the  
spam.

Frederic

From frederic at de-villamil.com  Fri Dec 14 10:12:40 2007
From: frederic at de-villamil.com (Frederic de Villamil)
Date: Fri, 14 Dec 2007 16:12:40 +0100
Subject: [typo] LoadError starting typo: Expected
	(...)app/models/category.rb to define Category
In-Reply-To: <85a11e30712140636m3014a1f8ve29b36f8d3a87560@mail.gmail.com>
References: <486be5dc0712140315g49dc6d36g67ce2f9df2d64b41@mail.gmail.com>
	<85a11e30712140636m3014a1f8ve29b36f8d3a87560@mail.gmail.com>
Message-ID: <EB9BB899-C836-4A93-B463-922F6E0AFE13@de-villamil.com>

Hello,

Typo stable / trunk is not suited to work with Rails 2.0

We have a Rails 2.0 branch, which may lead to a very soon release  
(release planned on sunday December the 16th if things keep going on  
this way)

We've et up a poll on Typo official weblog to let you choose the next  
typo theme. It's at http://blog.typosphere.org/articles/2007/12/13/poll-a-new-default-theme-for-typo-5-0

Best regards,
Fr?d?ric

Le 14 d?c. 07 ? 15:36, Dmitry Sustretov a ?crit :

> I had those messages when I tried to run typo on Rails 2.0.
>
> Try to run it with Rails 1.2.
>
> On 14/12/2007, rob lucas <robjlucas at googlemail.com> wrote:
>> Hi,
>>
>> I'm having some problems getting Typo running.
>>
>> Anyone got any idea why this is happening?
>>
>>> LoadError (Expected
>> /var/www/FoggedUpBeyondAllRecognition/app/models/category.rb
>> to define Category):
>>>
>>
>> If I turn off class caching, instead I get:
>>
>>> NameError (undefined local variable or method `acts_as_list' for
>> #<Class:0x40b5a960>):
>>>
>> /var/lib/gems/1.8/gems/activerecord-2.0.1/lib/active_record/base.rb: 
>> 1459:in
>> `method_missing'
>>>    /app/models/category.rb:2
>>>    ...etc...
>>>
>>
>> It seems that a problem with acts_as_list is breaking the Category  
>> class.
>>
>> Any help would be much appreciated.
>>
>> Thanks,
>>
>> Rob.
>> _______________________________________________
>> Typo-list mailing list
>> Typo-list at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/typo-list
>>
>
>
> -- 
> Dmitry Sustretov
> ------------------------------------------------------------
> -- PhD student at INRIA Lorraine-LORIA
> -- http://www.loria.fr/~sustreto/
> ------------------------------------------------------------
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list


From roblucas at lucasandblench.com  Fri Dec 14 11:11:28 2007
From: roblucas at lucasandblench.com (rob lucas)
Date: Fri, 14 Dec 2007 16:11:28 +0000
Subject: [typo] LoadError starting typo: Expected
	(...)app/models/category.rb to define Category
In-Reply-To: <EB9BB899-C836-4A93-B463-922F6E0AFE13@de-villamil.com>
References: <486be5dc0712140315g49dc6d36g67ce2f9df2d64b41@mail.gmail.com>
	<85a11e30712140636m3014a1f8ve29b36f8d3a87560@mail.gmail.com>
	<EB9BB899-C836-4A93-B463-922F6E0AFE13@de-villamil.com>
Message-ID: <486be5dc0712140811q18d64bbg20c3ca1e62cd43a8@mail.gmail.com>

Great. I have it working now. It was indeed the version of Rails. Thanks for
the help guys.

Rob.

On Dec 14, 2007 3:12 PM, Frederic de Villamil <frederic at de-villamil.com>
wrote:

> Hello,
>
> Typo stable / trunk is not suited to work with Rails 2.0
>
> We have a Rails 2.0 branch, which may lead to a very soon release
> (release planned on sunday December the 16th if things keep going on
> this way)
>
> We've et up a poll on Typo official weblog to let you choose the next
> typo theme. It's at
> http://blog.typosphere.org/articles/2007/12/13/poll-a-new-default-theme-for-typo-5-0
>
> Best regards,
> Fr?d?ric
>
> Le 14 d?c. 07 ? 15:36, Dmitry Sustretov a ?crit :
>
> > I had those messages when I tried to run typo on Rails 2.0.
> >
> > Try to run it with Rails 1.2.
> >
> > On 14/12/2007, rob lucas <robjlucas at googlemail.com> wrote:
> >> Hi,
> >>
> >> I'm having some problems getting Typo running.
> >>
> >> Anyone got any idea why this is happening?
> >>
> >>> LoadError (Expected
> >> /var/www/FoggedUpBeyondAllRecognition/app/models/category.rb
> >> to define Category):
> >>>
> >>
> >> If I turn off class caching, instead I get:
> >>
> >>> NameError (undefined local variable or method `acts_as_list' for
> >> #<Class:0x40b5a960>):
> >>>
> >> /var/lib/gems/1.8/gems/activerecord-2.0.1/lib/active_record/base.rb:
> >> 1459:in
> >> `method_missing'
> >>>    /app/models/category.rb:2
> >>>    ...etc...
> >>>
> >>
> >> It seems that a problem with acts_as_list is breaking the Category
> >> class.
> >>
> >> Any help would be much appreciated.
> >>
> >> Thanks,
> >>
> >> Rob.
> >> _______________________________________________
> >> Typo-list mailing list
> >> Typo-list at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/typo-list
> >>
> >
> >
> > --
> > Dmitry Sustretov
> > ------------------------------------------------------------
> > -- PhD student at INRIA Lorraine-LORIA
> > -- http://www.loria.fr/~sustreto/ <http://www.loria.fr/%7Esustreto/>
> > ------------------------------------------------------------
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/typo-list
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071214/8a5dcb96/attachment.html 

From roblucas at lucasandblench.com  Wed Dec 19 13:08:48 2007
From: roblucas at lucasandblench.com (rob lucas)
Date: Wed, 19 Dec 2007 18:08:48 +0000
Subject: [typo] send_file problem?
Message-ID: <486be5dc0712191008j3997da0dj47aa675a62c057bd@mail.gmail.com>

I see that typo uses routing to deal with the switching that goes on between
different themes...

  map.connect 'stylesheets/theme/:filename',
    :controller => 'theme', :action => 'stylesheets', :filename => /.*/

... which takes us to the stylesheets action of the themes controller...

  def stylesheets
    render_theme_item(:stylesheets, params[:filename], 'text/css;
charset=utf-8')
  end

... which uses the render_theme_item action...

    send_file(this_blog.current_theme.path + "/#{type}/#{file}",
              :type => mime, :disposition => 'inline', :stream => false)

... which uses "send_file" to serve the theme files from within the
framework to the outside world, as if they were in the public directory.

BUT... This is broken on my installation. The theme files simply don't show
up, so I get a nice unstyled blog. I only managed to get it to work by
simply copying the theme files into the public directory, which is not
ideal. Anyone know what is wrong here?

I'm using Typo 4.1, Rails 1.2.0, & Ruby 1.8.5

Cheers,

Rob.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071219/b7728ac6/attachment.html 

From cpatti at gmail.com  Fri Dec 21 12:02:36 2007
From: cpatti at gmail.com (Chris Patti)
Date: Fri, 21 Dec 2007 12:02:36 -0500
Subject: [typo] A parting suggestion
Message-ID: <7b528f860712210902y36d1cf0ewb251042d8a55ca7f@mail.gmail.com>

Typo is a great blogging engine, but as it stands today, unless you're
willing to roll your sleeves up and tangle with some fairly substantial
RAILS code, there are a number of situations wherein your Typo installation
can begin to fail with no obvious repair steps in sight to take.

So, just a humble opinion - you might want the docs to reflect that.  I
would think the Typo community would be better served by having people
participating who can handle the level of  expertise needed to keep their
installation rolling and also contribute meaningfully to the community.

Thanks for everything and good luck with Typo!
-Chris

-- 
Chris Patti --- Y!: feoh -- AIM: chrisfeohpatti --- E-Mail:
cpatti at gmail.com
"Technological progress is like an ax in the hands of a pathological
criminal." -Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071221/950bf758/attachment.html 

From crazy.bisht at gmail.com  Sun Dec 30 09:01:58 2007
From: crazy.bisht at gmail.com (Sanjay Bisht)
Date: Sun, 30 Dec 2007 19:31:58 +0530
Subject: [typo] Layouts help needed
Message-ID: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>

Hi,

I am trying to create a new theme for Typo. For this I want the index page
to have a different layout than the rest of the pages. Can someone please
help me in this direction, as to how can I set up a new layout for the index
page apart from the default layout.

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071230/b1b07872/attachment-0001.html 

From pdcawley at bofh.org.uk  Sun Dec 30 09:42:33 2007
From: pdcawley at bofh.org.uk (Piers Cawley)
Date: Sun, 30 Dec 2007 14:42:33 +0000
Subject: [typo] Layouts help needed
In-Reply-To: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>
References: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>
Message-ID: <897e96cc0712300642t57c12770g21662676f8b75019@mail.gmail.com>

On 12/30/07, Sanjay Bisht <crazy.bisht at gmail.com> wrote:
> Hi,
>
> I am trying to create a new theme for Typo. For this I want the index page
> to have a different layout than the rest of the pages. Can someone please
> help me in this direction, as to how can I set up a new layout for the index
> page apart from the default layout.

You can't. Well, not directly. You'd have to have a test in the
default layout and have it select the actual layout partial to use.

From crazy.bisht at gmail.com  Sun Dec 30 11:25:50 2007
From: crazy.bisht at gmail.com (Sanjay Bisht)
Date: Sun, 30 Dec 2007 21:55:50 +0530
Subject: [typo] Layouts help needed
In-Reply-To: <897e96cc0712300642t57c12770g21662676f8b75019@mail.gmail.com>
References: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>
	<897e96cc0712300642t57c12770g21662676f8b75019@mail.gmail.com>
Message-ID: <c8a227ac0712300825y1cfe9b9dk6ad26a508e1af0b6@mail.gmail.com>

Hi Piers,

Can you please explain as to what you just mentioned. I did not understand
you perfectly.

On Dec 30, 2007 8:12 PM, Piers Cawley <pdcawley at bofh.org.uk> wrote:

> On 12/30/07, Sanjay Bisht <crazy.bisht at gmail.com> wrote:
> > Hi,
> >
> > I am trying to create a new theme for Typo. For this I want the index
> page
> > to have a different layout than the rest of the pages. Can someone
> please
> > help me in this direction, as to how can I set up a new layout for the
> index
> > page apart from the default layout.
>
> You can't. Well, not directly. You'd have to have a test in the
> default layout and have it select the actual layout partial to use.
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071230/c2e76db7/attachment.html 

From benr at x-cr.com  Sun Dec 30 12:18:21 2007
From: benr at x-cr.com (Ben Reubenstein)
Date: Sun, 30 Dec 2007 10:18:21 -0700
Subject: [typo] Layouts help needed
In-Reply-To: <c8a227ac0712300825y1cfe9b9dk6ad26a508e1af0b6@mail.gmail.com>
References: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>
	<897e96cc0712300642t57c12770g21662676f8b75019@mail.gmail.com>
	<c8a227ac0712300825y1cfe9b9dk6ad26a508e1af0b6@mail.gmail.com>
Message-ID: <44c79a160712300918p6f2e80bfr9ee301a34636b4b2@mail.gmail.com>

Hi ~
You would implement this by checking if the controller/action is the index
page on the layout for your theme.  If it is you would render a different
partial.  I guess you could do it with a before_filter too that dynamically
assigned the layout, but this could get messy since you would be messing
with the Typo source.

~ Ben

On 12/30/07, Sanjay Bisht <crazy.bisht at gmail.com> wrote:
>
> Hi Piers,
>
> Can you please explain as to what you just mentioned. I did not understand
> you perfectly.
>
> On Dec 30, 2007 8:12 PM, Piers Cawley <pdcawley at bofh.org.uk > wrote:
>
> > On 12/30/07, Sanjay Bisht < crazy.bisht at gmail.com> wrote:
> > > Hi,
> > >
> > > I am trying to create a new theme for Typo. For this I want the index
> > page
> > > to have a different layout than the rest of the pages. Can someone
> > please
> > > help me in this direction, as to how can I set up a new layout for the
> > index
> > > page apart from the default layout.
> >
> >
> > You can't. Well, not directly. You'd have to have a test in the
> > default layout and have it select the actual layout partial to use.
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/typo-list
> >
>
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>



-- 
Ben Reubenstein
303-947-0446
http://www.x-cr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071230/20ebf699/attachment.html 

From frederic at de-villamil.com  Sun Dec 30 13:09:46 2007
From: frederic at de-villamil.com (Frederic de Villamil)
Date: Sun, 30 Dec 2007 19:09:46 +0100
Subject: [typo] Layouts help needed
In-Reply-To: <44c79a160712300918p6f2e80bfr9ee301a34636b4b2@mail.gmail.com>
References: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>
	<897e96cc0712300642t57c12770g21662676f8b75019@mail.gmail.com>
	<c8a227ac0712300825y1cfe9b9dk6ad26a508e1af0b6@mail.gmail.com>
	<44c79a160712300918p6f2e80bfr9ee301a34636b4b2@mail.gmail.com>
Message-ID: <9067E678-68CA-4D46-A5C5-C2BD5A54BE3F@de-villamil.com>

Hello,

Even tough I hate using conditionnal statement in themes, the solution  
I use is

if controller.controller_name == 'foobar' and controller.action_name  
== 'foobar'
do something
else
do soemthing else
end

Hope this helps
Fred

Le 30 d?c. 07 ? 18:18, Ben Reubenstein a ?crit :

> Hi ~
>
> You would implement this by checking if the controller/action is the  
> index page on the layout for your theme.  If it is you would render  
> a different partial.  I guess you could do it with a before_filter  
> too that dynamically assigned the layout, but this could get messy  
> since you would be messing with the Typo source.
>
> ~ Ben
>
> On 12/30/07, Sanjay Bisht <crazy.bisht at gmail.com > wrote:
> Hi Piers,
>
> Can you please explain as to what you just mentioned. I did not  
> understand you perfectly.
>
>
> On Dec 30, 2007 8:12 PM, Piers Cawley < pdcawley at bofh.org.uk > wrote:
> On 12/30/07, Sanjay Bisht < crazy.bisht at gmail.com> wrote:
> > Hi,
> >
> > I am trying to create a new theme for Typo. For this I want the  
> index page
> > to have a different layout than the rest of the pages. Can someone  
> please
> > help me in this direction, as to how can I set up a new layout for  
> the index
> > page apart from the default layout.
>
>
> You can't. Well, not directly. You'd have to have a test in the
> default layout and have it select the actual layout partial to use.
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
>
>
> -- 
> Ben Reubenstein
> 303-947-0446
> http://www.x-cr.com
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071230/3fdbcecc/attachment.html 

From crazy.bisht at gmail.com  Sun Dec 30 13:32:33 2007
From: crazy.bisht at gmail.com (Sanjay Bisht)
Date: Mon, 31 Dec 2007 00:02:33 +0530
Subject: [typo] Layouts help needed
In-Reply-To: <9067E678-68CA-4D46-A5C5-C2BD5A54BE3F@de-villamil.com>
References: <c8a227ac0712300601t435b6dbidb0e0e11d6567258@mail.gmail.com>
	<897e96cc0712300642t57c12770g21662676f8b75019@mail.gmail.com>
	<c8a227ac0712300825y1cfe9b9dk6ad26a508e1af0b6@mail.gmail.com>
	<44c79a160712300918p6f2e80bfr9ee301a34636b4b2@mail.gmail.com>
	<9067E678-68CA-4D46-A5C5-C2BD5A54BE3F@de-villamil.com>
Message-ID: <c8a227ac0712301032i55992f68p6312ceded251ba7c@mail.gmail.com>

Hey,

Even I was thinking on the same lines, but somehow it's not giving me the
satisfaction (the one that you get when you know the job is perfectly done
:) ). I guess that I will have to try the else-if loop only.

Thanks and regards

On Dec 30, 2007 11:39 PM, Frederic de Villamil <frederic at de-villamil.com>
wrote:

> Hello,
> Even tough I hate using conditionnal statement in themes, the solution I
> use is
>
> if controller.controller_name == 'foobar' and controller.action_name ==
> 'foobar'
> do something
> else
> do soemthing else
> end
>
> Hope this helps
> Fred
>
> Le 30 d?c. 07 ? 18:18, Ben Reubenstein a ?crit :
>
> Hi ~
> You would implement this by checking if the controller/action is the index
> page on the layout for your theme.  If it is you would render a different
> partial.  I guess you could do it with a before_filter too that dynamically
> assigned the layout, but this could get messy since you would be messing
> with the Typo source.
>
> ~ Ben
>
> On 12/30/07, Sanjay Bisht <crazy.bisht at gmail.com > wrote:
> >
> > Hi Piers,
> >
> > Can you please explain as to what you just mentioned. I did not
> > understand you perfectly.
> >
> > On Dec 30, 2007 8:12 PM, Piers Cawley < pdcawley at bofh.org.uk > wrote:
> >
> > > On 12/30/07, Sanjay Bisht < crazy.bisht at gmail.com> wrote:
> > > > Hi,
> > > >
> > > > I am trying to create a new theme for Typo. For this I want the
> > > index page
> > > > to have a different layout than the rest of the pages. Can someone
> > > please
> > > > help me in this direction, as to how can I set up a new layout for
> > > the index
> > > > page apart from the default layout.
> > >
> > >
> > > You can't. Well, not directly. You'd have to have a test in the
> > > default layout and have it select the actual layout partial to use.
> > > _______________________________________________
> > > Typo-list mailing list
> > > Typo-list at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/typo-list
> > >
> >
> >
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/typo-list
> >
>
>
>
> --
> Ben Reubenstein
> 303-947-0446
> http://www.x-cr.com
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
>
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071231/5b80ab40/attachment-0001.html 

From frederic at de-villamil.com  Sun Dec 30 14:18:42 2007
From: frederic at de-villamil.com (Frederic de Villamil)
Date: Sun, 30 Dec 2007 20:18:42 +0100
Subject: [typo] Typo 5.0 "Eugene Atget" for Rails 2.0 is out
Message-ID: <6A99CBB7-626F-41AE-A6E9-07F0FAC0157B@de-villamil.com>



Typo 5.0 "Eug?ne Atget" finally finished after about 7 month of  
making. This in an important release, stuffed with great new features,  
loads of fixes and an incredible amount of polish. This may sound like  
DHH introduction to Rails 2.0, and it does, because Typo 5.0 now runs  
with Ruby on Rails 2.0 and won't run with anything else. That's the  
reason of the major version change.

Before jumping into the breakdown of features, I?d just like to extend  
my deep gratitude towards everyone who helped make this release  
possible. From Piers who made this possible to the (hundreds of)  
contributors who got a patch applied to everyone on #typo who kept the  
spirit alive. You can all be mighty proud of the role you played.  
Cheers!

** Why Eug?ne Atget ? **

I've wanted to give our releases a name for a while now, but we needed  
to find a path we should follow from along the versions. Piers and I  
are both photographers, and most of the visible work on Typo has been  
done in Paris, which is a town Atget spent his life to picture. That's  
the reason why his name came first when we had to choose one.

** Sidebars removal **

As we announced earlier, we've decided to move most of the sidebars  
plugins out of the trunk. There are many reasons why we think that,  
out of some basic functionnalities, sidebars should be third party  
softwares apart performances issues. We'll continue to maintain these  
plugins anyway.

If you're using one of the following plugins, be sure to install it,  
or your blog may explode with lots of nasty error messages.

? AIM presence
? Audioscrobbler
? Backpack
? Delicious
? Flickr
? 43 things
? 43 places
? Magnolia
? Recent comments
? Tada
? Upcoming
? Xbox


Plugins are now in our plugins repository (http://svn.typosphere.org/typo/plugins/ 
), and installs like any rails plugin. Expect basic archives soon.

** Code refactoring **

The immerged part of the iceberg, but not the least one, most of the  
existing code has been rewriten. Typo was started when Rails was  
young, very young, and lots of things were added to the framework  
after we had to write them.

The result is impressive in terms of performances, and bug fixing as  
well.

** Admin refactoring**

Admin has been entirely revamped, twice, between 4.1 and 5.0, and  
we're quite proud of how it works now.

The existing admin was the result of a scaffold during Typo early  
days, and even though some improvements has been done, many things  
were not as user friendly as they should have been. New admin now aims  
at giving a clear view on the information, and eased access to the  
most daily used functionnalities in your blogging life.

? Simple and avanced admin

We now deliver the admin in 2 flavors, simple and advanced, because  
everybody doesn't have the same need when it goes to blogging. We have  
also splitted the settings in 2 places, to separate basic and advanced  
settings.

? More localisation

4.1 introduced Typo internationalization, but no one noticed it as it  
was hidden in the deep of environment.rb. You can now choose your  
prefered language from the settings. We hope the community to support  
the translation effort.

? Comments moderation

Another hidden feature of 4.1 I think it's important to mention here  
is default comment moderation. This is a stone in the build of a  
better discussion management.

? Theme editor

A theme editor was a missing piece in Typo admin, and it's now filled  
with a basic, but usable editor. For now it allows you to edit your  
layout and stylesheet. Views editing will come later.

? Dashboard

We've also added a dashboard we plan to improve with time. It aims at  
giving you a view on the latests activity on your Typo blog.

** Solving SEO issues**

For long time now, Typo has been a pain to search engine optimisation,  
mostly because most pages, out of single posts, had the same meta  
title and description. That thing we never noticed before had nasty  
effects when melted with Google duplicate content algorythm, which  
even led some blogs to be banned from index. Expect some more  
improvement in a near future.

** New themes**

Azure which has been Typo default theme for a while now has been  
removed from the core and won't be supported anymore. Standard issue  
is now our new default theme, and we have introduced Dirtylicious as  
well. Scribbish has been kept for backward compatibility as many blogs  
are using it, starting Piers.

Both themes were built above Scribbish markup and are thus hatom  
compliant.

** Typo themes garden**

I know this should be a community matter, and it may not have its  
place on a release note, however I think it's important enough to  
mention it. Every theme listed on <a href="http://www.dev411.com/typo/themes/ 
">dev 411 Typo theme viewer</a> has been updated to support Typo 5.0,  
and updated themes are already avaliable.

We do think having a usable themes and plugins park is important, and  
too many themes were only Typo 2.6.0 compatible. That's the reason why  
we did the themes migration while finishing Typo 5.0, and we plan to  
port even more non Typo themes in a near futur.

** And now ?**

Now, we're going to have some rest while you're migrating and giving  
your first feedbacks. We already have a new roadmap to Typo 5.1, which  
contains

? Atom Publishing Protocol.
? Admin feeds.
? Working to make the admin interface talk APP.
? Themes with helpers.
? Customizing the Feedback state machine so different spam protection  
engines can use different states.
? Add users grants
? OpenID consumption.
? If we really have to, multiblogging...
? Even more admin improvement.
? Doc, doc and even more doc.
? Plugin manager tool.


We hope you'll enjoy this release as much as we enjoyed making it.

Fr?d?ric and Piers

From benr at x-cr.com  Sun Dec 30 16:15:58 2007
From: benr at x-cr.com (Ben Reubenstein)
Date: Sun, 30 Dec 2007 14:15:58 -0700
Subject: [typo] Typo 5.0 "Eugene Atget" for Rails 2.0 is out
In-Reply-To: <6A99CBB7-626F-41AE-A6E9-07F0FAC0157B@de-villamil.com>
References: <6A99CBB7-626F-41AE-A6E9-07F0FAC0157B@de-villamil.com>
Message-ID: <44c79a160712301315k22dd7a6bg53bc572bfb0d7011@mail.gmail.com>

Hi Frederic ~

Awesome work! I am excited to migrate.  For those of us upgrading, are there
any special things we need to do besides pulling the latest version,
migrating our database, and checking the sidebar items we use?
 I apologize if this is addressed somewhere in the doc.
~ Ben

On 12/30/07, Frederic de Villamil <frederic at de-villamil.com> wrote:
>
>
>
> Typo 5.0 "Eug?ne Atget" finally finished after about 7 month of
> making. This in an important release, stuffed with great new features,
> loads of fixes and an incredible amount of polish. This may sound like
> DHH introduction to Rails 2.0, and it does, because Typo 5.0 now runs
> with Ruby on Rails 2.0 and won't run with anything else. That's the
> reason of the major version change.
>
> Before jumping into the breakdown of features, I'd just like to extend
> my deep gratitude towards everyone who helped make this release
> possible. From Piers who made this possible to the (hundreds of)
> contributors who got a patch applied to everyone on #typo who kept the
> spirit alive. You can all be mighty proud of the role you played.
> Cheers!
>
> ** Why Eug?ne Atget ? **
>
> I've wanted to give our releases a name for a while now, but we needed
> to find a path we should follow from along the versions. Piers and I
> are both photographers, and most of the visible work on Typo has been
> done in Paris, which is a town Atget spent his life to picture. That's
> the reason why his name came first when we had to choose one.
>
> ** Sidebars removal **
>
> As we announced earlier, we've decided to move most of the sidebars
> plugins out of the trunk. There are many reasons why we think that,
> out of some basic functionnalities, sidebars should be third party
> softwares apart performances issues. We'll continue to maintain these
> plugins anyway.
>
> If you're using one of the following plugins, be sure to install it,
> or your blog may explode with lots of nasty error messages.
>
> ? AIM presence
> ? Audioscrobbler
> ? Backpack
> ? Delicious
> ? Flickr
> ? 43 things
> ? 43 places
> ? Magnolia
> ? Recent comments
> ? Tada
> ? Upcoming
> ? Xbox
>
>
> Plugins are now in our plugins repository (
> http://svn.typosphere.org/typo/plugins/
> ), and installs like any rails plugin. Expect basic archives soon.
>
> ** Code refactoring **
>
> The immerged part of the iceberg, but not the least one, most of the
> existing code has been rewriten. Typo was started when Rails was
> young, very young, and lots of things were added to the framework
> after we had to write them.
>
> The result is impressive in terms of performances, and bug fixing as
> well.
>
> ** Admin refactoring**
>
> Admin has been entirely revamped, twice, between 4.1 and 5.0, and
> we're quite proud of how it works now.
>
> The existing admin was the result of a scaffold during Typo early
> days, and even though some improvements has been done, many things
> were not as user friendly as they should have been. New admin now aims
> at giving a clear view on the information, and eased access to the
> most daily used functionnalities in your blogging life.
>
> ? Simple and avanced admin
>
> We now deliver the admin in 2 flavors, simple and advanced, because
> everybody doesn't have the same need when it goes to blogging. We have
> also splitted the settings in 2 places, to separate basic and advanced
> settings.
>
> ? More localisation
>
> 4.1 introduced Typo internationalization, but no one noticed it as it
> was hidden in the deep of environment.rb. You can now choose your
> prefered language from the settings. We hope the community to support
> the translation effort.
>
> ? Comments moderation
>
> Another hidden feature of 4.1 I think it's important to mention here
> is default comment moderation. This is a stone in the build of a
> better discussion management.
>
> ? Theme editor
>
> A theme editor was a missing piece in Typo admin, and it's now filled
> with a basic, but usable editor. For now it allows you to edit your
> layout and stylesheet. Views editing will come later.
>
> ? Dashboard
>
> We've also added a dashboard we plan to improve with time. It aims at
> giving you a view on the latests activity on your Typo blog.
>
> ** Solving SEO issues**
>
> For long time now, Typo has been a pain to search engine optimisation,
> mostly because most pages, out of single posts, had the same meta
> title and description. That thing we never noticed before had nasty
> effects when melted with Google duplicate content algorythm, which
> even led some blogs to be banned from index. Expect some more
> improvement in a near future.
>
> ** New themes**
>
> Azure which has been Typo default theme for a while now has been
> removed from the core and won't be supported anymore. Standard issue
> is now our new default theme, and we have introduced Dirtylicious as
> well. Scribbish has been kept for backward compatibility as many blogs
> are using it, starting Piers.
>
> Both themes were built above Scribbish markup and are thus hatom
> compliant.
>
> ** Typo themes garden**
>
> I know this should be a community matter, and it may not have its
> place on a release note, however I think it's important enough to
> mention it. Every theme listed on <a href="
> http://www.dev411.com/typo/themes/
> ">dev 411 Typo theme viewer</a> has been updated to support Typo 5.0,
> and updated themes are already avaliable.
>
> We do think having a usable themes and plugins park is important, and
> too many themes were only Typo 2.6.0 compatible. That's the reason why
> we did the themes migration while finishing Typo 5.0, and we plan to
> port even more non Typo themes in a near futur.
>
> ** And now ?**
>
> Now, we're going to have some rest while you're migrating and giving
> your first feedbacks. We already have a new roadmap to Typo 5.1, which
> contains
>
> ? Atom Publishing Protocol.
> ? Admin feeds.
> ? Working to make the admin interface talk APP.
> ? Themes with helpers.
> ? Customizing the Feedback state machine so different spam protection
> engines can use different states.
> ? Add users grants
> ? OpenID consumption.
> ? If we really have to, multiblogging...
> ? Even more admin improvement.
> ? Doc, doc and even more doc.
> ? Plugin manager tool.
>
>
> We hope you'll enjoy this release as much as we enjoyed making it.
>
> Fr?d?ric and Piers
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>



-- 
Ben Reubenstein
303-947-0446
http://www.x-cr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071230/c622a21c/attachment.html 

From frederic at de-villamil.com  Sun Dec 30 16:36:34 2007
From: frederic at de-villamil.com (Frederic de Villamil)
Date: Sun, 30 Dec 2007 22:36:34 +0100
Subject: [typo] Typo 5.0 "Eugene Atget" for Rails 2.0 is out
In-Reply-To: <44c79a160712301315k22dd7a6bg53bc572bfb0d7011@mail.gmail.com>
References: <6A99CBB7-626F-41AE-A6E9-07F0FAC0157B@de-villamil.com>
	<44c79a160712301315k22dd7a6bg53bc572bfb0d7011@mail.gmail.com>
Message-ID: <B8C6E27E-35F5-497B-8C52-DD0DD483F434@de-villamil.com>

Hi Ben,

I'd say, do like before any migration, backup your blog and database,  
pray a bit...
migrate should run like a charm if you 're upgrading from 4.x.

As I've said in the release, we've removed most of the plugins so  
you'll have to reinstall some of them. It's explained in the release  
note.

Regards,
Fr?d?ric


Le 30 d?c. 07 ? 22:15, Ben Reubenstein a ?crit :

> Hi Frederic ~
>
> Awesome work! I am excited to migrate.  For those of us upgrading,  
> are there any special things we need to do besides pulling the  
> latest version, migrating our database, and checking the sidebar  
> items we use?  I apologize if this is addressed somewhere in the doc.
>
> ~ Ben
>
> On 12/30/07, Frederic de Villamil <frederic at de-villamil.com > wrote:
>
>
> Typo 5.0 "Eug?ne Atget" finally finished after about 7 month of
> making. This in an important release, stuffed with great new features,
> loads of fixes and an incredible amount of polish. This may sound like
> DHH introduction to Rails 2.0, and it does, because Typo 5.0 now runs
> with Ruby on Rails 2.0 and won't run with anything else. That's the
> reason of the major version change.
>
> Before jumping into the breakdown of features, I'd just like to extend
> my deep gratitude towards everyone who helped make this release
> possible. From Piers who made this possible to the (hundreds of)
> contributors who got a patch applied to everyone on #typo who kept the
> spirit alive. You can all be mighty proud of the role you played.
> Cheers!
>
> ** Why Eug?ne Atget ? **
>
> I've wanted to give our releases a name for a while now, but we needed
> to find a path we should follow from along the versions. Piers and I
> are both photographers, and most of the visible work on Typo has been
> done in Paris, which is a town Atget spent his life to picture. That's
> the reason why his name came first when we had to choose one.
>
> ** Sidebars removal **
>
> As we announced earlier, we've decided to move most of the sidebars
> plugins out of the trunk. There are many reasons why we think that,
> out of some basic functionnalities, sidebars should be third party
> softwares apart performances issues. We'll continue to maintain these
> plugins anyway.
>
> If you're using one of the following plugins, be sure to install it,
> or your blog may explode with lots of nasty error messages.
>
> ? AIM presence
> ? Audioscrobbler
> ? Backpack
> ? Delicious
> ? Flickr
> ? 43 things
> ? 43 places
> ? Magnolia
> ? Recent comments
> ? Tada
> ? Upcoming
> ? Xbox
>
>
> Plugins are now in our plugins repository (http://svn.typosphere.org/typo/plugins/
> ), and installs like any rails plugin. Expect basic archives soon.
>
> ** Code refactoring **
>
> The immerged part of the iceberg, but not the least one, most of the
> existing code has been rewriten. Typo was started when Rails was
> young, very young, and lots of things were added to the framework
> after we had to write them.
>
> The result is impressive in terms of performances, and bug fixing as
> well.
>
> ** Admin refactoring**
>
> Admin has been entirely revamped, twice, between 4.1 and 5.0, and
> we're quite proud of how it works now.
>
> The existing admin was the result of a scaffold during Typo early
> days, and even though some improvements has been done, many things
> were not as user friendly as they should have been. New admin now aims
> at giving a clear view on the information, and eased access to the
> most daily used functionnalities in your blogging life.
>
> ? Simple and avanced admin
>
> We now deliver the admin in 2 flavors, simple and advanced, because
> everybody doesn't have the same need when it goes to blogging. We have
> also splitted the settings in 2 places, to separate basic and advanced
> settings.
>
> ? More localisation
>
> 4.1 introduced Typo internationalization, but no one noticed it as it
> was hidden in the deep of environment.rb. You can now choose your
> prefered language from the settings. We hope the community to support
> the translation effort.
>
> ? Comments moderation
>
> Another hidden feature of 4.1 I think it's important to mention here
> is default comment moderation. This is a stone in the build of a
> better discussion management.
>
> ? Theme editor
>
> A theme editor was a missing piece in Typo admin, and it's now filled
> with a basic, but usable editor. For now it allows you to edit your
> layout and stylesheet. Views editing will come later.
>
> ? Dashboard
>
> We've also added a dashboard we plan to improve with time. It aims at
> giving you a view on the latests activity on your Typo blog.
>
> ** Solving SEO issues**
>
> For long time now, Typo has been a pain to search engine optimisation,
> mostly because most pages, out of single posts, had the same meta
> title and description. That thing we never noticed before had nasty
> effects when melted with Google duplicate content algorythm, which
> even led some blogs to be banned from index. Expect some more
> improvement in a near future.
>
> ** New themes**
>
> Azure which has been Typo default theme for a while now has been
> removed from the core and won't be supported anymore. Standard issue
> is now our new default theme, and we have introduced Dirtylicious as
> well. Scribbish has been kept for backward compatibility as many blogs
> are using it, starting Piers.
>
> Both themes were built above Scribbish markup and are thus hatom
> compliant.
>
> ** Typo themes garden**
>
> I know this should be a community matter, and it may not have its
> place on a release note, however I think it's important enough to
> mention it. Every theme listed on <a href=" http://www.dev411.com/typo/themes/
> ">dev 411 Typo theme viewer</a> has been updated to support Typo 5.0,
> and updated themes are already avaliable.
>
> We do think having a usable themes and plugins park is important, and
> too many themes were only Typo 2.6.0 compatible. That's the reason why
> we did the themes migration while finishing Typo 5.0, and we plan to
> port even more non Typo themes in a near futur.
>
> ** And now ?**
>
> Now, we're going to have some rest while you're migrating and giving
> your first feedbacks. We already have a new roadmap to Typo 5.1, which
> contains
>
> ? Atom Publishing Protocol.
> ? Admin feeds.
> ? Working to make the admin interface talk APP.
> ? Themes with helpers.
> ? Customizing the Feedback state machine so different spam protection
> engines can use different states.
> ? Add users grants
> ? OpenID consumption.
> ? If we really have to, multiblogging...
> ? Even more admin improvement.
> ? Doc, doc and even more doc.
> ? Plugin manager tool.
>
>
> We hope you'll enjoy this release as much as we enjoyed making it.
>
> Fr?d?ric and Piers
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
>
>
> -- 
> Ben Reubenstein
> 303-947-0446
> http://www.x-cr.com
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071230/eb44762c/attachment-0001.html 

From kevwil at gmail.com  Sun Dec 30 17:27:58 2007
From: kevwil at gmail.com (Kevin Williams)
Date: Sun, 30 Dec 2007 15:27:58 -0700
Subject: [typo] Typo 5.0 "Eugene Atget" for Rails 2.0 is out
In-Reply-To: <B8C6E27E-35F5-497B-8C52-DD0DD483F434@de-villamil.com>
References: <6A99CBB7-626F-41AE-A6E9-07F0FAC0157B@de-villamil.com>
	<44c79a160712301315k22dd7a6bg53bc572bfb0d7011@mail.gmail.com>
	<B8C6E27E-35F5-497B-8C52-DD0DD483F434@de-villamil.com>
Message-ID: <683a886f0712301427w644cd3m4f30010e1e185f4f@mail.gmail.com>

And you should either:

1) remove any of the sidebars that were removed in 5.0 _before_ migrating to 5.0
2) install the sidebar plugins you need _before_ putting your new 5.0
blog on the 'net

The admin pages don't work if you reference sidebars which don't exist in 5.0.


On Dec 30, 2007 2:36 PM, Frederic de Villamil <frederic at de-villamil.com> wrote:
> Hi Ben,
>
> I'd say, do like before any migration, backup your blog and database, pray a
> bit...
> migrate should run like a charm if you 're upgrading from 4.x.
>
> As I've said in the release, we've removed most of the plugins so you'll
> have to reinstall some of them. It's explained in the release note.
>
> Regards,
> Fr?d?ric
>
>
>
> Le 30 d?c. 07 ? 22:15, Ben Reubenstein a ?crit :
>
>
>
> Hi Frederic ~
>
> Awesome work! I am excited to migrate.  For those of us upgrading, are there
> any special things we need to do besides pulling the latest version,
> migrating our database, and checking the sidebar items we use?  I apologize
> if this is addressed somewhere in the doc.
>
> ~ Ben
>
> On 12/30/07, Frederic de Villamil <frederic at de-villamil.com > wrote:
> >
> >
> > Typo 5.0 "Eug?ne Atget" finally finished after about 7 month of
> > making. This in an important release, stuffed with great new features,
> > loads of fixes and an incredible amount of polish. This may sound like
> > DHH introduction to Rails 2.0, and it does, because Typo 5.0 now runs
> > with Ruby on Rails 2.0 and won't run with anything else. That's the
> > reason of the major version change.
> >
> > Before jumping into the breakdown of features, I'd just like to extend
> > my deep gratitude towards everyone who helped make this release
> > possible. From Piers who made this possible to the (hundreds of)
> > contributors who got a patch applied to everyone on #typo who kept the
> > spirit alive. You can all be mighty proud of the role you played.
> > Cheers!
> >
> > ** Why Eug?ne Atget ? **
> >
> > I've wanted to give our releases a name for a while now, but we needed
> > to find a path we should follow from along the versions. Piers and I
> > are both photographers, and most of the visible work on Typo has been
> > done in Paris, which is a town Atget spent his life to picture. That's
> > the reason why his name came first when we had to choose one.
> >
> > ** Sidebars removal **
> >
> > As we announced earlier, we've decided to move most of the sidebars
> > plugins out of the trunk. There are many reasons why we think that,
> > out of some basic functionnalities, sidebars should be third party
> > softwares apart performances issues. We'll continue to maintain these
> > plugins anyway.
> >
> > If you're using one of the following plugins, be sure to install it,
> > or your blog may explode with lots of nasty error messages.
> >
> > ? AIM presence
> > ? Audioscrobbler
> > ? Backpack
> > ? Delicious
> > ? Flickr
> > ? 43 things
> > ? 43 places
> > ? Magnolia
> > ? Recent comments
> > ? Tada
> > ? Upcoming
> > ? Xbox
> >
> >
> > Plugins are now in our plugins repository
> (http://svn.typosphere.org/typo/plugins/
> > ), and installs like any rails plugin. Expect basic archives soon.
> >
> > ** Code refactoring **
> >
> > The immerged part of the iceberg, but not the least one, most of the
> > existing code has been rewriten. Typo was started when Rails was
> > young, very young, and lots of things were added to the framework
> > after we had to write them.
> >
> > The result is impressive in terms of performances, and bug fixing as
> > well.
> >
> > ** Admin refactoring**
> >
> > Admin has been entirely revamped, twice, between 4.1 and 5.0, and
> > we're quite proud of how it works now.
> >
> > The existing admin was the result of a scaffold during Typo early
> > days, and even though some improvements has been done, many things
> > were not as user friendly as they should have been. New admin now aims
> > at giving a clear view on the information, and eased access to the
> > most daily used functionnalities in your blogging life.
> >
> > ? Simple and avanced admin
> >
> > We now deliver the admin in 2 flavors, simple and advanced, because
> > everybody doesn't have the same need when it goes to blogging. We have
> > also splitted the settings in 2 places, to separate basic and advanced
> > settings.
> >
> > ? More localisation
> >
> > 4.1 introduced Typo internationalization, but no one noticed it as it
> > was hidden in the deep of environment.rb. You can now choose your
> > prefered language from the settings. We hope the community to support
> > the translation effort.
> >
> > ? Comments moderation
> >
> > Another hidden feature of 4.1 I think it's important to mention here
> > is default comment moderation. This is a stone in the build of a
> > better discussion management.
> >
> > ? Theme editor
> >
> > A theme editor was a missing piece in Typo admin, and it's now filled
> > with a basic, but usable editor. For now it allows you to edit your
> > layout and stylesheet. Views editing will come later.
> >
> > ? Dashboard
> >
> > We've also added a dashboard we plan to improve with time. It aims at
> > giving you a view on the latests activity on your Typo blog.
> >
> > ** Solving SEO issues**
> >
> > For long time now, Typo has been a pain to search engine optimisation,
> > mostly because most pages, out of single posts, had the same meta
> > title and description. That thing we never noticed before had nasty
> > effects when melted with Google duplicate content algorythm, which
> > even led some blogs to be banned from index. Expect some more
> > improvement in a near future.
> >
> > ** New themes**
> >
> > Azure which has been Typo default theme for a while now has been
> > removed from the core and won't be supported anymore. Standard issue
> > is now our new default theme, and we have introduced Dirtylicious as
> > well. Scribbish has been kept for backward compatibility as many blogs
> > are using it, starting Piers.
> >
> > Both themes were built above Scribbish markup and are thus hatom
> > compliant.
> >
> > ** Typo themes garden**
> >
> > I know this should be a community matter, and it may not have its
> > place on a release note, however I think it's important enough to
> > mention it. Every theme listed on <a href="
> http://www.dev411.com/typo/themes/
> > ">dev 411 Typo theme viewer</a> has been updated to support Typo 5.0,
> > and updated themes are already avaliable.
> >
> > We do think having a usable themes and plugins park is important, and
> > too many themes were only Typo 2.6.0 compatible. That's the reason why
> > we did the themes migration while finishing Typo 5.0, and we plan to
> > port even more non Typo themes in a near futur.
> >
> > ** And now ?**
> >
> > Now, we're going to have some rest while you're migrating and giving
> > your first feedbacks. We already have a new roadmap to Typo 5.1, which
> > contains
> >
> > ? Atom Publishing Protocol.
> > ? Admin feeds.
> > ? Working to make the admin interface talk APP.
> > ? Themes with helpers.
> > ? Customizing the Feedback state machine so different spam protection
> > engines can use different states.
> > ? Add users grants
> > ? OpenID consumption.
> > ? If we really have to, multiblogging...
> > ? Even more admin improvement.
> > ? Doc, doc and even more doc.
> > ? Plugin manager tool.
> >
> >
> > We hope you'll enjoy this release as much as we enjoyed making it.
> >
> > Fr?d?ric and Piers
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/typo-list
> >
>
>
>
> --
> Ben Reubenstein
> 303-947-0446
> http://www.x-cr.com _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>

From kevwil at gmail.com  Mon Dec 31 12:12:49 2007
From: kevwil at gmail.com (Kevin Williams)
Date: Mon, 31 Dec 2007 10:12:49 -0700
Subject: [typo] error in api when caching enabled
Message-ID: <683a886f0712310912h59759679p22ef0a44d447d93b@mail.gmail.com>

I'm not sure if I have something messed up with my install or if this
is actually a bug. I have Rails fragment caching enabled with the
memcache store, and it speeds up my blog rendering in browsers quite a
lot. I'm not sure if this is a Rails issue, a Memcache client issue,
or a Typo issue. (The memcache client plugin in Typo is quite
outdated, but the latest one doesn't have a 'delete_if' method
either.) Can anyone comment on it?



Processing BackendController#xmlrpc (for 67.41.118.40 at 2007-12-31
11:47:49) [POST]
  Parameters: {"action"=>"xmlrpc", "controller"=>"backend",
"methodCall"=>{"methodName"=>"metaWeblog.newPost",
"params"=>{"param"=>[{"value"=>{"string"=>"0"}},
{"value"=>{"string"=>"username"}}, {"value"=>{"string"=>"password"}},
{"value"=>{"struct"=>{"member"=>[{"name"=>"mt_keywords",
"value"=>{"string"=>"test"}}, {"name"=>"mt_convert_breaks",
"value"=>{"string"=>"textile"}}, {"name"=>"title",
"value"=>{"string"=>"Testing, Testing"}}, {"name"=>"categories",
"value"=>{"array"=>{"data"=>{"value"=>{"string"=>"General"}}}}},
{"name"=>"description", "value"=>{"string"=>"test from
TextMate\n\n"}}, {"name"=>"mt_text_more", "value"=>{"string"=>"\nif
you can read this, the API is working"}}]}}},
{"value"=>{"boolean"=>"1"}}]}}}
Casting of method parameters failed
HTTP-Error: 405 Method Not Allowed
HTTP-Error: 302 Found
Expiring #<Article:0x2aec802a7500>, with controller:
#<BackendController:0x2aec8031ee98>


NoMethodError (undefined method `delete_if' for <MemCache: 1 servers,
0 buckets, ns: nil, ro: false>:MemCache):
    /vendor/rails/actionpack/lib/action_controller/caching.rb:454:in
`delete_matched'
    /vendor/rails/actionpack/lib/action_controller/caching.rb:426:in
`expire_fragment'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:30:in
`benchmark'
    /vendor/rails/actionpack/lib/action_controller/caching.rb:425:in
`expire_fragment'
    /vendor/rails/actionpack/lib/action_controller/caching.rb:664:in `send!'
    /vendor/rails/actionpack/lib/action_controller/caching.rb:664:in
`method_missing'
    /app/models/blog_sweeper.rb:63:in `sweep_articles'
    /app/models/blog_sweeper.rb:41:in `expire_for'
    /app/models/blog_sweeper.rb:27:in `after_save'
    /vendor/rails/activerecord/lib/active_record/observer.rb:157:in `send'
    /vendor/rails/activerecord/lib/active_record/observer.rb:157:in `update'
    /usr/local/lib/ruby/1.8/observer.rb:185:in `notify_observers'
    /usr/local/lib/ruby/1.8/observer.rb:184:in `each'
    /usr/local/lib/ruby/1.8/observer.rb:184:in `notify_observers'
    /vendor/rails/activerecord/lib/active_record/callbacks.rb:338:in `notify'
    /vendor/rails/activerecord/lib/active_record/callbacks.rb:302:in `callback'
    /vendor/rails/activerecord/lib/active_record/callbacks.rb:214:in
`create_or_update'
    /vendor/rails/activerecord/lib/active_record/base.rb:1972:in
`save_without_validation'
    /vendor/rails/activerecord/lib/active_record/validations.rb:934:in
`save_without_transactions'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:108:in `save'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:66:in
`transaction'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:80:in
`transaction'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:100:in
`transaction'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:108:in `save'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:120:in
`rollback_active_record_state!'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:108:in `save'
    /app/apis/meta_weblog_service.rb:101:in `newPost'
    /vendor/actionwebservice/lib/action_web_service/invocation.rb:141:in `send'
    /vendor/actionwebservice/lib/action_web_service/invocation.rb:141:in
`perform_invocation_without_interception'
    /vendor/actionwebservice/lib/action_web_service/invocation.rb:135:in
`perform_invocation'
    /vendor/actionwebservice/lib/action_web_service/dispatcher/abstract.rb:46:in
`web_service_filtered_invoke'
    /vendor/actionwebservice/lib/action_web_service/dispatcher/abstract.rb:41:in
`web_service_delegated_invoke'
    /vendor/actionwebservice/lib/action_web_service/dispatcher/abstract.rb:60:in
`web_service_invoke'
    /vendor/actionwebservice/lib/action_web_service/dispatcher/abstract.rb:25:in
`invoke_web_service_request'
    /vendor/actionwebservice/lib/action_web_service/dispatcher/action_controller_dispatcher.rb:58:in
`dispatch_web_service_request'
    /usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
    /vendor/actionwebservice/lib/action_web_service/dispatcher/action_controller_dispatcher.rb:56:in
`dispatch_web_service_request'
    (eval):1:in `xmlrpc'
    /vendor/rails/actionpack/lib/action_controller/base.rb:1158:in `send'
    /vendor/rails/actionpack/lib/action_controller/base.rb:1158:in
`perform_action_without_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:697:in
`call_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:725:in
`run_before_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:664:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:664:in
`proxy_before_and_after_filter'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:483:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:483:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:722:in
`run_before_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:695:in
`call_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:689:in
`perform_action_without_benchmark'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in
`perform_action_without_rescue'
    /usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in
`perform_action_without_rescue'
    /vendor/rails/actionpack/lib/action_controller/rescue.rb:199:in
`perform_action_without_caching'
    /vendor/rails/actionpack/lib/action_controller/caching.rb:678:in
`perform_action'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in
`cache'
    /vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
    /vendor/rails/actionpack/lib/action_controller/caching.rb:677:in
`perform_action'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in
`process_without_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:685:in
`process_without_session_management_support'
    /vendor/rails/actionpack/lib/action_controller/session_management.rb:123:in
`process'
    /vendor/rails/actionpack/lib/action_controller/base.rb:388:in `process'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:171:in
`handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:115:in
`dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:126:in
`dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in `dispatch'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/rails.rb:76:in
`process'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/rails.rb:74:in
`synchronize'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/rails.rb:74:in
`process'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:159:in
`process_client'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:158:in `each'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:158:in
`process_client'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:285:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:285:in
`initialize'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:285:in `new'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:285:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:268:in
`initialize'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:268:in `new'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb:268:in `run'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/configurator.rb:282:in
`run'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/configurator.rb:281:in
`each'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/configurator.rb:281:in
`run'
    /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/mongrel_rails:136:in
`run'
    /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel/command.rb:212:in
`run'
    /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/mongrel_rails:252
    /usr/local/bin/mongrel_rails:19:in `load'
    /usr/local/bin/mongrel_rails:19

Sending data
Completed in 0.98284 (1 reqs/sec) | Rendering: 0.00008 (0%) | DB:
0.00000 (0%) | 200 OK [http://www.almostserio.us/backend/xmlrpc]

From benr at x-cr.com  Mon Dec 31 14:41:03 2007
From: benr at x-cr.com (Ben Reubenstein)
Date: Mon, 31 Dec 2007 12:41:03 -0700
Subject: [typo] Trunk DELETED my Blog folder
Message-ID: <44c79a160712311141w7f6f5c50g1e8f4bd4d405a42f@mail.gmail.com>

Hi ~
I backed everything up, svn upped (little past the 5.0 release), migrated,
and things were working.  Tried to login to admin, and THE ENTIRE DIRECTORY
MY BLOG WAS IN WAS DELETED.  I think the cache code has a serious bug.  My
history shows NO commands that would have altered the files.

~ Ben

-- 
Ben Reubenstein
303-947-0446
http://www.x-cr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071231/a678cb95/attachment.html 

From benr at x-cr.com  Mon Dec 31 15:03:15 2007
From: benr at x-cr.com (Ben Reubenstein)
Date: Mon, 31 Dec 2007 13:03:15 -0700
Subject: [typo] Trunk DELETED my Blog folder
In-Reply-To: <44c79a160712311141w7f6f5c50g1e8f4bd4d405a42f@mail.gmail.com>
References: <44c79a160712311141w7f6f5c50g1e8f4bd4d405a42f@mail.gmail.com>
Message-ID: <44c79a160712311203g74dcf1ddmc77f09a05b1bc6ca@mail.gmail.com>

It also DELETES /tmp if you are running as a privileged user (I was testing
something)... This is a confirmed bug via #typo added ticket to trac.

On 12/31/07, Ben Reubenstein <benr at x-cr.com> wrote:
>
> Hi ~
>
> I backed everything up, svn upped (little past the 5.0 release), migrated,
> and things were working.  Tried to login to admin, and THE ENTIRE DIRECTORY
> MY BLOG WAS IN WAS DELETED.  I think the cache code has a serious bug.  My
> history shows NO commands that would have altered the files.
>
>
> ~ Ben
>
> --
> Ben Reubenstein
> 303-947-0446
> http://www.x-cr.com
>



-- 
Ben Reubenstein
303-947-0446
http://www.x-cr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20071231/cb30bd32/attachment.html 

From murray at murmini.com  Mon Dec 31 22:21:33 2007
From: murray at murmini.com (Murray Wilson)
Date: Mon, 31 Dec 2007 22:21:33 -0500
Subject: [typo] Typo grinding to a halt
Message-ID: <41F04BB0-AA29-4F35-9A9B-2F41E2C9C796@murmini.com>

I have an active blog, http://www.murmini.com and it has been  
remarkably robust for a couple of years. Over the past few months it  
has become painfully slow. If your posting articles or comments or  
making any updates via the admin interface, it takes forever for it to  
accept changes. I am now receiving a lot of emails from people telling  
me they can't post comments as their browser times-out before it  
posts. I am hosting it on Rails Machine and the team there can't find  
what is wrong with it. I would be very very grateful of someone  
knowledgeable with the workings of Typo could contact me and suggest  
what we can do. Its a great program and has served me very well,  
however of recent it has become very frustrating. Thanks you in  
advance for any help you can provide. murray