Mark,
Thanks. Actually that was helpful. I just didn't know if there was a
C::A::P::Upload in the offering. I did look at C::Uploader, but need to
look again. I know that is outside the purview of this list serve, but
would be curious to see a working example.
Brad
On 2005-12-30, Brad Cathey
Oops. I did see some samples in the C::U::Cookbook. I guess I'm looking
for general file uploads (I don't need the image manipulation that is in
all the examples). Am looking to check for size, and trap errors in a
friendly way while uploading a file to the hard drive.
Thanks, Brad
Mark,
Hi all,
I want to give users the ability to set their own expire times. Problem is
that I'm not tapping the database for their choice until after
cgiapp_init, the only place I can really:
$self-session_config( DEFAULT_EXPIRY = 15);
without getting an error and death.
I'd like to be able to
I'm curious about
handling situations where I have common operations that must be applied
to
all modes upon exiting. Example:
I load a unique .tmpl files and assign values to parameters in run
modes.
But before outputing, I want to assign some values common to all of
.tmpls.
Bill, yes I have. But that really doesn't answer my question. I could be
any module that I am trying to transfer control to.
Brad
On Dec 19, 2005, at 9:21 PM, [EMAIL PROTECTED] wrote:
Typical scenario: The user is initially directed to Login.pm. After
successfully logging in, a home screen
Influenced by a long thread that I started over the weekend about the
number of run modes allowed in an application, I've been breaking my one
large app into several. I have a question about turning control back to
another module.
Typical scenario: The user is initially directed to Login.pm.
I'm liking this thread. But I have some elementary questions:
package My::MainApp;
use base qw/My::BaseApp/; # I already have this one; it handles sessions
etc
use My::MainApp::Admin; # contains the run modes dealing with admin
functions
use My::MainApp::News; # another example package of
Where's the best the place for instance and application files?
I thought, originally, that instance scripts would go in my web directory,
as in index.cgi, so it would fire automatically. But maybe, if I go with
the multi-instance scenario that Jesse just suggested, they should go in
my /cgi-bin.
Cees:
That is odd, as it usually works out of the box without requiring any
configuration.
You're absolutely right. I was just trying too hard. After commenting out
session_config and having it work, I successfully added back in:
$self-session_config( DEFAULT_EXPIRY = '+15m');
As I
Mark,
I recommended using postrun for this, becaues it runs after every run
mode in the module, but is only needed one once: After you have logged
in. I would find it more efficient and logicial to then call
set_session() at the end of the login processing run mode.
Thanks, I didn't realize
Seems like I have spent more time on C::A::P::Session than all the other
plugins combined--and I just can't get it to work. It is setting a session
in cgiapp_postrun after logging in for the first time (it is also setting
a cookie very nicely). This is evidenced by the line: 'logged_in: 1 in my
Just started working with CGI::Application::Plugin::Session and am
confused about a few things:
1) I'm used to CGI::Session, where I have to assign a cookie name and the
deal with a session id generated by C::S and written into the cookie. How
is the session id and cookie name handled in
Hi all.
New to CGI::App and am wondering how to do the following in C::A that I
was doing with a switch statement previously.
The old:
SWITCH: for ($query-param('funct')) {
/save project/ido { saveproject(); editproject(); last; };
}
The above runs sub called 'saveproject' and then when
13 matches
Mail list logo
