MichaelBluejay - 6:25 am on Sep 30, 2013 (gmt 0)
Okay, I got my second idea above to work, by doing the following:
(1) Changing the ownership of the symbolic link to "main" (not sure if this was really necessary, but it was the first thing I tried. That alone didn't fix it.)
(2) Changing the ownership of /home/subuser/test to "main". (That also didn't fix it.)
(3) Setting the permissions of /home/subuser/test/ to 777.
That does seem like a bit of a security risk, though. I imagine the risk is that if anyone is able to log onto my system, no matter what user they are, they can scan for directories that have write access, and then put web-accessible files there. But I don't know a way around this.
Is there a way to do either the first method, the second method, or some other method of granting editing access to a subuser without compromising security?