I've been using HTML::Mason under mod_perl on my site for awhile, using
0.89, and I like it lots. :-) So when the new 1.0 came out, I went to go
upgrade, and broke EVERYTHING.
Not only that, but, I haven't been able to make sense out of what Mason
wants for its dir heirarchy, anyway:
First,
At 11:03 AM -0800 3/1/01, Rob Bloodgood wrote:
I've been using HTML::Mason under mod_perl on my site for awhile, using
0.89, and I like it lots. :-) So when the new 1.0 came out, I went to go
upgrade, and broke EVERYTHING.
Not only that, but, I haven't been able to make sense out of what Mason
Hi Rob
I just went through this exact situation this morning. I ended up
(unnecessarily) recompiling apache/mod_perl in the hopes of fixing it. All
that really needed to be done was to add "use HTML::Mason::ApacheHandler;"
to mason's handler.pl. I'm assuming your v0.89 site was working properly.
"Ray" == Ray Zimmerman [EMAIL PROTECTED] writes:
Ray At 11:03 AM -0800 3/1/01, Rob Bloodgood wrote:
and in the same vein, the *ONLY* way I could get it to run was to put it's
data_dir under DocumentRoot as well.
Ray Is it a file permissions problem? If you're
Hi Rob,
I've been using HTML::Mason under mod_perl on my site for
awhile, using
0.89, and I like it lots. :-) So when the new 1.0 came out,
Me too 8^) I'm a Mason junkie for going on 4 years now I think - since 0.4
8^)
I went to go
upgrade, and broke EVERYTHING.
There are some very
