Skip to content
Loading...

Archives

403 Forbidden on Edit and View Form when Version History permissions denied

403 Forbidden on Edit and View Form when Version History permissions denied

A list that is set to keep past versions.  If you set permissions for one group to not be able to view the version history when you try to view or edit the a list item (both using qListView web part) you receive a 403 Forbidden response from the server.  If you return the access to the version history tpermission you can then load the Edit and View Forms.

Error “The requested page cannot be accessed because the related configuration data for the page

Error “The requested page cannot be accessed because the related configuration data for the page

Using the configuration editor in Quest Webparts to edit the web.config page if the Editor tab for the Quest Software Configuration Section Editor and a value is entered for the “Maximum File Upload Size is entered” then a ”  <EditorSettings MaxFileUploadSize=”51200″ />” is created and after the other issues are fixed then we get the error
“The requested page cannot be accessed because the related configuration data for the page is invalid”

qListView displaying different result on approval workflow depending on permissions granted fo

qListView displaying different result on approval workflow depending on permissions granted fo

qListView will display different result on Approval Workflow field if the permission granted to the user to view the site is different.

For example, when setting up qListView to display the Approval Status, if a user have full right on the site, the Approval status will display correctly (eg. display as Approved, Pending or etc). But if a user with only Read permission assigned to that site, the Approval Status will display as number (eg. 1, 2 or 3).

The About window of a quest web part still shows previous bundle version since upgrade to a full version.