Okay - I tried both Neil's solution and the Pm/Jo solution, and the following happened:<br>
<br>
Neil's solution works if the pmwiki directory is still in the public
html realm (for me, /var/www/blah.blah). Unfortunately, I'm in
hosted server space and have no access to httpd.conf, so I have to
tweak his solution for .htaccess files, but it does work like
clockwork. It still seems like it'd be best to get it out of that
realm and into the non-public area (for me, /home/blah) -- while you
can't run pmwiki.php, you could still get in and run the scripts, or
whatever. So I tried putting the symlink (to
/home/blah/pmwiki/pub) in the document root, and setting up the
+FollowSymLinks option in .htaccess, and that worked to some
extent. Now everything appears to work except the CSS & the
images (anything that is accessed directly by the browser), and I get
403: "You don't have permission to access
/farmpub/skins/pmwiki/pmwiki.css on this server". permissions on
the folder are 777. Do you think that there is some kind of
permission override or am I still not "getting it"?<br>
<br>
Jon<br>
<br>
<br><br><div><span class="gmail_quote">On 6/3/05, <b class="gmail_sendername">Joachim Durchholz</b> <<a href="mailto:jo@durchholz.org">jo@durchholz.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Patrick R. Michaud wrote:<br>> On Thu, Jun 02, 2005 at 10:03:44PM -0500, Jon Haupt wrote:<br>><br>>> So then I tried using a "symlink". Again I didn't know what i was doing<br>>> so I just looked it up and ended up using the following command to create
<br>>> a link (from the field /pub directory):<br>>><br>>> ln -s /path/to/pmwiki/pub farmpub<br>><br>> [...]<br>><br>> You also have to make sure that the webserver has permission to the<br>
> farm's pub/ directory -- at minimum this means having execute permissions<br>> on each of the directories /path, /path/to, /path/to/pmwiki, and<br>> /path/to/pmwiki/pub .<br><br>Apache may or may not follow symlinks as well - it's a configuration
<br>option. If it's switched off, you can often activate it in .htaccess with<br><br> Options +FollowSymLinks<br><br>in the directory that has the symlink (or one of its ancestor directories).<br><br>Whether an option is allowed or not in .htaccess can be configured in
<br>Apache, so it is possible that symlinks can't be made to work. I suggest<br>setting up a test that checks just whether symlinks work, say, by<br>installing a simple .html file, creating a symlink to it from the same<br>
directory, then retrieve the file and the symlink and see whether the<br>symlink gets served.<br><br>Regards,<br>Jo<br>_______________________________________________<br>pmwiki-users mailing list<br><a href="mailto:pmwiki-users@pmichaud.com">
pmwiki-users@pmichaud.com</a><br><a href="http://pmichaud.com/mailman/listinfo/pmwiki-users">http://pmichaud.com/mailman/listinfo/pmwiki-users</a><br></blockquote></div><br><br><br>-- <br>Jon Haupt<br>Fine & Performing Arts Librarian
<br>Iowa State University<br>152 Parks Library<br>Ames, IA 50011<br>515-294-0904<br><a href="mailto:jhaupt@iastate.edu">jhaupt@iastate.edu</a>