Password Protected Area

Permalink
I have a client with a password protected area for their staff.http://www.mwood.cc/high-school/staff... Up until we updated to version 8, clicking this link would give the user a login screen. Now it just gives a page not found error. Any help would be appreciated.

walkingstick
 
tallacman replied on at Permalink Reply
tallacman
I can have look for you. Id need your admin login to the c5 dashboard. Send me a private message if thats ok.
walkingstick replied on at Permalink Reply
walkingstick
Some more information on this. I've had my developer working on this, trying to resolve it, and this is what he had to say when I asked if he'd figured it out:
-----
Sadly, no, I’ve been working on it all night and I cannot figure out why it is doing this. At first I thought it was some custom code I built, but then I realized that it would do this even on pages that my code didn’t affect. It’s very weird, it’ll redirect a root level page like the Search page if you remove Guests, but if it seems like putting a page in a subfolder breaks this because I have pages in a Test folder that won’t redirect to login.

FWIW, I’m starting to think it’s a core routing bug having to do with spaces and hyphens in the location/URL because it seemed to come and go when these were present and interestingly, I just tried it on your site (my personal site, not the client's site) and it exhibits the same behavior. Setting permissions on the ‘portfolio’ page works fine, but try it on a page in ‘SEO Services’ and it just goes to ‘not found’, same with a root level page ‘About Walking Stick Communications’. That being said, a Test subfolder on mwood seems to exhibit similar behavior
----
So, there we have it. If this is a bug in the core code of version 8, how do we get this fixed? The client is very cranky about this problem.
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi walkingstick,

Have you checked the bug tracker to see if others are experiencing this issue? If no one has reported this issue, I recommend reporting it and including the specific steps required to repeat the error.

concrete5 bug tracker
https://www.concrete5.org/developers/bugs...

In the future, when making significant site changes and updates, I highly recommend applying them to a clone of the live production site first. This will allow you to safely check for errors and issues before making the changes live.
walkingstick replied on at Permalink Reply
walkingstick
Thanks. I have posted it to the Bug Tracker.

We have over twenty C5 sites now. We did do some testing on several sites for a few weeks before rolling the update out across all of them. This is just one particular bug that cropped up for this client's particular issue.
Doki replied on at Permalink Reply
Doki
I know this is an old thread but I'm also encountering the problem in v8. Do you have the link to the bug tracker on-hand?

The weird part for me is that some pages properly route to the login page and some don't. Even in the same heirarchy level, some will route to login, and some will route to 404. The only thing different in my case is that the pages are consistent on where they route.
Doki replied on at Permalink Reply
Doki
Disregard request for bug tracker. I'm currently running v8.1 and see the issue is fixed on the 8.2.0RC2 instance running on our test server. Ergo, the solution to the above issue is to move to v8.2.1.