From 1.0.0.rc2 to 1.1.1...

[Jean-Baptiste Bonnet]

Hi Gaspard,

I'm keeping an eye on your work and play with Zena once in a while.
Thanks for sharing!

I had a Zena 1.0.0.rc2 installed and running properly on my local computer.
I decided to try last available version which turns out to be 1.1.1
After installation I ran:
rake zena:init

which gave me the error:
can't activate tzinfo (= 0.3.26, runtime) for ["zena-1.1.1"], already
activated tzinfo-0.3.27 for []

OK, I reverted the gem tzinfo to version 0.3.26
sudo gem uninstall tzinfo -v 0.3.27

and after this zena 1.1.1 would start. Good!
but now when I start the webbrowser the first page displays without any
skin and when I refresh it throws the "We're sorry..." (error 500)

Any idea how to solve this? attached is the log from the terminal.
My Zena 1.0.0.rc2 is still running properly. Shall I uninstall it?

Thanks again!
JBB

[Gaspard Bucher]

Hi Jean-Baptiste,

I am not sure what you have done. To create a new 1.1.1 project, you need to:

$ gem install zena

$ zena new myapp

$ cd myapp

$ rake zena:init

To update an existing project:

$ gem install zena

=> edit config/environment.rb: config.gem 'zena', :version => '1.1.1'
$ rake zena:assets

$ rake zena:migrate

=============

From the logs, it seems the first error is related to request.env not finding "REQUEST_PATH" which is weird. I added some debugging to 1.1.2:

Can you try with this gem ? http://zenadmin.org/en/community/document842.gem (Zena 1.1.2 git head).

$ wget http://zenadmin.org/en/community/document842.gem -O zena-1.1.2.gem

$ gem install -l zena-1.1.2.gem

...

Gaspard

--
_______________________________________________
zena mailing list
ze...@zenadmin.org
http://zenadmin.org/en/community

--

                                                               Gaspard

[Gaspard Bucher]

PS: you also need to download zafu 0.8.4: http://zenadmin.org/en/community/document842.gem

$ wget http://zenadmin.org/en/community/document842.gem -O zafu-0.8.4.gem

--

                                                               Gaspard

[Jean-Baptiste Bonnet]

Hi Gaspard

I did create a new project, I did not try to update an existing project.
It seems you gave the same link (document842.gem) for both gems so installation of zena 1.1.2 cannot be achieved. Can you check the link for zafu 0.8.4 please?
Thanks for your help.

JB

[Gaspard Bucher]

On Sun, Jul 17, 2011 at 1:35 PM, Jean-Baptiste Bonnet <bonnet.je...@free.fr> wrote:

Hi Gaspard

I did create a new project, I did not try to update an existing project.
It seems you gave the same link (document842.gem) for both gems so installation of zena 1.1.2 cannot be achieved. Can you check the link for zafu 0.8.4 please?
Thanks for your help.

JB

 Ooops, here's the correct link:

$ wget http://zenadmin.org/en/community/document843.gem -O zafu-0.8.4.gem

[Jean-Baptiste Bonnet]

Hi again Gaspard

I tried the new 1.1.2 gem. Installation went good with zafu 0.8.4
Now I get the first page ("localhost") good with the normal skin.
Then any refresh of click on a link will throw the "We're sorry..." error
You'll find the terminal log attached if you can have a look...

Cheers!
JB

--

[Gaspard Bucher]

Found it !

You are running the server in development environment and this is a well known bug: 

* *development* environment (code reloading) breaks miserably with Zena

Just change the production database to point to the development one and use

$ script/server -e production

This annoying bug is hard to fix so we will only try to fix it when we port to rails 3.

Cheers !

Gaspard

PS: Just pasting some log elements for google

SystemStackError (stack level too deep):
  zena (1.1.2) bricks/acls/lib/bricks/acls.rb:73:in `get_skin_without_acls'

NoMethodError (undefined method `previously_last_modified=' for #<ActionView::Template:0xb737c6a4>):
  zafu (0.8.4) lib/zafu/controller_methods.rb:14:in `render_for_file'

--

                                                               Gaspard

[Jean-Baptiste Bonnet]

It works!

I finally preferred to run this command:

rake db:migrate RAILS_ENV="production"

which seemed simplier to me and ensures that the whole environment is set to production (so I can still use "zena rake:init" and the server starts automatically in development)

Thanks again!
JB