The specified page details could not be found.

[mmickelson]

I'm getting this error "The specified page details could not be found." that makes pages invisible no matter what settings I have in the dashboard. I've added the usual basic authentication code at the top of each page I want secured.
I added "" to the page_include_paths in the config.php so that the admin site root files are included in the options for page level authorization. See #183 for the thread.
It seems that the root level files are the ones that are having this problem.

What does the error mean and what might be a way to fix it?

[alexweissman]

Are the paths to the pages appearing in your pages table? If so, what are they?

[mmickelson]

They show up as /SystemAdmin.php, etc.

[alexweissman]

Can you try debugging the value of $relativeURL in models/authorization.php on line 285? There might be a problem with the way that getRelativeDocumentPath is resolving the document path. This could be a bug.

[mmickelson]

I am using the latest of the butterflyknife branch since it looked like that was the recommended version from what I read.
The function that encompasses that line of code is function securePage($file). If I add echo "RELATIVE URL: ".$relativeURL; so lines 284-289 read

else {
    // Automatically grant access if master (root) user
    if ($loggedInUser->user_id == $master_account){
        echo "RELATIVE URL: ".$relativeURL;
        return true;
    }

I am redirected to the 404 page. I modified the page I'm trying to access to echo that it was going to redirect to 404 and comment the actual redirect, I can see that when I try to access the page, it shows that $relativeUrl is set to SystemAdmin.php.

One question, does User Frosting follow requires and includes to be sure each bit of code used has permission for that level? For example, if SystemAdmin.php has

include("../Connection.php");
include("includes/paginator.php");
include("includes/paginator_html.php");

Do I need to make sure all of those are tracked by User Frosting? I suppose it would make some sense if it did. None of those files are included in the config as folders to track. Maybe that's causing the issue?

[alexweissman]

FYI if you want to use debug print statements without actually sending them to the output of the page, you can use the command error_log("blah") to print stuff directly to the php error log. I use it all the time, it helps a lot!

[alexweissman]

Alright, closing this issue - lemme know if you have the same problems with the master branch.