When the above page appears, I login. Then when I go to delete a school year, it deletes, but when I refresh the page, the school year I deleted appears again. If I delete it a second time, I get an error. Why can’t I delete the school year?
The previous links do not work. I am unaware of another way to attach images.
Hmmm, this is very odd, and not something I have seen before. Please can you tell me what version of Gibbon you are using, and what server stack you have? Ross
Hmmm, this is very odd, and not something I have seen before. Please can you tell me what version of Gibbon you are using, and what server stack you have? Are you by any chance using a version of PHP lower than 5.5? Ross
That all looks fine. Very odd. What browser are you using? Can you clear your browser cache, and try a different browser and also a different computer? Just trying to narrow down the possibilities.
I tried different computers on different browsers. Also tried a different network.
No matter what I can’t log out and I get an error when I click links; “You do not have access to this action.”
I am really tired of installing Gibbon over and over. I have tried 2 other SIS software but this is the absolute BEST!!
Feeling kinda down and bummed. Feel like crying because I already showed the staff Gibbon and they love love loved the demo.
Ross mate, please assist a humble Network Admin. Please?
Created a new user as an Admin. Still no luck logging out or getting access to certain areas without “You do not have access to this action.”
cadelp, I am hearing your pain, and happy to try and help. Can you please email the URL, username and password for your install to email@example.com, and I will see what I can do. Thanks. Ross.
Did you get my email?
chadelp, a little patience please. I know you are keen, but keep in mind that I have a full time job, with many demands, and so I can’t always respond immediately. I have received the email, and will look now. Hold tight…
Chadel, I have done some testing on your system, and I cannot recreate issues #2 and #3, so it seems these are on your end, even though they are server side script errors. I am trying to think of something on the client side that would effect the server scripting, but nothing comes to mind. I know you have tried different browsers and networks, but can you think of anything that the things you have tested have in common, that would be different from my setup?
Can you check your PHP error log to see if it contains anything of interest? How about Inspect Element’s console in Firefox? Seeing any errors?
For issue #1, I can recreate it, and I guess it might have something to do with redirects. Can I ask you to do a test install of v13’s development branch, to see if you get the same issue?
Hope this helps, let me know how you get on.
One thing I just realised: issues #2 and #3 appear only once you try to log out unsuccessfully. It seems it is logging you out, but for some reason the Home page is acting like it is still logged in. Again, please can you check your PHP error log, this time for anything referencing the file logout.php
I wonder if this is to do with the fact that you have opcache enabled in PHP…
@skuipers any ideas what might be going on here? Seems similar to something that came up with Craig a few months ago, but I can’t recall what that was. Any thoughts?
@admin It does sound a lot like the login/logout errors from the previous development branch (a 303 redirect header was being applied that caused browser caching issues). The particular lines of code were never in v12 and no longer in v13, however the cause may be similar.
Chadel, you mentioned installing Gibbon over and over again, it’s possible that something is cached locally on your machine (like a redirect). Try clearing your browser cache, cookies and saved login data.
Also one more thing to try: if you have v12 installed, open the index.php file. At the very top, change lines 21 and 22 to read:
`ini_set('session.cache_limiter', 'nocache'); session_cache_limiter('nocache');`
</p> (in v13, these are lines 46-47 of src/Gibbon/session.php) These two steps should help ensure your current cache is cleared and nothing else is written to cache. Be sure to test login/logout with different browsers if you can.
Good morning @skuipers @admin
It is indeed a very lovely morning.
I did 4 of the 5 steps recommended by the 2 of you.
- PHP error log referencing file logout.php - no error for logout.php
- opcache - disabled from htaccess before it runs script from php.ini as it was already installed; php_flag opcache.enable Off
- browser cache, cookies and saved login data to be cleared - Firefox, Chrome tested on several machines
- index.php - line 21 and 22 replaced with nocache lines
- v13 install test - installed v13 but before I could get to test it, v12 is working!
Didn’t get to step 5 as one or more of the previous steps worked.
Seeing that I disabled opcache and added nocache to lines 21 and 22, would running both cause an issue?
Ross I was indeed impatient and I humbly apologise. I got spoiled with those times you answered so swiftly.
Chadel, I understand your impatience, as sometimes we just need things to work, and time slips away painfully.
I’m really glad the issue is resolved, but I would love to know when step caused it, 2, 3 or 4. Would you have time to undo steps 2 and 4, individually, and in combination, to see which step makes the difference.
Thanks for such a detailed followup: this kind of information, archived here, will definitely help future Gibbon admins.
For you Ross, I would do it. Only because there was nothing for me to follow but now I may leave a trail for others to follow
Getting on it in a few mins. Need to stop the users who are going to do data entry.
Made everything default by restoring a backup from 2 days ago.
- opcache - disabled from htaccess before it runs script from php.ini as it was already installed; php_flag opcache.enable Off | Added the command by itself without step 3 and 4, same issue logging out and authenticating. Restarted Apache and MySQL, same issue with authenticating and logging out
- browser cache, cookies and saved login data to be cleared - Firefox, Chrome tested on several machines | Cleared the cache before step 2 (so only step 3 was done) and I got same issues authenticating and logging out. I then did step 2 and then step 3 right after, so disabled opcache and cleared cache, same issue authenticating and logging out
- index.php - line 21 and 22 replaced with nocache lines | Restored backup on server again for a clean start. And restored browser backup on chrome (on PC) but left firefox with a clean cache. I then did step 4. Checked firefox (clean cache) and it worked. Checked chrome (old cache) and it didn’t work as I suspected. Clean cache and it worked.
So now that all this testing was done, my conclusion is step 4 works with firefox because I did the ‘everything’ erase and nothing new will be cached. With chrome, the old cache prevented me from logging out. Step 4 ensures nothing new is cache, so clearing the chrome cache allowed chrome to see past the old cache, and of course cache nothing else in future.
Hope this post pleases you greatly.