-
Notifications
You must be signed in to change notification settings - Fork 293
Action load_repository_info triggered when no user logged (and no repo active) #617
Comments
The code at this line mentioned looks quite different from what it was in 5.3.1. I realize lots things were shuffled around, and that at loading the person's repo something isn't going as it should when moving to the new release. |
Update from 531 to 532 should be normally not so complex.. Had you also simply cleared the cookies (by unlogging)? |
Thanks Charles for the prompt reply If we find the cause to this we could add a note to the update information page so we can avoid others complaining ;-) I just re-tried
Just to share more information on the setup:
I may not be able to give a quick update, but I'll see if I can do a comparative install with a close-to-identical config and check if the config data in the DB store looks and that it would require updating (maybe manually fora dev release) some things. |
What is the complete PHP Fatal error? |
That is all I get in the error logs. When I turn loglevel to "debug" all additional errors I get is just SSL debugging stuff for the SSL vHost. The error message points to line 1113 in class.AbstractConfDriver.php, and yes that happens even before loggin in. |
ah ah interesting, indeed not logged = no current repository => fatal error trying to get its ID. The point is that it should no go through that part when not logged in. Do you have guest user enabled or something like that? Can I access your install? |
Now that sounds interesting, I've sent you access information in private to your @pydio.io mailbox. |
…gged (necessary for vision theme). Fix #617
should be fixed by cc6b65b |
Hi
I really am looking forward to 5.3.2 but (the as it seems) same issue happened as I had here
#603 while preparing a pull request, now this happened
after updating from 5.3.1 DEB to 5.3.2 on Debian Wheezy.
What I did so far:
Yet it still happens...
And I'm getting this in the error Logs of apache:
Will continue to investigate for what I can, I hope this can be avoided during regular updates by time of a stable release.
--- Mathieu
The text was updated successfully, but these errors were encountered: