More in this section
Forums / Bugs & Issues / Non-administrator backend users cannot access the backend after upgrade to Sitefinity 8

Non-administrator backend users cannot access the backend after upgrade to Sitefinity 8

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
3 posts, 0 answered
  1. Scott Farmer
    Scott Farmer avatar
    9 posts
    23 Mar 2010
    05 May 2015
    Link to this post

    Hi guys,

     Since we updated to Sitefinity V8, it appears that our non-admin backend users can't login to the backend.

     Can anyone provide any clarity on this kb article? There's really no instruction. Any help would be greatly appreciated.

  2. Stefani Tacheva
    Stefani Tacheva avatar
    718 posts
    31 May 2017
    08 May 2015
    Link to this post

    We provided response in the support ticket you have opened. I am pasting it below so it cam be useful for our community:

    The error is being caused by one of the scripts that get executed during the upgrade to Sitefinity 8, in which the scripts fail to be executed properly. In order to fix this problem you will need to view the WebForm that is attached to the article in your Sitefinity project after being logged in as an administrator.

    The web form can be placed anywhere inside the project folder (root, another folder, etc.), the important part is to navigate to the page once logged in. For example, if the form was placed on the root, you would navigate to in order to execute the fix.

    Stefani Tacheva
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
  3. Steven
    Steven avatar
    0 posts
    22 Aug 2013
    12 Dec 2016 in reply to Stefani Tacheva
    Link to this post

    I'm experiencing this problem as well, but you did not attach the FixUpgrade.aspx to this post.

3 posts, 0 answered