Please help us help you and fill where relevant:
LimeSurvey version: [LimeSurvey Community Edition Version 7.0.7+260729]
Own server or LimeSurvey Cloud: Own Server
Survey theme/template: Any theme
==================
Hi. We just upgraded from v6 to v7. All has seemed to be working well over the last two weeks. We just noticed that if we click to edit any surveys, the URL remains the same as it has always been, for example:  mySite.com/index.php/surveyAdministration/view?surveyid=123456 . However when we click on ONE of our surveys versus all of the others, the URL is different and looks like this:  mySite.com/editor/#/survey/123456 . 

Note the EDITOR in the URL. It only does it for one survey and then the screen displays "checking permissions" and then gets stuck and never advances. Even if we manually key in the syntax of the working URL, it will redirect to the EDITOR URL. I am assuming this is attempting to use the new editor vs the old? Any idea why this is redirecting to this different URL rather than using the old control panel editor like all of our other surveys? 

At the moment we cannot access this one survey as a result. We also attempted to copy it and it too produces the same results. 
Thank you for any help.
 

This might be a bug in this specific version.

What you can also try, instead of copying, is downloading the survey and importing it again.

But I don't see how this should impact the URL for the editor. It really sounds strange to have this behaviour.

In Version 7 the URL is rewritten in a different way. PATH instead of GET is used.

Are you using the new or old editor?
You can check and change that in the user menu.
 

 

I recommend to use the classic one first and check if everything is working.
Then check if the webserver is ready for URL rewriting as needed.

www.limesurvey.org/manual/LimeSurvey_7_Q...itor_in_LimeSurvey_7
 

haha I must be waaaaay too into LimeSurvey! Jelo's screen shot pointed me to the toggle to choose the editor - and I hadn't been able to see that in previous versions of v7. But today with v7.09 I SEE IT!! Such an amazing relief. Thank you so much Jelo! 

thank you for the input Holch. Really appreciate you taking the time! FYI - first thing I had tried when encountering the issue was to export from a working version and then imported, but the issue had remained. Good thinking though - we were both on the same path of diagnosis.