Hey Folks,
I have just discovered the long and hard way, over half a days worth of my time, that it is necessary for the SuperAdmin to also be an Extended User, if that addon is being used.
A message like the following comes up, if they are not when accessing pages that require authorization
:
Somehow the k_user_id not being set correctly when the Super Admin does not exist in Extended Users
affects all user's attempting to access pages that need authentication. I noticed that the k_user_id was ending
up set to '-1' as my Super Admin user in this case. I figured somehow I must have broken my DB, although
I had no idea of how. It took a while to notice this, because if I am not building a site, I use a regular
administrative user when working on it. This user's k_user_id was showing up sensibly, and verified
to be correct. Yet it still could not access the profile page.
So we know that at least in some cases without Super Admin also being an Extended User, the k_user_id for
them can end up inappropriately set, (i.e. '-1'.)
I have no idea why this prevents all users from accessing a page, but it can.
I confirmed this as a bug in the code, somewhere, by duplicating it with the demo code that is used to teach
the use of the Extended Users addon. If your Super Admin is already an extended user, because you followed
the tutorial verbatim, simply delete them from the Extended User side, and the problem should arise. At least
it did for me, duplicating my real site's issue. I ended up in this circumstance by not adding the Super Admin
as an Extended User, after learning from the tutorial, and not realizing it was actually necessary to do so to obtain the correct behavior. I highly doubt that that was the intent, hence posting this here.
Thanks again for such a great tool KK. I can say that I understand the structure of the DB better than ever now.
I have just discovered the long and hard way, over half a days worth of my time, that it is necessary for the SuperAdmin to also be an Extended User, if that addon is being used.
A message like the following comes up, if they are not when accessing pages that require authorization
:ERROR: Tag "form" - page_id required
Somehow the k_user_id not being set correctly when the Super Admin does not exist in Extended Users
affects all user's attempting to access pages that need authentication. I noticed that the k_user_id was ending
up set to '-1' as my Super Admin user in this case. I figured somehow I must have broken my DB, although
I had no idea of how. It took a while to notice this, because if I am not building a site, I use a regular
administrative user when working on it. This user's k_user_id was showing up sensibly, and verified
to be correct. Yet it still could not access the profile page.
So we know that at least in some cases without Super Admin also being an Extended User, the k_user_id for
them can end up inappropriately set, (i.e. '-1'.)
I have no idea why this prevents all users from accessing a page, but it can.
I confirmed this as a bug in the code, somewhere, by duplicating it with the demo code that is used to teach
the use of the Extended Users addon. If your Super Admin is already an extended user, because you followed
the tutorial verbatim, simply delete them from the Extended User side, and the problem should arise. At least
it did for me, duplicating my real site's issue. I ended up in this circumstance by not adding the Super Admin
as an Extended User, after learning from the tutorial, and not realizing it was actually necessary to do so to obtain the correct behavior. I highly doubt that that was the intent, hence posting this here.
Thanks again for such a great tool KK. I can say that I understand the structure of the DB better than ever now.