Skip Menu |

This queue is for tickets about the Catalyst-TraitFor-Component-ConfigPerSite CPAN distribution.

Report information
The Basics
Id: 78089
Status: open
Worked: 50 min
Priority: 0/
Queue: Catalyst-TraitFor-Component-ConfigPerSite

People
Owner: TEEJAY [...] cpan.org
Requestors: nick [...] webcraftcs.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in:
  • 0.05
  • 0.06
  • 0.07
  • 0.08
  • 0.09
  • 0.10
Fixed in: (no value)

Attachments
Catalyst-TraitFor-Component-ConfigPerSite-0.10_nick.tar.gz



Subject: Additional site config parameters are not accessible
Date: Thu, 28 Jun 2012 10:40:19 +0100
To: bug-Catalyst-TraitFor-Component-ConfigPerSite [...] rt.cpan.org
From: Nick <nick [...] webcraftcs.com>
The Catalyst-TraitFor-Component-ConfigPerSite package does not allow access to config parameters other than the specific ones required for the database connection (in Model::DB) or view (in View::TT). Access to additional parameters is desired to fully utilise this package. Specifically, individual site file paths for use by DBIx::Class::InflateColumn::FS would be useful to be able to keep site files in segregated areas. e.g. <Model::DB> schema_class default::Schema <connect_info> dsn dbi:mysql:defaultdb user xxxx password xxxx </connect_info> file_path /path/to/site/default </Model::DB> Thank you
Hi Nick, Can you post a bit more example code - i.e. modify the config/code in the tests included in the distribution, as I can't see how to replicate it without a bit more context/code to implement the function you're calling against the schema. The configuration all seems to be correctly copied at the model layer - should I also be throwing it in the dbic schema connect call too? I can't make much more progress without either some more pointers in the code or dedicated a large chunk of my weekend (which won't be likely in the short term) Thanks, Aaron
On Thu Jun 28 05:40:32 2012, nick@webcraftcs.com wrote: Show quoted text
> > The Catalyst-TraitFor-Component-ConfigPerSite package does not allow > access to config parameters other than the specific ones required for > the database connection (in Model::DB) or view (in View::TT).
Looking again at your original catalyst list post I can see that the problem is due to Catalyst::TraitFor::Model::DBIC::Schema::SchemaProxy loading configuration at start/compile time. I'll see if I can find a work around and/or provide an easy alternative in ConfigPerSite.
Subject: Re: [rt.cpan.org #78089] Additional site config parameters are not accessible
Date: Wed, 18 Jul 2012 17:27:41 +0100
To: bug-Catalyst-TraitFor-Component-ConfigPerSite [...] rt.cpan.org
From: Nick <nick [...] webcraftcs.com>
Hi Aaron, Apologies for the lack of contact from me which was due to an urgent application deployment and subsequent server failure, but I'm around now and keen to help (if I can!). I was using TraitFor/SchemaProxy so that I could move the file_path out of the Model and ultimately into the config files. I may have overly complicated things and suspect I can simplify it slightly.....will report back shortly... Nick On 13/07/12 21:08, Aaron James Trevena via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=78089 > > > On Thu Jun 28 05:40:32 2012, nick@webcraftcs.com wrote:
>> The Catalyst-TraitFor-Component-ConfigPerSite package does not allow >> access to config parameters other than the specific ones required for >> the database connection (in Model::DB) or view (in View::TT).
> Looking again at your original catalyst list post I can see that the > problem is due to Catalyst::TraitFor::Model::DBIC::Schema::SchemaProxy > loading configuration at start/compile time. > > I'll see if I can find a work around and/or provide an easy alternative > in ConfigPerSite. > >
Subject: Re: [rt.cpan.org #78089] Additional site config parameters are not accessible
Date: Thu, 19 Jul 2012 13:12:02 +0100
To: bug-Catalyst-TraitFor-Component-ConfigPerSite [...] rt.cpan.org
From: Nick <nick [...] webcraftcs.com>
Hi Aaron, I've spent some time this morning adding the relevant bits to the test directory to at least demonstrate the file_path/SchemaProxy issue. I have attached a zip file with everything in and you will notice some modified files including a couple of additional test files with a suffix "_nick.t". The test databases have also been modified. Hopefully this will be of some use although I suspect you may have done this much already by now! Although it's more a conflict between SchemaProxy and ConfigPerSite than a bug, I do believe that ConfigPerSite would be enhanced by the ability to specify different site file paths (in the config file) for the inflate_columns_fs feature. Thanks Nick On 13/07/12 21:08, Aaron James Trevena via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=78089 > > > On Thu Jun 28 05:40:32 2012, nick@webcraftcs.com wrote:
>> The Catalyst-TraitFor-Component-ConfigPerSite package does not allow >> access to config parameters other than the specific ones required for >> the database connection (in Model::DB) or view (in View::TT).
> Looking again at your original catalyst list post I can see that the > problem is due to Catalyst::TraitFor::Model::DBIC::Schema::SchemaProxy > loading configuration at start/compile time. > > I'll see if I can find a work around and/or provide an easy alternative > in ConfigPerSite. > >

Message body not shown because it is not plain text.