This is not a bug, but a problem of the webserver configuration.
What webserver software are you using? Apache, nginx, or something else?

Hi! It's also happpening to me, our Limesurvey is on an URL with the same pattern: www.site.com/limesurvey/index.php/admin/authentication/sa/login

I think it's indeed a bug, as reported @cheeseburger, for the following reasons:

1. The infinite loop in the "Checking permissions" page that appears in only some surveys, only happens in the new editor (released in Limesurvey 7), the classic editor works normally with no issues
2. In config file, baseURL is set to '/limesurvey'
3. In config fiile, publicURL is set to 'www.site.com/limesurvey'
4. We have another survey sites in Limesurvey 6.17.13, with the same config, no issues
5. We have used Liimesurvey from years ago, never had a problem with webserver configuration

Because of that issue (and some others), we're still sticking in version 6.x

I think this same issue is reported on https://bugs.limesurvey.org/view.php?id=20541

Now, if there is some step that I'm missing and was set in version 7.x, I would be very appreciated if you let me know.

Editor selection popup.png (72,452 bytes)   

Editor selection popup.png (72,452 bytes)   

Checking permissions.png (13,149 bytes)   

Checking permissions.png (13,149 bytes)   

@frankro14 LimeSurvey 7 requires that proper rewrite rules can be used or are set by the webserver configuration. This is not a bug in LimeSurvey.
Same question: What webserver software are you using? Apache, nginx, or something else?

Hi we are using Apache. We found the multi-step configuration change in the docs and applied it. It did allows us to access the surveys we could not previously access however some current challenges include:

• although we used the same method for multiple servers running LS v7, the behavior for how we edit surveys is different for each
• we applied the rewrite steps and changed GET to PATH and this allowed us to access the "CHECKING PERMISSIONS" related surveys but only allows us to use the new editor and the option to use the old is no longer possible
• for some reason some of our servers allow us to access ALL of our surveys using the old editor and others do not
• for the servers that do not allow us to 100% use the old editor, for some unknown reason forces the new editor on SOME of our surveys and on others, it allows us to use the old editor
• the changing behaviors and inability for any of our programmers to find a consistent logic or pattern feels like a bug
  Thank you for your time to respond and to inquire with more questions. Appreciate it.

@c_schmitz in my case, I'm using Apache