Not signed in (Sign In)

Vanilla 1.1.2 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthordrwool
    • CommentTimeJun 30th 2008
     permalink
    At our site we have Lyceum installed not at the web root, but in a subdirectory "currents/lyceum" so it is accessed at http://watershedhs.org/currents/lyceum

    Everything works fine this way, with only one exception I've noticed. After you log into Lyceum, Lyceum tries to send you to portal.php in the web root directory (http://watershedhs.org/portal.php). Which of course doesn't exist because all the Lyceum files are in a subdirectory. I have worked around this by adding a line in the web root's .htaccess file to redirect requests for portal.php to the proper place.

    My question: Shouldn't Lyceum do this automatically? Apparently for all other purposes, it recognizes that its own "root" directory is in /currents/lyceum and acts appropriately. Or, is there a Lyceum config parameter that I should be setting to accomplish this more elegantly?
    • CommentAuthordrwool
    • CommentTimeJun 30th 2008
     permalink
    This is perhaps related: If I use a URL that attempts to access a nonexistant blog (say, http://watershedhs.org/currents/lyceum/bad-blog-name) I just get a blank page, instead of an error message.

    On the other hand, if I use a URL that references a nonexistant page WITHIN an existing blog, I get the 404 error message as defined in our blog theme, so that works as expected.
    • CommentAuthordrwool
    • CommentTimeJul 21st 2008
     permalink
    Any thoughts about this? (URL referencing a nonexistant blog just results in a blank page, but it should give some sort of error message.)