From: "Tomas Doran"
On 9 Jan 2010, at 20:35, Octavian Rasnita wrote:
(Maybe the docs could be a little more clear, because this is a
great feature.)
Please supply a doc patch?
Cheers
t0m
I was sure you will say this. :-)
I attached a unified diff for the version 5.80017.
I hope it is
I'm happy to announce the next release of Catalyst-Runtime (5.80017).
This release mainly cures all issues reported with upgraded scripts (or
applications generated with the latest release of Catalyst::Devel) and
makes Catalyst compatible with upcomming versions of Moose.
This release also starte
On 9 Jan 2010, at 20:35, Octavian Rasnita wrote:
(Maybe the docs could be a little more clear, because this is a
great feature.)
Please supply a doc patch?
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin
2010/1/9 Alex Povolotsky :
> Hello!
>
> I'm working on a (more or less) flexible system with plugins should be
> installed just like controllers; some basic information about them
> (particulary, numerical id) must be kept in database.
>
> Plugins should be handle some queries in /admin/service/$se
Hello!
I'm working on a (more or less) flexible system with plugins should be
installed just like controllers; some basic information about them
(particulary, numerical id) must be kept in database.
Plugins should be handle some queries in /admin/service/$servicename
I'd like to put 'smart l
From: "Aristotle Pagaltzis"
* Octavian Rasnita [2010-01-09 15:20]:
It could be helpful to have shortcuts for the second way of
creating URLS, something like...
c.url_query('controller_name', 'action_name', param1, param2)
Already exists, although it uses the internal path instead of
separat
* Octavian Rasnita [2010-01-09 15:20]:
> It could be helpful to have shortcuts for the second way of
> creating URLS, something like...
>
> c.url_query('controller_name', 'action_name', param1, param2)
Already exists, although it uses the internal path instead of
separately passing the controller
On Sat, Jan 9, 2010 at 8:47 AM, Kiffin Gish wrote:
> SMTP isn't even making it out the front door, e.g. no requests are being
> generated nor showing up via wireshark.
>
> Any other ideas, friend?
>
> On Sat, 2010-01-09 at 16:05 +, Tomas Doran wrote:
>> On 9 Jan 2010, at 15:53, Kiffin Gish wro
SMTP isn't even making it out the front door, e.g. no requests are being
generated nor showing up via wireshark.
Any other ideas, friend?
On Sat, 2010-01-09 at 16:05 +, Tomas Doran wrote:
> On 9 Jan 2010, at 15:53, Kiffin Gish wrote:
>
> > Can't send data
>
> That error is caused when you m
On 6 Jan 2010, at 06:13, Jim Dread wrote:
I tried getting some argv in there by giving arguments to the server
script, but it didn't fix it. So I edited HTTP.pm to this:
#exec $^X, $0, @{ $options->{argv} || [] };
And now it restarts okay when HUPed. Did I do something wrong or is
On 9 Jan 2010, at 15:53, Kiffin Gish wrote:
Can't send data
That error is caused when you make an SMTP connection, but your mail
server rejects the message for some reason.
Use wireshark & tcpdump to work out what's actually going down the
wire between your app and the mail server?
Ch
Been struggling most of the afternoon trying to figure this out but to
no avail, hopefully someone can help me.
For registration of new users I've decided to expand upon the MojoMojo
example, using Catalyst::View::Email::Template. Trying to send email
results in the following error:
The following
On 5 Jan 2010, at 12:28, Emmanuel Quevillon wrote:
On 01/05/2010 12:51 PM, Андрей П. Ковбович wrote:
Hi,
try this option: --detach
Hi,
That solved my problem. But it could be good to change it from the
help message which is still :
This is a regression and has been fixed in trunk.
I
On 9 Jan 2010, at 11:35, Kiffin Gish wrote:
Yes you're right, I overlooked the presence namespace::autoclean at
the
top.
Checked out the documentation but don't quite understand the
difference
with namespace::clean. Is the latter the same as auto except then more
explicit in that only nam
From: "Kiffin Gish"
I noticed that in certain examples depending on the coder, sometimes the
following format is used:
c.uri_for(c.controller('Users').action_for('list'))
and other times this fomat:
c.uri_for('/users/list')
What's the difference and is there an advantage of using one
I noticed that in certain examples depending on the coder, sometimes the
following format is used:
c.uri_for(c.controller('Users').action_for('list'))
and other times this fomat:
c.uri_for('/users/list')
What's the difference and is there an advantage of using one or the
other?
Thanks
Yes you're right, I overlooked the presence namespace::autoclean at the
top.
Checked out the documentation but don't quite understand the difference
with namespace::clean. Is the latter the same as auto except then more
explicit in that only named -except methods aren't cleaned out?
Also, when us
17 matches
Mail list logo
