Forum

Michael,

The only issues I have heard regarding javascript behaving differently when logged in or out usually was an issue with knockout.  That is because the developer might have tested while logged in and knockout script tag is on the page for the admin ribbon and didn't realize knockout reference may not exist when not logged in.

I haven't heard of file permissions causing js issues.  If you are looking at the resources in Firebug as a logged out user, can you directly access the angular script files?  If not, are you getting a 401 or something when they are serverd up to the client?

I believe I've found the root cause. I have a few javascript files we've packaged and installed to our dnn environments. One is a packaged version of angular bootstrap ui and the other is a module for setting up dnn api calls so that code doesn't have to be re-written for every module that needs it. Now there's two main issues that caused problems. The first is the order that I register the files in my code behind. Here's the incorrect way to do it:

You might be thinking 'what could possibly be wrong with this?' Well it's not obvious (at all) even when you look into the scripts themselves. My app definition adds my dnn api module as a dependency. However it's my controller script that implements it. I can't be sure exactly why this happens but since scripts that implement dependencies aren't loaded first they don't function properly. Simply load those first like so:

And the problem magically goes away.

The second problem that I have not been able to find a way around is with my api module. When the user is not logged in that file or its functionality does not exist. This causes the controller to not function or become undefined or unavailable. I was talking to co-worker and from what I gathered that module doesn't exist? From what he said $.ServicesFramework doesn't exist when you're not logged in and that causes the module to fail causing my scripts to crash. Haven't found a work around for this yet.

Thanks.