[ANN] Release of Typo 5.1 "Cartier Bresson"

Hello,

After a long time of development, Typo 5.1 “Cartier-Bresson” was
released on monday July the 21th at around 8PM GMT and can be
considered as a major Typo Version.

It contains :

** Multiple users and roles.

This point actually makes Typo 5.1 a major version. This release
introduces 3 roles, coming along with various privileges :
– Administrator, who owns full administrative and publishing power.
– Publisher, who owns full publishing power on his own contents.
– Contributors, who only have the right to login and edit their profile.

There is now an option to allow new users to register by themselves or
not. If not, the administrator will just have to add them himself in
the admin.

** Improved admin

The admin has been heavily refactored to be lighter, easier to use,
and offer more capabilities.
– You can now save your posts as drafts. Drafts now appear in a
separate area of your administration to separarte them from offline
posts.
– New editing interface.
– Tag autocompletion.
– A new dashboard that makes daily administration easier.
– Save as draft capabilities
– Autosave capabilities (only with simple visual editor)
– Revamped UI
– Many more…

** New default theme

After leaving the too much long used Azure theme for some templates
found on open source design websites, we realized Typo needed a new
default theme. We asked O2Source a French web Agency involved in many
free and open source templates, and they came up with Typographic.

We wanted something new, far from the classic white and blue fixed
width wordpressish thing, something with its own personnality, that
would take the whole screen and adapt many resolutions, and we’ve been
quite delighted with what Hélène produced.

** Come back of the gem and the installer

After fixing numerous bugs happening with Typo installed through our
installer, we were able to provide the gem again, making Typo
installation easier than ever.

MySQL is now the default database and SQLITE dependency has been
removed.

** Lots of code improvement and refactoring

The code have been improved and refactored, maing Typo lighter than
ever. This is a guarantee of less errors.

** New migrators

We’ve included new migrators, allowing easy import from Wordpress and
Dotclear 1.2 and 2. Typepad and Textpattern may follow soon.

** New site with up to date documentation

The bugtracker has been moved from Trac to Redmine, so has the
documentation, which has been rewriten in many ways. Access to the doc
has also been made easier by merging redmine.typosphere.org with
trac.typosphere.org.

Lots of bugfixes, too much to say here.

Frédéric de Villamil
[email protected] tel: +33 (0)6 62 19 1337
http://fredericdevillamil.com Typo : http://typosphere.org

Frédéric, Piers & contributors: congratulations! You do an amazing work,
thanks!

Cheers, Sazima

On Mon, Jul 21, 2008 at 3:13 PM, de Villamil Frédéric <

Le 21 juil. 08 à 20:35, joy ride a écrit :

released on monday July the 21th at around 8PM GMT and can be
– Publisher, who owns full publishing power on his own contents.
The admin has been heavily refactored to be lighter, easier to use,
– Many more…
We wanted something new, far from the classic white and blue fixed

We’ve included new migrators, allowing easy import from Wordpress

Thank you,
having forgotten to commit something important (like a bug in the
autosave) I did a second shot and released 5.1.1. I’m sorry for the
few people who have already upgraded :confused:

I know I’ve been hard on the tool, but let me say here that I am very
excited about upgrading to this new version, and am eager to give it a
go!

Chet F.
Mobile 713-376-9252

Hello Frédéric,

I wish I could say Rubygems was giving 5.1.1, I told it gem install
typo -v 5.1.1 and it installed 5.0… admin said 4.1.1

So I went to typosphere to try and find a tarball download, and well I
couldn’t find one. Tried to find the svn url or something, well I
couldn’t find that either… so I trudged around and checked out
trunk, it says it’s 5.1.1 so fine and dandy, created a new database,
told it to migrate, goto the admin signed up.

I can say it was nice seeing it actually cared about password length,
having the rich text editor (fck editor) is rather nice.

However here are some things I find to be problematic,

size, wow…

damm 5380 7.3 4.8 203532 99020 pts/3 Sl+ 17:46 0:08 ruby
script/server

now I’ll admit I am on 64-bit and I should expect some larger sizes…
but yikes.

The default theme, it’s nice to see a really unique theme. But can we
have the same thing with pastel blues? the peach is just a bit much
for me. But there’s other themes.

rake spec

Test::Unit::AssertionFailedError in ‘BackendController
test_meta_weblog_new_post’
<Mon Jul 21 07:00:00 UTC 2008> expected but was
<Tue Jul 22 07:00:00 UTC 2008>.
/usr/lib64/ruby/1.8/test/unit/assertions.rb:48:in assert_block' /usr/lib64/ruby/1.8/test/unit/assertions.rb:495:in _wrap_assertion’
/usr/lib64/ruby/1.8/test/unit/assertions.rb:46:in assert_block' /usr/lib64/ruby/1.8/test/unit/assertions.rb:83:in assert_equal’
./spec/controllers/backend_controller_spec.rb:182:in
test_meta_weblog_new_post' /usr/lib64/ruby/1.8/timeout.rb:53:in timeout’

Test::Unit::AssertionFailedError in ‘BackendController
test_meta_weblog_edit_post’
<Mon Jul 21 07:00:00 UTC 2008> expected but was
<Tue Jul 22 07:00:00 UTC 2008>.
/usr/lib64/ruby/1.8/test/unit/assertions.rb:48:in assert_block' /usr/lib64/ruby/1.8/test/unit/assertions.rb:495:in _wrap_assertion’
/usr/lib64/ruby/1.8/test/unit/assertions.rb:46:in assert_block' /usr/lib64/ruby/1.8/test/unit/assertions.rb:83:in assert_equal’
./spec/controllers/backend_controller_spec.rb:145:in
test_meta_weblog_edit_post' /usr/lib64/ruby/1.8/timeout.rb:53:in timeout’

Finished in 22.50511 seconds

464 examples, 2 failures

Figured i’d say it, try it…

Thanks,

Scott

On Jul 21, 2008, at 11:13 AM, de Villamil Frédéric wrote:

– A new dashboard that makes daily administration easier.
default theme. We asked O2Source a French web Agency involved in

ever. This is a guarantee of less errors.
doc has also been made easier by merging redmine.typosphere.org with
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

!DSPAM:4884d310117641804284693!

Le 22 juil. 08 à 03:16, Scott L. a écrit :

now I’ll admit I am on 64-bit and I should expect some larger
test_meta_weblog_new_post’
2)
/usr/lib64/ruby/1.8/timeout.rb:53:in `timeout’

Hi Scott,

Thanks for feedback.

– For rubyforge issue, it may take time to mirror the new version
amongst servers.

– Finding Typo : I’ve added a link on the homepage of the site. Should
have done that before.

– Memory : if I remember correctly, 64bits means just twice much ram
than 32.

– Default theme : personnalization through a color picker is part of
the 5.2 theme editor improvements I plan to set up. Temporary roadmap
is at http://typosphere.org/projects/roadmap/typo

– Tests. I don’t know what to say because I can’t have the gem built
without tests passing, and I have it. And I just ran tests once again.
So… The only thing I see should be a timezone difference between
your computer and rails passing the tests with tests started too close
to midnight. If someone knows, I’d be really interested.

Le 22 juil. 08 à 16:23, Chris D. a écrit :

Chris

/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/filters.rb:689:in
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
mongrel/rails.rb:74:in process' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb: configurator.rb:282:in run’
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/
27:in `gem_original_require’
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
10:18:17) [GET]
Redirected to http://gridengine.info/articles.atom
Completed in 0.00161 (622 reqs/sec) | DB: 0.00000 (0%) | 301 Moved
Permanently [http://gridengine.info/xml/atom/feed.xml]

Hi Chris,

did you restart your Typo application after upgrading ? Did you also
run rake db:migrate to upgrade your database ? It’s an important step
since you need to get your database migrated to log in.

Cheers,
Frédéric


Frédéric de Villamil
[email protected] tel: +33 (0)6 62 19 1337
http://fredericdevillamil.com Typo : http://typosphere.org

Never mind. All set.

After the tgz update failed I tried the gem install method. After
updating all gems and installing new dependencies that were apparently
not needed with my 5.0.3 install (not mentioned on website from what I
can tell) including ‘linecache’ and ‘columnize’ I’ve got things
working in a fresh directory.

-Chris

Hi,

I’m hitting a snag with the upgrade. The gem installed and ‘typo
install’ went right along, updated the database, and now rake
db:migrate returns without work to do, so I think things are mostly
in place, however, if I try to access any pages, I get a ‘Signup’
box. If I try to access /admin, I get something like:

Processing DashboardController#index (for 216.107.222.222 at
2008-07-23 03:14:51) [GET]
Session ID: 7bc4e03f41d1adf87a16971a648a7f49
Parameters: {“action”=>“index”, “controller”=>“admin/dashboard”}

========
NameError (undefined local variable or method current_user' for #<Admin::DashboardController:0xb6b5e080>): /lib/login_system.rb:47:inlogin_required’
/vendor/rails/actionpack/lib/action_controller/filters.rb:469:in
send!' /vendor/rails/actionpack/lib/action_controller/filters.rb:469:incall’
/vendor/rails/actionpack/lib/action_controller/filters.rb:441:in
run' /vendor/rails/actionpack/lib/action_controller/filters.rb:716:inrun_before_filters’
/vendor/rails/actionpack/lib/action_controller/filters.rb:695:in
call_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:689:inperform_action_without_benchmark’
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
68:in perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:inmeasure’
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
68:in perform_action_without_rescue' /vendor/rails/actionpack/lib/action_controller/rescue.rb:199:inperform_action_without_caching’
/vendor/rails/actionpack/lib/action_controller/caching.rb:678:in
passenger_orig_perform_action' /vendor/rails/activerecord/lib/active_record/connection_adapters/ abstract/query_cache.rb:33:incache’
/vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in
cache' /vendor/rails/actionpack/lib/action_controller/caching.rb:677:inpassenger_orig_perform_action’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/railz/
request_handler.rb:53:in perform_action' /vendor/rails/actionpack/lib/action_controller/base.rb:524:insend’
/vendor/rails/actionpack/lib/action_controller/base.rb:524:in
process_without_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:685:inprocess_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:inprocess’
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
171:in handle_request' /vendor/rails/actionpack/lib/action_controller/dispatcher.rb: 115:indispatch’
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:
126:in dispatch_cgi' /vendor/rails/actionpack/lib/action_controller/dispatcher.rb: 9:indispatch’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/railz/
request_handler.rb:38:in process_request' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ abstract_request_handler.rb:163:inmain_loop’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/railz/
application_spawner.rb:307:in start_request_handler' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/railz/ application_spawner.rb:144:inspawn_application!’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
utils.rb:165:in safe_fork' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ utils.rb:163:infork’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
utils.rb:163:in safe_fork' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/railz/ application_spawner.rb:130:inspawn_application!’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
utils.rb:165:in safe_fork' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ utils.rb:163:infork’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
utils.rb:163:in safe_fork' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/railz/ application_spawner.rb:129:inspawn_application!’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
spawn_manager.rb:236:in spawn_rails_application' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ spawn_manager.rb:219:insynchronize’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
spawn_manager.rb:219:in spawn_rails_application' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ spawn_manager.rb:122:inspawn_application’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
spawn_manager.rb:253:in handle_spawn_application' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ abstract_server.rb:317:insend
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/
abstract_server.rb:317:in main_loop' /usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/lib/passenger/ abstract_server.rb:168:instart_synchronously’
/usr/lib/ruby/gems/1.8/gems/passenger-2.0.2/bin/passenger-spawn-
server:46

Rendering /opt/typo/example.com-bill/public/500.html (500 Internal
Server Error)

in the logs. If I try to sign up for an account, I get a mail, but
it refers to ‘My Shiny Weblog!’ - I think mails used to have the real
blog name in there.

The database connection is up:
6341 ? Ss 0:00 postgres: typo typo_mcgonigle.us-bill
127.0.0.1(33855) idle

and the real data is in the tables.

Suggestions on where to look next?

Thanks,
-Bill

Hello,

I’m updating from 5.0.3 using the .tgz archive. The rake migration
process went smoothly and the blog renders articles but I can’t login
as admin to complete the migration:

Any hints on this update? Out of date gems or something?

Regards,
Chris

I’m also having this problem after using the install script to upgrade
from 5.03. I havent found much info on a fix. I dont want to do a fresh
install as my client spent a while getting the theme looking right!

Where is current_user supposed to be getting set?

If anyone has any ideas would be very much appreciated…

Thanks
Adam

Bill McGonigle wrote:

Hi,

I’m hitting a snag with the upgrade. The gem installed and ‘typo
install’ went right along, updated the database, and now rake
db:migrate returns without work to do, so I think things are mostly
in place, however, if I try to access any pages, I get a ‘Signup’
box. If I try to access /admin, I get something like:

Processing DashboardController#index (for 216.107.222.222 at
2008-07-23 03:14:51) [GET]
Session ID: 7bc4e03f41d1adf87a16971a648a7f49
Parameters: {“action”=>“index”, “controller”=>“admin/dashboard”}

========
NameError (undefined local variable or method current_user' for #<Admin::DashboardController:0xb6b5e080>): /lib/login_system.rb:47:inlogin_required’
/vendor/rails/actionpack/lib/action_controller/filters.rb:469:in
send!' /vendor/rails/actionpack/lib/action_controller/filters.rb:469:incall’
/vendor/rails/actionpack/lib/action_controller/filters.rb:441:in
run' /vendor/rails/actionpack/lib/action_controller/filters.rb:716:inrun_before_filters’
/vendor/rails/actionpack/lib/action_controller/filters.rb:695:in

Rendering /opt/typo/example.com-bill/public/500.html (500 Internal
Server Error)

in the logs. If I try to sign up for an account, I get a mail, but
it refers to ‘My Shiny Weblog!’ - I think mails used to have the real
blog name in there.

The database connection is up:
6341 ? Ss 0:00 postgres: typo typo_mcgonigle.us-bill
127.0.0.1(33855) idle

and the real data is in the tables.

Suggestions on where to look next?

Thanks,
-Bill

Adam W. wrote:

I’m also having this problem after using the install script to upgrade
from 5.03. I havent found much info on a fix. I dont want to do a fresh
install as my client spent a while getting the theme looking right!

Where is current_user supposed to be getting set?

current_user is save in session. So have you clear all session after
upgrading ?

rake db:sessions:clear

Adam W. wrote:

Hi Cyril

Thanks for your suggestion. However, I just tried doing rake
db:sessions:clear, also with RAILS_ENV=production, restarting mongrel
afterwards, but it seems to make no difference.

Is there anything else it might be?

Have you check this issue ?

http://typosphere.org/issues/show/1258

Hi Cyril

Thanks for your suggestion. However, I just tried doing rake
db:sessions:clear, also with RAILS_ENV=production, restarting mongrel
afterwards, but it seems to make no difference.

Is there anything else it might be?

Cyril M. wrote:

Adam W. wrote:

I’m also having this problem after using the install script to upgrade
from 5.03. I havent found much info on a fix. I dont want to do a fresh
install as my client spent a while getting the theme looking right!

Where is current_user supposed to be getting set?

current_user is save in session. So have you clear all session after
upgrading ?

rake db:sessions:clear

Cyril M. wrote:

Adam W. wrote:

Hi Cyril

Thanks for your suggestion. However, I just tried doing rake
db:sessions:clear, also with RAILS_ENV=production, restarting mongrel
afterwards, but it seems to make no difference.

Is there anything else it might be?

Have you check this issue ?

http://typosphere.org/issues/show/1258

Yes I checked that yesterday, and froze rails 2.02 into the typo vendor
folder.
So I still need to set the version in environment.rb?

Cyril M. wrote:

Adam W. wrote:

Is there anything else it might be?

Use ruby 1.8.6 too, not 1.8.7

Can you paste a log ?

You can come in IRC to explain with direct and several people.


Cyril M.
http://blog.shingara.fr

OK I have Ruby 1.8.5 on my server.
If I upgrade to 1.8.6 should this fix the issue?

Adam W. wrote:

Is there anything else it might be?

Use ruby 1.8.6 too, not 1.8.7

Can you paste a log ?

You can come in IRC to explain with direct and several people.


Cyril M.

Adam W. wrote:

Can you paste a log ?

Maybe. I don’t sure. But Typo-5.1.3 doesn’t support ruby 1.8.5 in README


Cyril M.

OK I am back to this problem … after quite a few months! My client who
I set up the blog for was not using it, and now they want to the problem
has come back to haunt me…

If anyone knows of a fix that does not involve upgrading Ruby (I am
scared of breaking one of my other sites) that would be really
appreciated!!

Current Typo version: 5.1.3
Ruby version: 1.8.5

Would the new 5.3 version fix this issue? Can anyone confirm if
upgrading to Ruby1.9 would fix this? I have installed ruby1.9 on the
server just need to switch the alias but I need to thoroughly check my
other sites for compatibility before I do this.

Regarding Typo bugs, It seems that at least ‘current_user’ and
‘logged_in?’ are not available to accounts_controller. I added a check
for current_user before line 10 with respond_to?(‘current_user’) just to
see how far it got after, and it then trips up on ‘logged_in?’

If anyone has any info I would be very thankful.

Regards
Adam

Cyril M. wrote:

Adam W. wrote:

Can you paste a log ?

Maybe. I don’t sure. But Typo-5.1.3 doesn’t support ruby 1.8.5 in README


Cyril M.
http://blog.shingara.fr