On Wed, Sep 14, 2011 at 11:44 AM, Roland Philibert rphilib...@aptina.comwrote:
I did try what you suggest as per:
sub thing_GET {
my ($self, $c) = @_;
$self-status_ok(
$c,
entity = $rs =
$c-model('DB::data)-search({},{result_class =
On Fri, Jun 10, 2011 at 11:10 AM, Jesse Sheidlower jes...@panix.com wrote:
ok( $mech_admin-tick('roles','2'), ticked the newwords_admin checkbox );
The only thing failing here is the _test_ in the first line of this. The
form is submitted correctly, and when I test the view page for this
I was surprised to discover that when a chained action throws a fatal
error, Catalyst continues executing the remaining actions in the
chain. Personally, I had assumed that each action in the chain could
depend on the preceeding actions having been executed successfully.
I've looked at the code
On Mon, Mar 7, 2011 at 6:20 PM, Ashley Pond V a...@sedition.com wrote:
2011/3/7 Adam Sjøgren a...@koldfront.dk:
On Mon, 7 Mar 2011 13:01:42 -0800, Ashley wrote:
What Ronald said + the #fragment is not passed along in the available
ENV with some servers and setups. In these cases it doesn't
On Tue, Mar 8, 2011 at 11:27 AM, Ashley Pond V a...@sedition.com wrote:
Well, the original message was:
How do I call uri_for_action and pass it the '#id' part? It's not an arg
and it's not part of the query string. This is called the fragment
identifier in the final URL.
uri_for_action
On Sun, Mar 6, 2011 at 6:46 AM, John M. Dlugosz wxju46g...@snkmail.com wrote:
On 3/6/2011 5:28 AM, Andrew Rodland andrew-at-cleverdomain.org
|Catalyst/Allow to home| wrote:
Or, since you know that what it generates *doesn't* have a fragment you could
always just $c-uri_for_action(...) .
On Mon, Mar 7, 2011 at 2:35 PM, Ashley Pond V a...@sedition.com wrote:
Using the fragment is probably a bad idea. It's not supported by all
servers so it can end up lost on the backend depending on your setup.
I can't figure out what you mean by this. This is a URL that will be
included in
On Mon, Mar 7, 2011 at 3:25 PM, John M. Dlugosz wxju46g...@snkmail.com wrote:
On 3/7/2011 1:35 PM, Ashley Pond V apv-at-sedition.com |Catalyst/Allow to
home| wrote:
Using the fragment is probably a bad idea. It's not supported by all
servers so it can end up lost on the backend depending on
On Wed, Mar 2, 2011 at 12:43 AM, John M. Dlugosz wxju46g...@snkmail.com wrote:
As for reaching for templates in CSS: Sure, you can break common lines into
different tags so you only specify a color once:
#this, #that, div p .theother { color: x }
but that doesn't help making (say) a
On Sat, Feb 12, 2011 at 3:45 AM, fREW Schmidt fri...@gmail.com wrote:
#1: is it correct that the svn user rjk is Ronald J Kimball
r...@linguist.dartmouth.edu ?
That email address is no longer active. Please use r...@tamias.net instead.
My github username is tamias.
I'm excited to have
On Fri, Nov 26, 2010 at 3:02 PM, Aristotle Pagaltzis pagalt...@gmx.de wrote:
* Ronald J Kimball rkimb...@pangeamedia.com [2010-11-23 18:00]:
REST principles dictate that I use POST, not GET, for these
requests. The same-origin policy forces me to use JSONP, which
can only make GET requests
On Mon, Nov 22, 2010 at 7:33 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 22 Nov 2010, at 18:28, Ronald J Kimball wrote:
It doesn't care what the request method is, as long as it's POST, PUT,
OPTIONS, or DELETE. ;)
No, it just doesn't care.
If I create Catalyst::Action::Deserialize
On Mon, Nov 22, 2010 at 3:12 PM, Aristotle Pagaltzis pagalt...@gmx.de wrote:
This is really, really, really bad. It’s roughly like modifying
a file system to be allow file deletion as a side effect of
opening a file. GET is supposed to be safe, that is, it should be
free of side effects that
On Mon, Nov 22, 2010 at 12:53 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 22 Nov 2010, at 17:44, Ronald J Kimball wrote:
This works for JSON requests (e.g. application/json), but not for
JSONP requests (e.g. text/javascript), because there is no
Catalyst::Action::Deserialize::JSONP. I
On Mon, Aug 2, 2010 at 5:56 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 29 Jul 2010, at 21:40, Ronald J Kimball wrote:
The only reference I found to this issue is a post to this mailing list
from 2007, which no one answered. Has anyone else experienced this problem?
Would a patch
I've recently been working on writing tests for a Catalyst app using
Test::WWW::Mechanize::
Catalyst. Unfortunately, I've hit a snag; Catalyst::Test's local_request()
method (which is used by Test::WWW::Mechanize::Catalyst) does not parse the
base href=... tag in the content of the response.
toppe...@gmail.com wrote:
Then, I tried setting $page in my controllers, hoping to have the
submenu switches/menu.tt2, etc included.
However, when I load the page, I get the following error:
Couldn't render template file error - /menu.tt2: absolute paths are
not allowed (set ABSOLUTE option)
According to the whois record, it appears the domain has already been
renewed:
Domain ID:D108520399-LROR
Domain Name:CATALYSTFRAMEWORK.ORG
Created On:14-Nov-2005 14:17:32 UTC
Last Updated On:19-Nov-2007 14:17:38 UTC
Expiration Date:14-Nov-2008 14:17:32 UTC
It is stupid that they apparently
18 matches
Mail list logo
