Strange Security(?) Issue
I came across a strange issue today.
One of our Technicians was editing his request, specifically changing the Category and Sub-Category. When he clicked the save button the page seemed to post, but it actually reverted to the previous Cat and Sub-Cat values.
I tried to edit the same request using my admin login and had no issues, so I then made him an admin, logged out, cleared the cache and logged in. Just to check his permission, I clicked the admin tab, and it showed up with no problem. We then tried to do the same edit process and has the same failed result.
The very strange thing is that when I tried to go back to the admin tab to check the permissions, then system threw a "You Don't Have Permission to View This Page". It was the same login and the same session. After repeating the process, we got the exact same result, including being able to see the admin page at 1st but not after the edit request attempt.
[Developer Speak Follows]
We are on 6.0.0 and using SQL Server.
Is the system maybe not releasing DB connectors, or caching them so his permissions got wonky? :?
One of our Technicians was editing his request, specifically changing the Category and Sub-Category. When he clicked the save button the page seemed to post, but it actually reverted to the previous Cat and Sub-Cat values.
I tried to edit the same request using my admin login and had no issues, so I then made him an admin, logged out, cleared the cache and logged in. Just to check his permission, I clicked the admin tab, and it showed up with no problem. We then tried to do the same edit process and has the same failed result.
The very strange thing is that when I tried to go back to the admin tab to check the permissions, then system threw a "You Don't Have Permission to View This Page". It was the same login and the same session. After repeating the process, we got the exact same result, including being able to see the admin page at 1st but not after the edit request attempt.
[Developer Speak Follows]
We are on 6.0.0 and using SQL Server.
Is the system maybe not releasing DB connectors, or caching them so his permissions got wonky? :?