RE: [Catalyst] Problem storing session data

2008-04-01 Thread Peter Sørensen
Thanks for the suggestion. I tried but this does not solve my problem. I'm a little uncertain on where to set theese values. I've done this: _PACKAGE__-config-{session = { storage = '/tmp/session'.$$, cache_size = '10m',

[Catalyst] Nested calls to model does not work?

2008-04-01 Thread Alex Povolotsky
Sorry for resending, looks like everyone able to answer overlooked this message. I'm researching the problem without much success. Hello! I've experienced strange problem displaying data. Minimal test case is fairly big, I can attach it here, but will try to extract most important information.

[Catalyst] many_to_many filling

2008-04-01 Thread Alex Povolotsky
defaults_from_model does only default settings. To fill select/checkbox group/whatever else, one must add to .yml file: db: model: (name-of-your-Catalyst-model) resultset: (name-of-proper-resultset) label_column: (column to put into label) It is not documented anywhere but can be extracted

Re: [Catalyst] Problem storing session data

2008-04-01 Thread Bill Moseley
On Tue, Apr 01, 2008 at 10:17:25AM +0200, Peter Sørensen wrote: _PACKAGE__-config-{session = { storage = '/tmp/session'.$$, cache_size = '10m', page_size = '256k', expires

Re: [Catalyst] Problem storing session data

2008-04-01 Thread Peter Karman
On 04/01/2008 03:17 AM, Peter Sørensen wrote: Thanks for the suggestion. I tried but this does not solve my problem. I'm a little uncertain on where to set theese values. I've done this: _PACKAGE__-config-{session = { storage = '/tmp/session'.$$,

Re: [Catalyst] Re: Catalyst-Manual-FAQ Addition

2008-04-01 Thread Russell Jurney
I just do what castaway tells me. Where do you suggest this go? Russell Jurney [EMAIL PROTECTED] On Mar 31, 2008, at 2:09 PM, Aristotle Pagaltzis wrote: * Russell Jurney [EMAIL PROTECTED] [2008-03-31 14:30]: I discovered that 'call' is a reserved word for Catalyst controllers, and any

[Catalyst] X-Forwarded-For

2008-04-01 Thread Bill Moseley
C::Engine::Apache does this: # If we are running as a backend server, the user will always appear # as 127.0.0.1. Select the most recent upstream IP (last in the list) my ($ip) = $headers-{'X-Forwarded-For'} =~ /([^,\s]+)$/; $c-request-address( $ip ); Why the most recent? If

Re: [Catalyst] X-Forwarded-For

2008-04-01 Thread Andy Grundman
On Apr 1, 2008, at 11:17 PM, Bill Moseley wrote: C::Engine::Apache does this: # If we are running as a backend server, the user will always appear # as 127.0.0.1. Select the most recent upstream IP (last in the list) my ($ip) = $headers-{'X-Forwarded-For'} =~ /([^,\s]+)$/;

Re: [Catalyst] X-Forwarded-For

2008-04-01 Thread Bill Moseley
On Tue, Apr 01, 2008 at 11:38:15PM -0400, Andy Grundman wrote: When using X-Forwarded-For you cannot trust any value that is not added by your own upstream proxy, so we only want to use the last value in the list. Ah, right. In this case I've got more than one proxy which that code