The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/global.php(961) : eval()'d code 26 errorHandler->error
/global.php 961 eval
/printthread.php 16 require_once
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/printthread.php(287) : eval()'d code 2 errorHandler->error
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



UserSpice
Forbidden after update from 4.2 -> 4.3.2 - Printable Version

+- UserSpice (https://userspice.com/forums)
+-- Forum: Support Center (https://userspice.com/forums/forumdisplay.php?fid=23)
+--- Forum: UserSpice 4.3 and Below (https://userspice.com/forums/forumdisplay.php?fid=26)
+--- Thread: Forbidden after update from 4.2 -> 4.3.2 (/showthread.php?tid=898)

Pages: 1 2


Forbidden after update from 4.2 -> 4.3.2 - nessinits - 01-02-2018

It's weird. I've updated to 4.3.10 hoping that the issue would be solved you updating. The issue is still the same, but I also noticed that the update.php didn't notify me of updates. Every update 0 updates have been applied, but when I check the updates in the code these seem to be applied. Also the update table isn't updated on the two/three last updates.

I have no clue, but the userspice works (without re-auth).


Forbidden after update from 4.2 -> 4.3.2 - Brandin - 01-02-2018

It has to be a permission issue with admin_verify.php...if you set a page (admin.php for example) to reAuth 1 and try to visit the page, do you get forbidden as it tries to redirect you to admin_verify.php?


Forbidden after update from 4.2 -> 4.3.2 - nessinits - 01-02-2018

The issue is solved. Weird, but true. I only used my admin account in dev. When I added another account, made it administrator and then tried to access the function that was reAuth-ed it worked. When I tried afterwards with my regular admin account, it also worked.

I have no clue what happened, but it works.


Forbidden after update from 4.2 -> 4.3.2 - Brandin - 01-02-2018

Glad to hear it, I would love to figure out what happened but it shall be a mystery!