I run a shared site, with several users/vhosts. I'd like to be able to use mason on all of them, but am having problems with that. If I have a perl module named "Album.pm" on site 1, and then I create another module on site 2 and name it "Album.pm", these seem to get mixed up, and sometimes site 1 will show the output from site 2's Album module, and vice versa.
I have the sites set up with separate component roots, in httpd.conf: (site 1's VirtualHost directive:) PerlSetVar MasonCompRoot /home/user1/public_html PerlSetVar MasonDataDir /usr/local/modperl/mason-data/user1 (site2's VirtualHost directive:) PerlSetVar MasonCompRoot /home/user2/public_html PerlSetVar MasonDataDir /usr/local/modperl/mason-data/user2 This seems to have no effect though. Right now the only solution seems to be to name the modules differently, eg. "Site1Album.pm" and "Site2Album.pm". I'd rather not have to do that, as it seems risky (don't want to have to approve every module a user wants to post), and it makes it hard to post multiple installations of the same program. Is there a better solution to this? Thanks, -- Jackie Hamilton [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
