Looks like it is a problem with the debug printing code or the some
unescape code somewhere. That is the proper escape for +.
Yes. and the problem is Catalyst is unescaping it to early, so its
seeing it as a literal +, which then gets converted to a space according
to the HTTP RFC. It
quote who=[EMAIL PROTECTED]
That's what uri_for is already doing (I forgot to mention I'd checked
already).
uri_for:
http://myserver.com/blah/?username=first.last%2Bme%40gmail.com
URI::Escape:
perl -MURI::Escape -e print uri_escape('[EMAIL PROTECTED]');
Gavin Henry wrote:
quote who=[EMAIL PROTECTED]
That's what uri_for is already doing (I forgot to mention I'd checked
already).
uri_for:
http://myserver.com/blah/?username=first.last%2Bme%40gmail.com
I haven't looked into this at all, but try using a chained action
instead. I think
This is only slightly modified code from the tutorial on CPAN. I
probably mis-copied something and hence my problem, but I can't seem
to figure out what.
I have a a controller called Campaigns.pm with the delete method
below (comments and empty lines removed):
124 sub delete : Local {
126 my
I tested but couldn't reproduce. So I wouldn't say this is a Cat bug.
% catalyst.pl TestApp
% cd TestApp
% vi lib/TestApp/Controller/Root.pm
sub default : Private {
my ( $self, $c ) = @_;
# Hello World
$c-response-body(Hello . ($c-req-param('username') || (default)));
}
%
Well, I found a solution to my problem. I'm not sure it is the most
elegant, but here goes:
I figured that just putting the proper cascade logic into my actual
DB schema would fix things, and it does. I changed my table
definition to:
84 CREATE TABLE `campaign_clients` (
85 `campaign_id`
I wonder if this is similar to something bug I saw a few months ago.
I tried to pass a GET url into a TT2 field but the question mark in the url
kept getting url-encoded to %3F. I was wondering if it was a Unicode
problem, but it may have been wrong url_for syntax.
Here is a snippet from the old
