Re^2: "MojoX::Session" suddenly quit working?!

Replies are listed 'Best First'.
Re^3: "MojoX::Session" suddenly quit working?! by jethro (Monsignor) on Apr 07, 2009 at 21:02 UTC
One mans broken is another mans feature. The new version might have changed something internally that your code expected to behave a certain way but was never written in stone, just to give one example of how it might not be a "seriously" big bug. Sometimes when I had a really difficult-to-find bug in my code I later found out that a presumption I was absolutely sure about turned out to be false.	[reply]
Re^4: "MojoX::Session" suddenly quit working?! by locked_user sundialsvc4 (Abbot) on Apr 07, 2009 at 21:15 UTC
Just help me discover “what and where t'hell it is,” and I shall be a happy boy.
Re^5: "MojoX::Session" suddenly quit working?! by jethro (Monsignor) on Apr 07, 2009 at 22:25 UTC
From my point of view it is obvious: The only thing that changed seems to be MojoX::Session (and maybe a few other modules updated with it? Did you also check differences in Mojo::Base or Mojo::Transaction?), so there must lie the fault (at least it would in a perfect world following logical rules ;-). You might check if the update changed some file permission on files used by the web server or mojo. You might try to debug the mojo modules themselves. Sorry, I don't have anything more than general ~~platitudes~~ advice	[reply]
Re^5: "MojoX::Session" suddenly quit working?! by locked_user sundialsvc4 (Abbot) on Apr 08, 2009 at 01:16 UTC
“Platitudes” or not, it is a problem that was introduced with the most recent update to some part of Mojo or Mojolicious. Doing a manual installation of the prior version `MojoX::Session` (v0.07) apparently fixed the problem. “I guess I was being a bit naive,” he admitted ruefully. “I guess I just thought that code which didn't work didn't make it to CPAN. And to be quite honest, it still seems strange... like I'm still missing something basic.”