> You switched the admin flag? (or have you applied other actions like > reconfiguring the anonymous user?)
I dod both. Switched the admin flag to false and reconfigured the anonymous role as follows: Website: Read Only: / URL: Get&Post : /* URL: Deny Access /.magnolia* > Where do the restricted files resist? docroot? mgnl-resources? the css and js files resist in /mgnlFiles/docroot/<module_name> /css or js and are loaded just fine in the author instance > magnolia.develop mainly switches of caching for files in mgnl-resources, > js-classes, ... I know that, but it was just weird enough that when I switched it to true it worked just fine.... > Not sure, but if you forgot to reconfigure the anonymous role in a way that > it has access to the js file it might actually be that the login screen has > been cached. the login screen looses its css and js too... (when I call publicinstance/.magnolia) > To verify that you call the scripts directly and check them. I use fireBug and my css and js file apear to be loaded, but not implemented. I have a js for the date and time on the website and although firebug loads the script, the browser gives an error that the function that is called does not exist... > If this is the case we should add a bug report: don't cache 403 (access > forbidden) I beleive you have all information now. If I have made some mistake please correct me... if not I shall submit the report.. Thanks.. Vasko ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
