This topic is locked

Dynamic Permissions Problems

5/29/2009 4:49:36 PM
PHPRunner General questions
A
afdesigns author

I'm in the process of moving a project that I created in v3.1 to the new v5.1. Rather rebuilding-from-scratch would be a better term as v5.1 has added a lot of included features that means I can remove tons of custom code that was always a bit sketchy. I am trying to use the dynamic permissions as that is a serious plus for my application. However, when ever I enable it I and setup an admin account in PHPrunner just like I should per the manual, I receive a completely blank screen on login minus a log out option. No tables, no reports, no admin controls. Nothing. Anyone else running into this problem or do I just have a individual issue? Using the current build of v5.1 as of today.
http://demo.asprunner.net/eric_audioforcedesigns_com/TMLVAT
login: admin

pass: admin
Thanks!

  • Eric

A
afdesigns author 5/29/2009

To further confuse us... Now it's working at random. Sometimes I get the full menu on login, but most times I don't get anything. Seems to work about 1/4 of the time and not work 3/4 of the time... Try that one on...

  • Eric

A
ashipley 5/29/2009

Well, let me make it worse for you. I have 2 databases, both crezated under 4.2 and cvontinuing up through 5.1 They are located on 2 different servers. The mnues worked properly on both of them until this latest build. Now, the menu works fine on one server, but intermittently on the second one. When it does not work properly, I can simply click "Back and then, without any changes, click "Submit" and it works fine the second time in.
I did note a problem once with the menus hiding on me with the new cascading meunes. I had to assign each page to a group that I had acces to, or not only could I not access the page, it did not even show up on the menu. A neat trick, but I suspect the problem lies in the proram not picking up your status every time, and limits the menu items according. Just for GP, try assigning the pages to "Guest" or "Default" and see if the problem disappears.
Arthur.

A
afdesigns author 5/29/2009

Now we are getting to the root of the issue. It is seeing me logged in as a guest. I hammered it till I was able to log in, gave "default" access to four tables, "guest" only access to one, and left "admin" with access to all. Loged in as the admin account and it gave me only the rights of a "guest". Good call Arthur! Guess we have a major bug in our hands...

  • Eric

A
ashipley 5/29/2009

I may hyave stumbled across soethign helpful. As I was working on the problem for my database, I discovered that my name had been assigned to 2 diferent groups. One was admin and the second was a lower level group with fewer priveledges Sometimes when I logged in it picked me up as Admin and sometimes at the lower level. Look to see if you might have admin / admin set with more than one level of permissiobs (Assigned to more than one group)
Arthur

A
afdesigns author 5/30/2009

Been playing with it this morning to try to find some patterns to help figure out where this bug is playing around. It looks like the problem is with the PHP on the initial menu that comes up right after you login. I have guest permissions set to see only one of my tables, with no delete, add, or modify rights. I log in as an admin and I only see that one table. Once I go to it, all the tables are on the left just as it should be and I have all the rights I should have as an admin. I tried removing the cascade menus and that didn't change anything. Also tried my project on three totally different servers from three different hosting companies, local machine with XAMMP, and the demo site. So I highly doubt we have a server issue.

  • Eric

J
jalongi 5/31/2009

Just to let you know that I too am having the same problem ever since I upgraded to thte latest release. Changing back to static permissions corrects it but who wants that. I can also confirm that it is onlt on the first menu after login. If you refresh the screen, the complete menu appears.
Joe

J
Jane 6/1/2009

Thank you for pointing to this bug.

We'll fix it in the next update.