- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2014 02:15 PM
I built a custom application and on one instance it works great but when trying to pull the update set it messed up. So I ended up rebuilding it completely on a different instance and it work the exact same (for admin). But when I impersonate a user that will be using the app none of the scripts run. No client scripts, no UI Policies, nothing but as an admin all 4 of us can use it and it works perfectly. Would any one know why this would happen and how to fix it?
-Josh
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2014 06:29 AM
When you load a page as a non-admin, are there any errors on the page? What you're describing appears to be that some script that is applied on-load is erroring out, preventing the rest of the client scripts and ui policies from loading. Use firebug and load the page, and see what errors come up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2014 02:25 PM
Check your Read/Write Access Controls for the tables you are accessing. Do your itil users (or whoever is trying to run the app) have access to Read/Write to the tables?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2014 05:31 AM
That was the first place I looked. The custom app creates it's own roles to use the app and I made sure to add that role role to every group that will be using it. All the groups can read and write the problem is the scripts. All the client scripts and UI policies I wrote do not work for non-admin roles. I don't know what would cause this problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2014 06:29 AM
When you load a page as a non-admin, are there any errors on the page? What you're describing appears to be that some script that is applied on-load is erroring out, preventing the rest of the client scripts and ui policies from loading. Use firebug and load the page, and see what errors come up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2014 07:23 AM
Thanks. It was an error in my first client script that didn't get caught by the debugger. When I deactivated the script everything went back to normal.